claude-prompts-mcp: Instructions file for Claude Code

Agent Rules · Claude Prompts MCP

Canonical ownership and loading

• Edit CLAUDE.md and .claude/rules/*.md; do not edit this generated file.
• This compact file is the default Codex/OpenCode context. It preserves the project-wide decisions that change most tasks while staying within Codex's documented default 32 KiB project guidance budget.
• Claude Code applies rule paths: natively. Codex and OpenCode do not, so use the dispatch table below: when a task touches a matching path, read that canonical rule before editing.
• For project details not projected here, consult CLAUDE.md and its documentation pointers.

Core Principles

1. MCP Tooling Only -- Prompts, templates, chains flow through MCP tools. Manual edits under server/prompts/** forbidden.
2. Contract ownership -- Hand-written schemas in src/mcp/tools/schemas/ own runtime validation; tooling/contracts/*.json own descriptions/parameter metadata generated into src/mcp/contracts/schemas/_generated/. Run npm run generate:contracts, never edit _generated/. config.schema.json <- ConfigFile (generate:config-schema).
3. Transport Parity -- Runtime changes must work in STDIO and Streamable HTTP. The two differ in instance lifetime, and that difference is load-bearing: STDIO pins one McpServer per connection, while HTTP builds a fresh one per request. A change that mutates a registered instance passes STDIO and silently no-ops over HTTP. HTTP+SSE was removed in the SDK v2 upgrade.
4. Docs/Code Lockstep -- Update relevant doc in docs/ when behavior changes.
5. Validation Discipline -- CI owns the full test suite; local checks are a subset chosen by who is running them. A change's own check (the test, validator or probe that reads what the change wrote) runs with the change, and nothing wider. Before a push: npm run typecheck && npm run lint:ratchet && npm run typecheck:tests:ratchet && npm run validate:all. test:all (unit, integration and e2e) runs once, in CI, at the pull request; a red run is fixed on the branch, never merged around. Run test:all locally only to reproduce a CI failure or when no pull request will carry the change. typecheck:tests:ratchet is not optional: tsconfig.json excludes tests/, so typecheck is blind to every call site a signature change breaks. test:ci is an alias for test:unit and says nothing about the integration or e2e jobs. Owner ruling 2026-10-05, after a profile measured the full suite running three times in series per change while CI was green on 32 of 33 pull requests. (flips when a defect reaches main that a local test:all would have caught and the pull request's CI did not)