Claude Code v2.1
← Referinta

Cheat Sheet — Claude Code CLI v2.1

Start sesiune

1. Citeste STATE.md          → unde suntem?
2. Verifica docs/30-sessions/ → ce s-a facut ultima data?
3. Citeste ROADMAP.md        → imaginea de ansamblu
4. Identifica ONE next action → incepe

Workflow PAUL

PLAN → Intelege + descompune + scrie .planning/phases/NNN/PLAN.md
Fiecare task: fisiere | actiune | verificare | done
Max 2-3 task-uri per plan
APPLY → TDD: scrie test FAIL → cod minimal → test PASS → commit
Dupa 3 esecuri consecutive → STOP → reconsidera
UNIFY → Am atins ce era planificat?
Update STATE.md + full tests + update ROADMAP
Daca incomplet → PLAN nou

Comenzi slash

ComandaCe face
/obsidian:syncSincronizeaza sesiunea in vault
/obsidian:dailyCreeaza/update daily note
/adr:new [titlu]Creeaza Architecture Decision Record
/compactCompacteaza contextul (la breakpoints)
/clearSterge contextul (intre task-uri necorelate)

Cele 6 layere de memorie

1. CLAUDE.md           mereu incarcat
2. MEMORY.md           primele 200 linii auto
3. .claude/memory.json   knowledge graph MCP
4. .planning/STATE.md    sursa de adevar
5. --continue/--resume   sesiune activa
6. docs/ (Obsidian)      vault vizual

Git commits

feat:      functionalitate noua
fix:       bug fix
docs:      documentatie
chore:     maintenance
refactor: restructurare fara schimbare comportament
test:      teste noi sau fix teste

O schimbare logica per commit. Mesaj = DE CE, nu CE.

Fisiere cheie

FisierCand il citesti
.planning/STATE.mdLa FIECARE start de sesiune
.planning/ROADMAP.mdCand vrei imaginea de ansamblu
CLAUDE.mdCand modifici regulile agentului
docs/10-gsd/backlog.mdCand vrei sa vezi task-urile
docs/20-architecture/OVERVIEW.mdCand ai nevoie de context arhitectural

Stop sesiune

1. Commit toata munca
2. Update STATE.md (pozitie + next action)
3. /obsidian:sync
4. /compact daca context > 60%

Anti-patterns (NU face)