senior-dev-kit: Instructions file for Claude Code

senior-dev-kit — repo CLAUDE.md

This is a publicly distributed Claude Code config kit (MIT, installable as a plugin — see README.md and CONTRIBUTING.md). Every change ships to strangers: assume no shared context, no ability to ask the maintainer, and a machine that is not this one.

global-CLAUDE.md and presets/*/CLAUDE.md are templates installed into ~/.claude/ or a project's .claude/ — don't confuse them with this file, which is scoped to editing the kit itself.

Commands

• Test: npm test (targeted: node --experimental-strip-types --test scripts/<file>.test.ts)
• Validate frontmatter/routing: npm run validate
• Full gate (run before considering any change done): npm run check — runs test, validate, link-check, consistency-check, docs-check, routing-eval, behavior-eval, check-plugin, check-install, typecheck, lint, markdown-lint, audit — routing-eval and behavior-eval are the only two steps that measure model behavior rather than file contents, and both score live only under their env flag (RUN_ROUTING_EVAL=1, RUN_BEHAVIOR_EVAL=1; in PowerShell set $env:NAME=1 first — there is no inline prefix form) — check-install is the only step that looks outside the repo: it compares ~/.claude with this checkout and fails when the installed copy is behind. Every other step verifies the repo against itself, which is how a green gate once coexisted with a day-old install running the content the work had just replaced. It skips loudly where there is no copy install.
• Type-check only: npm run typecheck | Lint only: npm run lint
• Installer dry run: node scripts/install.mjs --dry-run
• Landing page: not on this branch. The page source lives on the site-src branch and the rendered output on gh-pages; a clone of the kit carries neither, because nobody installing a Claude Code configuration kit needs a website. site/ is git-ignored here and is the path that branch gets checked out into — git worktree add site site-src to work on it. .github/workflows/site.yml checks out both branches, renders, and force-pushes a single orphan commit to gh-pages; pushing to either branch publishes.
• The split does not weaken the derivation: every number the page states is read from this branch's contents at build time by scripts/gen-site.ts (agent/skill/preset counts, deny rules, the always-loaded line budget, the gate's own step list). site-check and consistency check 28 therefore run in that workflow, not in npm run check — check 28 says so out loud when it scans nothing, rather than passing silently.
• The site-src templates and style.css keep their contributor comments even though global-CLAUDE.md's CODE STYLE forbids comments in every file: nothing on that branch is served as-is. gen-site.ts strips every one at build time (stripTemplateNote / stripPartialNote / stripCssComments), and site-check fails the publish if any survives into an artifact. Write the rationale in the source; the visitor never receives it. Do not re-open this as a rule violation.