~ / rigs / vadimgaidai / react-harness

vadimgaidai/react-harness

React Harness for Claude Code: convention skills plus a structure plugin (feature folders or Feature-Sliced Design) make Claude write React applications in one structure on a plain request, with manual spec-driven stages and an automatic lo

↗ GitHub ★ 1 MIT updated 4d ago personal setup Claude Code Claude plugin
field: unknown workflow: Frontend & designPlanning & specsPR / code review runs claude in CI
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~1.5k tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

$ git clone --depth 1 https://github.com/vadimgaidai/react-harness

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit vadimgaidai/react-harness/plugins/feature-folders/skills/structure .claude/skills/structure
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/api-contract .claude/skills/api-contract
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/autopilot .claude/skills/autopilot
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/code-shape .claude/skills/code-shape
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/error-handling .claude/skills/error-handling
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/implement .claude/skills/implement
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/plan .claude/skills/plan
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/react-hook-form-zod .claude/skills/react-hook-form-zod
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/react-testing .claude/skills/react-testing
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/react .claude/skills/react
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/refine .claude/skills/refine
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/review .claude/skills/review
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/routing .claude/skills/routing
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/spec .claude/skills/spec
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/tanstack-query .claude/skills/tanstack-query
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/typescript .claude/skills/typescript
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/ui-conventions .claude/skills/ui-conventions
$ npx degit vadimgaidai/react-harness/plugins/react-harness/skills/verify .claude/skills/verify

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (18)

Similar rigs

copied ✓