description:**
```yaml
description: Use for debugging. First investigate root cause, then analyze
patterns, test hypotheses, and implement fixes with tests.
```
**GOOD - Capability + trigger:**
```yaml
description: Diagnoses bugs through root cause
formatting (Prettier) and linting (ESLint)
npm run format # Auto-format with Prettier
npm run test # Run all tests (Vitest)
```
### Running a Single Test
```bash
npx vitest run path/to/file.spec.ts # Run specific
with IdeaVim.
## Quick Reference
Essential commands:
- `./gradlew runIde` - Start dev IntelliJ with IdeaVim
- `./gradlew test -x :tests:property-tests:test -x :tests:long-running-tests:test` - Run standard tests
Avoid
server
npm run build # TypeScript compile + Vite build
npm run lint # ESLint
npm run test # Vitest watch mode
npm run test:run # Vitest single run
npm run preview # Preview production
priority + dependency order), runs the loop via `RALPH_LOOP_CMD` (default `ralph_loop.sh`; overridable for tests), commits `Fix #N: ` per issue, skips failures (or halts), and writes `.ralph/logs/queue_processing.log`. Single branch
WARN issue (Cal. Lab. Code §1400) — California requires 60 days notice before large layoffs." Test: could the reader take the output to their boss and explain it without a lawyer
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
WARN issue (Cal. Lab. Code §1400) — California requires 60 days notice before large layoffs." Test: could the reader take the output to their boss and explain it without a lawyer
WARN issue (Cal. Lab. Code §1400) — California requires 60 days notice before large layoffs." Test: could the reader take the output to their boss and explain it without a lawyer
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
WARN issue (Cal. Lab. Code §1400) — California requires 60 days notice before large layoffs." Test: could the reader take the output to their supervising attorney and explain it without
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
item issue list, a memo, a redline, a client letter. Use judgment — the test is "would a reader struggle to see the shape of this in text."
**Dashboard outputs escape
migrations
- **exposed-spring-boot-starter**: Spring Boot integration
- **spring-transaction**: Spring Framework transaction manager
### Test Modules
- **exposed-tests**: Main JDBC-based test suite
- **exposed-r2dbc-tests**: R2DBC-specific test suite
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.