Every feature or behavior change follows this loop. Do not skip steps. Ask before moving to the next one.
1. SPECIFY — agree on what to build, in plain language
2. RED — generate failing tests; wait for human approval before continuing
3. PROMPT — generate the implementation using the approved tests as the spec
4. GREEN — tests pass; do not weaken assertions to force it
5. REVIEW — check naming, single responsibility, duplication, dead code
6. REFACTOR — apply what review found; tests stay green throughout
7. COMMIT — one small focused commit with a clear why
- Always ask before moving to the next step. Never chain steps.
- Generate tests first. Wait for approval. Then generate the implementation.
- If a test fails, fix the implementation or the spec. Never change the test to make it pass.
- One behavior per cycle. If the prompt grows, split the cycle.
- Style changes (layout, colors) do not need a full cycle. Confirm with the user and apply.
- Always check an existing similar component before generating anything.
Lightweight SSE (Server-Sent Events) relay for the footballproject platform. Polls the backend API for live match events and live charts data, and broadcasts it in real-time to connected clients.
Method reference: TDCG/README.md