[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74HGFWW14G22X3XWDXJCFXP":3,"skill-same:01M74HGFWW14G22X3XWDXJCFXP":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M74HGFWW14G22X3XWDXJCFXP","phase-1-guardrails",null,"Use when the user explicitly asks to install the toolchain (lint \u002F format \u002F pre-commit hook \u002F test framework) or invokes \u002Finit-guardrails. Do NOT auto-install when only some tools are missing — first ask whether to add the missing pieces. This skill installs npm packages and writes config files; explicit consent required.","drumfiend21\u002Fclaude-tdd-pro","drumfiend21","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10619389?v=4","01M74HCNYY9VCB2B7FNCSPQSZN","Siddharth Joshi","01M74HCNZHQP883HA9WSN1G6TR",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Fphase-1-guardrails\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: phase-1-guardrails\ndescription: Use when the user explicitly asks to install the toolchain (lint \u002F format \u002F pre-commit hook \u002F test framework) or invokes \u002Finit-guardrails. Do NOT auto-install when only some tools are missing — first ask whether to add the missing pieces. This skill installs npm packages and writes config files; explicit consent required.\ndisable-model-invocation: true\n---\n\n# Phase 1: Guardrails\n\nYou are setting up the toolchain that lets all subsequent work happen\nsafely. The goal is \"next round of changes can't make things worse\" —\nevery commit gets formatted, linted, type-checked, and (optionally)\ntested before it lands.\n\nNo behavior changes in Phase 1. Just the rails.\n\n## What gets installed\n\nFor a JS\u002FTS\u002FReact project, the convergent stack is:\n\n| Tool | Purpose | Template |\n|---|---|---|\n| ESLint flat config | Lint | `templates\u002Feslint.config.flat.{js,react.js}` |\n| Prettier | Format | `templates\u002Fprettierrc.json` |\n| TypeScript `checkJs` | Type check w\u002Fo rename | `templates\u002Ftsconfig.checkjs.json` |\n| Husky | Git hooks | (run `npx husky init`) |\n| lint-staged | Run hooks on staged files only | (in `package.json`) |\n| Vitest | Test runner | `templates\u002Fvitest.config.with-cleanup.js` |\n| jest-dom + cleanup | Strict DOM matchers + leak prevention | `templates\u002Ftest-setup.js` |\n\nFor Python: switch ESLint+Prettier to `ruff` + `black` + `usort`,\nTypeScript to `pyright` or `mypy`, vitest to `pytest`. Same shape.\n\n## Step-by-step (JS\u002FTS\u002FReact project)\n\n### 1. Detect existing setup\n\nRead `package.json`. If ESLint \u002F Prettier \u002F etc. already exist —\nASK the user before overwriting. Their config might be intentional.\n\n### 2. Install dev dependencies\n\n```bash\nnpm install --save-dev \\\n  eslint @eslint\u002Fjs globals \\\n  prettier eslint-config-prettier \\\n  husky lint-staged \\\n  typescript @types\u002Fnode\n```\n\nFor React projects (note: `eslint-plugin-react` peer-deps cap at\nESLint 9; pin if needed):\n\n```bash\nnpm install --save-dev eslint@^9 @eslint\u002Fjs@^9 \\\n  eslint-plugin-react eslint-plugin-react-hooks \\\n  @types\u002Freact @types\u002Freact-dom\n```\n\nFor testing:\n\n```bash\nnpm install --save-dev vitest jsdom \\\n  @vitejs\u002Fplugin-react \\\n  @testing-library\u002Freact @testing-library\u002Fjest-dom @testing-library\u002Fuser-event\n```\n\nFor Node-only projects, also:\n\n```bash\nnpm install --save-dev eslint-plugin-security\n```\n\n### 3. Drop in templates\n\nCopy the following from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002F` to the\nproject root (or matching path):\n\n- `eslint.config.flat.js` (or `.react.js`) → `eslint.config.js`\n- `prettierrc.json` → `.prettierrc.json`\n- `tsconfig.checkjs.json` → `tsconfig.json`\n- `vitest.config.with-cleanup.js` → `vitest.config.js`\n- `test-setup.js` → `src\u002F__tests__\u002Fsetup.js`\n\nAdd a `.prettierignore`:\n\n```\nnode_modules\u002F\ndist\u002F\nbuild\u002F\ncoverage\u002F\npackage-lock.json\n*.md\n```\n\n### 4. Add scripts to package.json\n\n```json\n{\n  \"scripts\": {\n    \"lint\": \"eslint .\",\n    \"lint:fix\": \"eslint . --fix\",\n    \"format\": \"prettier --write .\",\n    \"format:check\": \"prettier --check .\",\n    \"typecheck\": \"tsc --noEmit\",\n    \"test\": \"vitest run\",\n    \"test:watch\": \"vitest\",\n    \"prepare\": \"husky\"\n  },\n  \"lint-staged\": {\n    \"*.{js,jsx,ts,tsx}\": [\"eslint --fix\", \"prettier --write\"],\n    \"*.{json,md,yml,yaml,css}\": [\"prettier --write\"]\n  }\n}\n```\n\n### 5. Initialize Husky\n\n```bash\nnpx husky init\n```\n\nReplace the default `.husky\u002Fpre-commit` content with:\n\n```\nnpx lint-staged\n```\n\nAdd `.husky\u002F_\u002F` to `.gitignore` (auto-regenerated by husky).\n\n### 6. Run prettier --write . once\n\nThis is the only Phase 1 step that touches existing files. Commit\nthe result as a SEPARATE, formatting-only commit so subsequent diffs\nstay reviewable:\n\n```bash\nnpx prettier --write .\ngit add -A\ngit commit -m \"chore(phase1): apply prettier formatting pass\n\nApply project-wide Prettier formatting per the new config. No\nbehavior change. Subsequent commits are content changes only.\n\nAssisted-by: Claude (claude-tdd-pro 0.3.0)\"\n```\n\n### 7. Verify everything works\n\n```bash\nnpm run lint           # may have warnings; should not have errors\nnpm run format:check   # should pass\nnpm run typecheck      # may have errors; record baseline\nnpm test               # if any tests exist; should pass\n```\n\nCapture baseline numbers (lint errors\u002Fwarnings, typecheck errors)\nin a final commit summary.\n\n### 8. Final commit + REMEDIATION.md update\n\n```bash\ngit add eslint.config.js .prettierrc.json .prettierignore \\\n        tsconfig.json vitest.config.js src\u002F__tests__\u002Fsetup.js \\\n        package.json package-lock.json .husky\u002Fpre-commit .gitignore\ngit commit -m \"chore(phase1): install guardrails (eslint + prettier + tsconfig + husky + vitest)\n\nPhase 1 of REMEDIATION. Adds:\n- ESLint flat config (with security\u002Freact\u002Freact-hooks plugins as applicable)\n- Prettier with project-wide style\n- TypeScript in checkJs mode (no file rename)\n- Husky 9 pre-commit hook running lint-staged\n- Vitest + jest-dom matchers + cleanup discipline\n\nBaseline: lint NN warnings (0 errors), tsc NN errors (will address\nin Phase 3), tests NN\u002FNN passing.\n\nNo behavior change.\n\nAssisted-by: Claude (claude-tdd-pro 0.3.0)\"\n```\n\nUpdate REMEDIATION.md to check off the Phase 1 items.\n\n## What to refuse\n\n- **\"Add Snyk \u002F Semgrep \u002F SonarQube\"** — overkill for the typical\n  small project; the standard `npm audit` + `eslint-plugin-security`\n  is enough. If the user really wants enterprise security tooling,\n  fine, but don't proactively suggest it.\n- **\"Configure CI to auto-fix and push back\"** — refuse (see the\n  `reject-bad-tooling` skill).\n- **\"Run `npm audit fix --force`\"** — refuse. Plain `npm audit fix`\n  only.\n- **\"Skip the formatting commit; just bundle it with feature work\"**\n  — refuse. The formatting commit must be its own commit so future\n  diffs stay reviewable.\n\n## What to defer\n\n- **The 1600-line god-file decomposition** — that's Phase 4, not now.\n  Phase 1 only adds the toolchain; the existing code stays untouched\n  except for prettier formatting.\n- **Fixing the lint warnings** — Phase 1 records the baseline. Phase 3\n  fixes the named bugs (which often resolve many warnings as a side\n  effect). Don't try to fix warnings as part of Phase 1.\n- **Major dependency upgrades** — Phase 5 deals with that. Phase 1\n  uses whatever versions are already in the project.\n","# Phase 1: Guardrails\n\nYou are setting up the toolchain that lets all subsequent work happen\nsafely. The goal is \"next round of changes can't make things worse\" —\nevery commit gets formatted, linted, type-checked, and (optionally)\ntested before it lands.\n\nNo behavior changes in Phase 1. Just the rails.\n\n## What gets installed\n\nFor a JS\u002FTS\u002FReact project, the convergent stack is:\n\n| Tool | Purpose | Template |\n|---|---|---|\n| ESLint flat config | Lint | `templates\u002Feslint.config.flat.{js,react.js}` |\n| Prettier | Format | `templates\u002Fprettierrc.json` |\n| TypeScript `checkJs` | Type check w\u002Fo rename | `templates\u002Ftsconfig.checkjs.json` |\n| Husky | Git hooks | (run `npx husky init`) |\n| lint-staged | Run hooks on staged files only | (in `package.json`) |\n| Vitest | Test runner | `templates\u002Fvitest.config.with-cleanup.js` |\n| jest-dom + cleanup | Strict DOM matchers + leak prevention | `templates\u002Ftest-setup.js` |\n\nFor Python: switch ESLint+Prettier to `ruff` + `black` + `usort`,\nTypeScript to `pyright` or `mypy`, vitest to `pytest`. Same shape.\n\n## Step-by-step (JS\u002FTS\u002FReact project)\n\n### 1. Detect existing setup\n\nRead `package.json`. If ESLint \u002F Prettier \u002F etc. already exist —\nASK the user before overwriting. Their config might be intentional.\n\n### 2. Install dev dependencies\n\n```bash\nnpm install --save-dev \\\n  eslint @eslint\u002Fjs globals \\\n  prettier eslint-config-prettier \\\n  husky lint-staged \\\n  typescript @types\u002Fnode\n```\n\nFor React projects (note: `eslint-plugin-react` peer-deps cap at\nESLint 9; pin if needed):\n\n```bash\nnpm install --save-dev eslint@^9 @eslint\u002Fjs@^9 \\\n  eslint-plugin-react eslint-plugin-react-hooks \\\n  @types\u002Freact @types\u002Freact-dom\n```\n\nFor testing:\n\n```bash\nnpm install --save-dev vitest jsdom \\\n  @vitejs\u002Fplugin-react \\\n  @testing-library\u002Freact @testing-library\u002Fjest-dom @testing-library\u002Fuser-event\n```\n\nFor Node-only projects, also:\n\n```bash\nnpm install --save-dev eslint-plugin-security\n```\n\n### 3. Drop in templates\n\nCopy the following from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002F` to the\nproject root (or matching path):\n\n- `eslint.config.flat.js` (or `.react.js`) → `eslint.config.js`\n- `prettierrc.json` → `.prettierrc.json`\n- `tsconfig.checkjs.json` → `tsconfig.json`\n- `vitest.config.with-cleanup.js` → `vitest.config.js`\n- `test-setup.js` → `src\u002F__tests__\u002Fsetup.js`\n\nAdd a `.prettierignore`:\n\n```\nnode_modules\u002F\ndist\u002F\nbuild\u002F\ncoverage\u002F\npackage-lock.json\n*.md\n```\n\n### 4. Add scripts to package.json\n\n```json\n{\n  \"scripts\": {\n    \"lint\": \"eslint .\",\n    \"lint:fix\": \"eslint . --fix\",\n    \"format\": \"prettier --write .\",\n    \"format:check\": \"prettier --check .\",\n    \"typecheck\": \"tsc --noEmit\",\n    \"test\": \"vitest run\",\n    \"test:watch\": \"vitest\",\n    \"prepare\": \"husky\"\n  },\n  \"lint-staged\": {\n    \"*.{js,jsx,ts,tsx}\": [\"eslint --fix\", \"prettier --write\"],\n    \"*.{json,md,yml,yaml,css}\": [\"prettier --write\"]\n  }\n}\n```\n\n### 5. Initialize Husky\n\n```bash\nnpx husky init\n```\n\nReplace the default `.husky\u002Fpre-commit` content with:\n\n```\nnpx lint-staged\n```\n\nAdd `.husky\u002F_\u002F` to `.gitignore` (auto-regenerated by husky).\n\n### 6. Run prettier --write . once\n\nThis is the only Phase 1 step that touches existing files. Commit\nthe result as a SEPARATE, formatting-only commit so subsequent diffs\nstay reviewable:\n\n```bash\nnpx prettier --write .\ngit add -A\ngit commit -m \"chore(phase1): apply prettier formatting pass\n\nApply project-wide Prettier formatting per the new config. No\nbehavior change. Subsequent commits are content changes only.\n\nAssisted-by: Claude (claude-tdd-pro 0.3.0)\"\n```\n\n### 7. Verify everything works\n\n```bash\nnpm run lint           # may have warnings; should not have errors\nnpm run format:check   # should pass\nnpm run typecheck      # may have errors; record baseline\nnpm test               # if any tests exist; should pass\n```\n\nCapture baseline numbers (lint errors\u002Fwarnings, typecheck errors)\nin a final commit summary.\n\n### 8. Final commit + REMEDIATION.md update\n\n```bash\ngit add eslint.config.js .prettierrc.json .prettierignore \\\n        tsconfig.json vitest.config.js src\u002F__tests__\u002Fsetup.js \\\n        package.json package-lock.json .husky\u002Fpre-commit .gitignore\ngit commit -m \"chore(phase1): install guardrails (eslint + prettier + tsconfig + husky + vitest)\n\nPhase 1 of REMEDIATION. Adds:\n- ESLint flat config (with security\u002Freact\u002Freact-hooks plugins as applicable)\n- Prettier with project-wide style\n- TypeScript in checkJs mode (no file rename)\n- Husky 9 pre-commit hook running lint-staged\n- Vitest + jest-dom matchers + cleanup discipline\n\nBaseline: lint NN warnings (0 errors), tsc NN errors (will address\nin Phase 3), tests NN\u002FNN passing.\n\nNo behavior change.\n\nAssisted-by: Claude (claude-tdd-pro 0.3.0)\"\n```\n\nUpdate REMEDIATION.md to check off the Phase 1 items.\n\n## What to refuse\n\n- **\"Add Snyk \u002F Semgrep \u002F SonarQube\"** — overkill for the typical\n  small project; the standard `npm audit` + `eslint-plugin-security`\n  is enough. If the user really wants enterprise security tooling,\n  fine, but don't proactively suggest it.\n- **\"Configure CI to auto-fix and push back\"** — refuse (see the\n  `reject-bad-tooling` skill).\n- **\"Run `npm audit fix --force`\"** — refuse. Plain `npm audit fix`\n  only.\n- **\"Skip the formatting commit; just bundle it with feature work\"**\n  — refuse. The formatting commit must be its own commit so future\n  diffs stay reviewable.\n\n## What to defer\n\n- **The 1600-line god-file decomposition** — that's Phase 4, not now.\n  Phase 1 only adds the toolchain; the existing code stays untouched\n  except for prettier formatting.\n- **Fixing the lint warnings** — Phase 1 records the baseline. Phase 3\n  fixes the named bugs (which often resolve many warnings as a side\n  effect). Don't try to fix warnings as part of Phase 1.\n- **Major dependency upgrades** — Phase 5 deals with that. Phase 1\n  uses whatever versions are already in the project.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","41c38db9b8cf2d5b7743093654a12fdd9cd59c03","skills\u002Fphase-1-guardrails","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro","https:\u002F\u002Fgithub.com\u002Fdrumfiend21","http:\u002F\u002Fjungleej.wordpress.com","2026-11-09 20:29:03",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add drumfiend21\u002Fclaude-tdd-pro --skill phase-1-guardrails",{"tool":38,"command":39},"bunx","bunx skills add drumfiend21\u002Fclaude-tdd-pro --skill phase-1-guardrails",{"tool":41,"command":42},"pnpm","pnpm dlx skills add drumfiend21\u002Fclaude-tdd-pro --skill phase-1-guardrails","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Fphase-1-guardrails\u002FSKILL.md",[],[46,53,60,67,74,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M74HHPZCJM1SJFPMAT28GZ1S","test-first-extract","Use when the user asks to EXTRACT or RELOCATE existing code into its own file, module, or component (\"extract X\", \"split out Y\", \"pull Z into its own file\", \"decompose god-file\"). NOT for net-new features (use tdd-feature-build) or behavior changes (use fix-bug). Enforces the 9-step extraction with isolated unit tests + integration regression tests as a two-tier safety net.","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Ftest-first-extract\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M74HHK1QJ5APDRM7WWMC90X9","tdd-feature-build","Use when the user describes a NEW feature to add (\"add X to Y\", \"implement Z\", \"build a feature that…\", \"make it possible to…\"). Enforces TDD — failing test first, minimum code to pass, refactor. Refuses to ship code without a test that demonstrably catches its absence. Does NOT trigger on bug fixes (use bug-fix-discipline) or refactors (use test-first-extract). Will ask 1-3 clarifying questions before writing any code; safe to delegate from \u002Ffeature command.","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Ftdd-feature-build\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M74HHEXN1MK9SK9JDGN52YDJ","sync","Multi-machine git-backed sync of local TDD Pro state via the `tdd-pro-sync` branch. Use when operators run claude-tdd-pro on more than one machine and want their FAILURE-LOG, decisions, audit checkpoints, workflow state, operator-curated URL registries, operator\u002Fcommunity trees, and paywalled attestations to follow them between hosts.","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Fsync\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74HHBQ8K1FNZ5AXTEGGF8RW","strict-component-tests","Use when writing or reviewing test files. Enforces strict assertions that actually catch regressions (getByRole, exact counts, jest-dom matchers) in contrast to permissive tests (queryAllByText length > 0) that pass against broken UIs. References QUALITY-BAR.md for the canonical strictness rules.","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Fstrict-component-tests\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74HHA5W00JK570KTA68MRZD","spec","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74HH5HR9S2Q6HRAW0GTXATA","spec-first","Use when the user describes a non-trivial feature or system that should be specified in writing before any code is written. Pattern from Geoffrey Huntley's \"Ralph\" loop, OpenSpec, intent-driven.dev, and Kent Beck's \"augmented coding\" framing — specs+tests are the durable artifact, code is the disposable one. Produces a Markdown spec document that the user reviews; only after approval does any code get written (typically via tdd-feature-build or \u002Ffeature).","https:\u002F\u002Fgithub.com\u002Fdrumfiend21\u002Fclaude-tdd-pro\u002Fblob\u002Fmain\u002Fskills\u002Fspec-first\u002FSKILL.md",[],[]]