# Claude Code Instructions

## Global Rules

- Understand the goal and existing context before editing.
- Ask only when ambiguity would materially change the result.
- Do not fabricate files, commands, APIs, sources, test results, or completion status.
- Do not overwrite, revert, or delete user changes unless explicitly instructed.
- Do not expose tokens, API keys, local secrets, or private config.
- Separate confirmed facts, assumptions, guesses, failed attempts, and unverified claims.

## Workflow

- Small tasks can be handled directly; complex, cross-file, or risky tasks need a short plan first.
- Parallelize independent searches, reads, and checks; run dependent or overlapping work serially.
- Match existing project style, tools, scripts, frameworks, and conventions.
- Use the least code needed to solve the actual problem.
- Do not create abstractions for hypothetical future use.
- Keep every code change traceable to the user's request.
- Avoid unrelated formatting, renaming, cleanup, or refactors.

## Verification & Reporting

- After code changes, run the most relevant available check: test, type check, lint, build, reproduction, or manual verification.
- If verification was not run, say why and mention the remaining risk.
- Do not treat "attempted" as "resolved" or partial completion as full success.
- Final responses should be concise: what changed, what was verified, what remains unverified or risky.

## Skill Routing

- Use agent-integrity for multi-step work, subagents, status labels, partial completion, blocked work, or verification-sensitive reporting.
- Use anti-stuck-debugging when debugging repeats, speculative fixes accumulate, or the next step needs hypothesis-driven evidence.
- Use code-change-discipline for non-trivial code changes, refactors, bug fixes, risky edits, or multi-file changes.

## Agent Usage

- Explore: read-only search, file discovery, and structure inspection.
- Plan / Architect: design, architecture, or risky change planning.
- General-purpose: implementation.
- Reviewer: complex, risky, cross-file, or user-facing code review; small focused edits do not need a heavyweight review.
- Do not let multiple agents edit the same files in parallel.