Revision 6 of 16
Adds the Technical specification and checklist section: commit a spec with a verifiable checkbox per requirement and reconcile it before finishing.
+14 −2 lines of text vs revision 5 (this site's diff)
| Old | New | Change | Line |
|---|---|---|---|
| @@ -4,6 +4,18 @@ | |||
| 4 | 4 | ||
| 5 | 5 | If a minor detail is not specified, choose a reasonable solution and document it. Do not copy an existing implementation of The Urlist. | |
| 6 | 6 | ||
| 7 | + | ## Technical specification and checklist | |
| 8 | + | ||
| 9 | + | Before coding, create and commit `TECHNICAL_SPEC.md`. Keep it concise; do not restate this document. | |
| 10 | + | ||
| 11 | + | It must contain: | |
| 12 | + | ||
| 13 | + | - Architecture, data model, routes/API, security boundaries, and key assumptions | |
| 14 | + | - An atomic Markdown checkbox for every requirement in this document, grouped by feature | |
| 15 | + | - A verification method on every checkbox: unit test, browser test, command, or direct inspection | |
| 16 | + | ||
| 17 | + | Use the format `- [ ] Requirement — Verify: method`. Maintain it throughout implementation. Check an item only after its implementation exists and its verification passes; reopen it if later work breaks it. Before finishing, resolve every unchecked item or leave it unchecked and report the exact blocker. | |
| 18 | + | ||
| 7 | 19 | ## Stack and design | |
| 8 | 20 | ||
| 9 | 21 | Use: | |
| @@ -191,7 +203,7 @@ | |||
| 191 | 203 | 2. Start the production build and confirm the app responds. | |
| 192 | 204 | 3. In a real Chromium browser, complete every user journey: anonymous publication; login/logout for both users; owned-list create/edit/drag-reorder/delete/restore; non-owner denial; public links/QR/sharing; themes; and desktop/mobile layouts. | |
| 193 | 205 | 4. Confirm active, anonymous, and deleted data survives restart. | |
| 194 | − | 5. Review this entire instruction and fix every missing or incorrect requirement. | |
| 195 | − | 6. Repeat affected validation. | |
| 206 | + | 5. Reconcile `TECHNICAL_SPEC.md` against this instruction, fix every missing or incorrect requirement, and confirm each checked item has evidence. | |
| 207 | + | 6. Repeat affected validation and leave no unchecked item unless it has a reported external blocker. | |
| 196 | 208 | ||
| 197 | 209 | Report what you built, assumptions, architecture, exact command results, and anything incomplete with its reason. Do not claim a check passed unless you ran it successfully. | |