Coding · guidance updated 22 Nov 2026
Claude Code prompt guide
Fable 5.2 default via /model fable or claude --model fable (except Claude apps gateway: use /model claude-fable-5-2). Sonnet/Opus 5.5 and Haiku 5.5 on Anthropic API. Skip verification reminders with Fable; describe outcomes not steps.
How to prompt Claude Code
- Distinguish deterministic (hooks, deny rules, stops) from non-deterministic (prompts, CLAUDE.md, skills)—use deterministic only for what must always happen.
- Give Claude a runnable check and ask it to iterate until the check passes.
- Scope precisely: file, scenario, constraints, and what 'done' means.
- For ambiguous problems or large features, use Fable with outcome descriptions, not step-by-step instructions.
- Reference files with @path; point to existing patterns to copy.
- For bugs, provide symptom, likely location, error text, and ask for a failing test before the fix.
- For multi-file work, explore and plan first; skip planning if the diff fits in one sentence.
- Ask Claude to fix root causes, not suppress errors.
- Use subagents for wide investigations to keep main context clean.
- Tell Claude only what it can't find by reading the repo or would rediscover every session.
- Set /goal conditions to gate unattended runs; use /verify after the check passes.
- Run /clear between unrelated tasks; after two failed corrections, rewrite the prompt.
The shape of a good prompt
[Task and why] [Context: @files, pattern to follow, constraints] [Requirements / edge cases] [Verification: runnable check, iterate until pass, show evidence] [Process: deterministic rules needed? plan first? subagents? Fable for ambiguous/large work? /goal gate?] [Deliverable: commit/PR, evidence]
Avoid
- Unscoped 'investigate X' prompts that read hundreds of files.
- Tasks with no way for Claude to verify its own work.
- A long CLAUDE.md full of things Claude can infer from code.
- Mixing unrelated tasks in one session.
- Asserting success without showing evidence of the check passing.
- Giving Fable step-by-step instructions instead of describing desired outcomes.
- Using sonnet[1m] or opus[1m] when already on Sonnet 5.5, Opus 5.5, Opus 4.7+ (native 1M windows).
- Adding emphasis to CLAUDE.md lines repeatedly instead of moving them to hooks when compliance matters.
Example
Request add rate limiting to our API
Add per-IP rate limiting to the public API. Context: middleware lives in @src/middleware/; follow the structure of @src/middleware/requestLogger.ts. Routes are registered in @src/app.ts. Requirements: - 100 requests/minute per IP on /api/*; /health exempt - Return 429 with a Retry-After header and our standard JSON error shape - Use the existing Redis client in src/lib/redis.ts; no new dependencies First explore and give me a short plan of files to change. After I approve: implement, add tests covering under-limit, at-limit, over-limit and the /health exemption, run `npm test` and `npm run typecheck`, and iterate until both pass. Show me the test output.