docs(repo): design a feature's screens in its spec and check them in a browser #555

Merged

root merged 1 commit from docs/screens-in-specs into main

2026-10-19 09:56:31 +00:00

root commented

2026-10-19 09:51:23 +00:00

(Migrated from gitlab.core-project.space)

Summary

The Puzzles spec (#440) named every story, seam and contract but no screen, so the page was built on the bare board: no move list, an aside of its own, no entry page, no result dialog. This puts screen design into the flow, before the spec and after the code.

 idea
   grill-with-docs
+  prototype (UI)          # only for a screen no page template fits
   to-spec
+    ## Screens            # per route or dialog: entry and exit, template, wireframe, every state
   implement / implement-spec
     tdd at the seams
+    browser check         # every listed state at 1280 and 390 px, screenshots as Evidence
     code-review

to-spec: a Screens section, and every state of every screen in a user story.
implement and implement-spec: forked (out of skills-lock.json, listed in docs/agents/skills.md). implement owns the browser check, and implement-spec points to it before its review.
apps/front/CODING_STANDARDS.md, review rule 8: a page is built on GameScreen, PageFrame, AuthPage or a home door, and fills each region. The old rule 8 is now 9.
docs/agents/issue-tracker.md: uploading a screenshot into a merge request description.

Evidence

Only docs and skills change. The five gate commands are green.

Merge Danger

Door: two-way

Blast Radius: agent workflow. Specs with front work get longer, and implement gets one more step. implement and implement-spec no longer take upstream updates.

## Summary The Puzzles spec (#440) named every story, seam and contract but no screen, so the page was built on the bare board: no move list, an aside of its own, no entry page, no result dialog. This puts screen design into the flow, before the spec and after the code. ```diff idea grill-with-docs + prototype (UI) # only for a screen no page template fits to-spec + ## Screens # per route or dialog: entry and exit, template, wireframe, every state implement / implement-spec tdd at the seams + browser check # every listed state at 1280 and 390 px, screenshots as Evidence code-review ``` - `to-spec`: a Screens section, and every state of every screen in a user story. - `implement` and `implement-spec`: forked (out of `skills-lock.json`, listed in `docs/agents/skills.md`). `implement` owns the browser check, and `implement-spec` points to it before its review. - `apps/front/CODING_STANDARDS.md`, review rule 8: a page is built on `GameScreen`, `PageFrame`, `AuthPage` or a home door, and fills each region. The old rule 8 is now 9. - `docs/agents/issue-tracker.md`: uploading a screenshot into a merge request description. ## Evidence Only docs and skills change. The five gate commands are green. ## Merge Danger **Door:** two-way **Blast Radius:** agent workflow. Specs with front work get longer, and `implement` gets one more step. `implement` and `implement-spec` no longer take upstream updates.

root commented

2026-10-19 09:55:39 +00:00

(Migrated from gitlab.core-project.space)

added 51 commits

b8ba2685...f3dc8a8a - 50 commits from branch main
29a22631 - docs(repo): design a feature's screens in its spec and check them in a browser

Compare with previous version

added 51 commits <ul><li>b8ba2685...f3dc8a8a - 50 commits from branch <code>main</code></li><li>29a22631 - docs(repo): design a feature's screens in its spec and check them in a browser</li></ul> [Compare with previous version](/amaurycoudr/chess-project/-/merge_requests/55/diffs?diff_id=342&start_sha=b8ba26850c4a67500f5058721df6c3f78e819045)

root (Migrated from gitlab.core-project.space) merged commit into main

2026-10-19 09:56:31 +00:00