Using Claude Code for code generation, refactoring, debugging, and documentation — integrated via custom slash commands and CLAUDE.md, choosing plan mode vs direct execution.
A /review command every developer should get on clone/pull belongs in .claude/commands/ (project, version-controlled) — not ~/.claude/commands/ (personal), not CLAUDE.md, and not a nonexistent config.json.
Monolith→microservices (dozens of files, service boundaries, multiple valid approaches) → plan mode to explore/design first. A single-file bug fix with a clear stack trace → direct execution.
Different conventions per area, with test files spread everywhere → .claude/rules/ with glob paths: (e.g., **/*.test.tsx). This applies automatically by path, unlike directory-bound CLAUDE.md or manually-invoked skills.
Use the Explore subagent for verbose discovery, scratchpad files for key findings, and /compact when context fills.
1.Where do you put a code-review slash command so every developer gets it on pull?
2.Different areas have different conventions and tests are scattered everywhere. Most maintainable way to auto-apply the right conventions?
3.For a single-file bug fix with a clear stack trace, which mode is appropriate?
4.A single-pass review of a 14-file PR gives inconsistent, contradictory feedback. Best restructuring?
5.You're restructuring a monolith into microservices — dozens of files, service boundaries, and multiple valid approaches. Which mode?
6.The requirements already state the change spans dozens of files and service boundaries. Is 'start direct, switch to plan mode later' a good approach?
7.Where does a personal, experimental slash command belong so it doesn't affect teammates?
8.Different areas have different conventions and test files are scattered across many directories. What auto-applies the right conventions?
9.A teammate reports the agent ignores an instruction that works fine on your machine. Most likely cause?
10.During a long session, context is filling up with verbose discovery output. Which combination helps most?
11.An Edit fails because its anchor text appears in several places in the file. Best recovery?
12.A /review command should reach every developer automatically on clone/pull. Where does it go?
13.A single-file bug fix with a clear stack trace lands on your desk. Which mode?
14.Your root CLAUDE.md has grown huge. Which keeps it modular without losing standards?
15.Behavior differs between two of your sessions and you can't tell why. Fastest diagnostic?