← ClaudeAtlas

design-summary-htmllisted

Builds docs/design/summary.html, one light-mode page for grasping the direction of the design quickly from the outputs of the req-to-design 0.3.0 chain (requirements-to-architecture-drivers → architecture-drivers-to-architecture → architecture-to-technical-policy → architecture-to-high-level-design), in quality-summary-html's layout with its own orange theme. As in quality-summary-html, a bundled script renders the page from the YAML items (drivers, design context, elements, decisions with their options and consequences, technical policies, interfaces, error contracts, SLI bindings, data entities, design parameters, debt, open hand-offs), takes the Mermaid diagrams and the tables no item holds from the reports, leaves the reports' prose out, cuts every text, table cell and diagram label to its gist (the first sentence, without bracketed asides; the YAML and the reports keep the rest), and reports where a report disagrees with the YAML, so every project and every re-run gets the same page with no hand-written
Taro000/chain-summary-html · ★ 0 · Web & Frontend · score 72
Install: claude install-skill Taro000/chain-summary-html
# Design summary HTML Renders `docs/design/summary.html` from the design chain's outputs so that a person can grasp the direction of the design quickly: the ranked architecture drivers, the elements and views, every decision with its options and consequences, the threat model, the walkthroughs, the technical policy (the stack, repositories, test layers, pipeline and specs), the high-level design's interfaces, error contracts, SLI bindings, end-to-end flows, latency budgets, screens, data and states, and what each stage handed off and has not been decided yet. The page is not for the full picture: it shows the gist of every text, and whoever needs the whole of one reads the YAML item (the source of truth) or the report. The page design and the set of tables are fixed, and `scripts/build_design_summary.py` does all of the rendering, from the outputs alone: nothing on the page is written by hand. The layout is quality-summary-html's (`assets/base.css` and `assets/base.js` are copies of its `summary.css` and `summary.js`); `assets/design.css` gives the page an orange theme and the parts the design page needs, and `assets/design.js` draws the diagrams. The page uses as little color as quality-summary-html: one orange from this skill's icon where quality-summary-html uses its blue, and neutrals everywhere else, diagrams included (Theme in `references/page-spec.md`). Your job is to run the script, read what it reports, check the result, and tell the user plainly what the page show