ralph-prd 1.1.0 → 1.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -23,18 +23,24 @@ Your job is to implement exactly the phase described below and nothing more.
|
|
|
23
23
|
|
|
24
24
|
## Implementation approach
|
|
25
25
|
|
|
26
|
-
|
|
27
|
-
Follow a strict red → green → refactor cycle, one behaviour at a time:
|
|
26
|
+
### Tracer-bullet principle
|
|
28
27
|
|
|
29
|
-
|
|
30
|
-
2. **GREEN** — Write the minimum production code to make that one test pass. Nothing more.
|
|
31
|
-
3. **REFACTOR** — Clean up without changing behaviour. Re-run tests to confirm they still pass.
|
|
32
|
-
4. Repeat for the next behaviour.
|
|
28
|
+
Build one thin vertical slice end-to-end before writing the next. A tracer bullet pierces all layers — route → handler → service → database — for a single behaviour, proving the path works before you widen it. Do not build all routes first, then all handlers, then all services. Build one complete behaviour at a time.
|
|
33
29
|
|
|
34
|
-
|
|
35
|
-
Do NOT write multiple tests upfront. Do NOT write production code before a failing test exists.
|
|
30
|
+
### For backend code (server logic, API routes, business logic, database layers, services, data models, utilities)
|
|
36
31
|
|
|
37
|
-
|
|
32
|
+
Apply red → green → refactor within each tracer bullet:
|
|
33
|
+
|
|
34
|
+
1. **RED** — Write one failing test for the behaviour this slice delivers. Run it to confirm it fails before writing any production code.
|
|
35
|
+
2. **GREEN** — Write the minimum production code across all layers to make that one test pass. Nothing more.
|
|
36
|
+
3. Repeat from step 1 for the next slice of behaviour.
|
|
37
|
+
4. **REFACTOR** — Clean up without changing behaviour. Re-run tests to confirm they still pass.
|
|
38
|
+
|
|
39
|
+
Do NOT write multiple tests upfront. Do NOT build out a full layer before proving a slice works end-to-end.
|
|
40
|
+
|
|
41
|
+
### Frontend code (UI components, CSS, HTML, browser JS, view templates)
|
|
42
|
+
|
|
43
|
+
Exempt from the TDD cycle — implement it directly. Still follow the tracer-bullet principle: one complete UI slice at a time, not all markup then all styles then all scripts.
|
|
38
44
|
|
|
39
45
|
---
|
|
40
46
|
|