···

       
7
       
7
       
 
       
- Security is built-in, not bolted-on

     

       
8
       
8
       
 
       
- Test-driven: write the test, then make it pass

     

       
9
       
9
       
 
       
- ASK QUESTIONS if you need context surrounding the product DONT ASSUME

     

       
10
       
10
       
+
       


     

       
10
       
11
       
 
       
## No Stubs, No Shortcuts

     

       
11
       
12
       
 
       
- **NEVER** use `unimplemented!()`, `todo!()`, or stub implementations

     

       
12
       
13
       
 
       
- **NEVER** leave placeholder code or incomplete implementations

     
···

       
15
       
16
       
 
       
- Every feature must be complete before moving on

     

       
16
       
17
       
 
       
- E2E tests must test REAL infrastructure - not mocks

     

       
17
       
18
       
 
       


     

       
19
       
19
       
+
       
## Issue Tracking

     

       
20
       
20
       
+
       


     

       
21
       
21
       
+
       
**This project uses [bd (beads)](https://github.com/steveyegge/beads) for ALL issue tracking.**

     

       
22
       
22
       
+
       


     

       
23
       
23
       
+
       
- Use `bd` commands, NOT markdown TODOs or task lists

     

       
24
       
24
       
+
       
- Check `bd ready` for unblocked work

     

       
25
       
25
       
+
       
- Always commit `.beads/issues.jsonl` with code changes

     

       
26
       
26
       
+
       
- See [AGENTS.md](AGENTS.md) for full workflow details

     

       
27
       
27
       
+
       


     

       
28
       
28
       
+
       
Quick commands:

     

       
29
       
29
       
+
       
- `bd ready --json` - Show ready work

     

       
30
       
30
       
+
       
- `bd create "Title" -t bug|feature|task -p 0-4 --json` - Create issue

     

       
31
       
31
       
+
       
- `bd update <id> --status in_progress --json` - Claim work

     

       
32
       
32
       
+
       
- `bd close <id> --reason "Done" --json` - Complete work

     

       
18
       
33
       
 
       
## Break Down Complex Tasks

     

       
19
       
34
       
 
       
- Large files or complex features should be broken into manageable chunks

     

       
20
       
35
       
 
       
- If a file is too large, discuss breaking it into smaller modules