Articles
Evergreen explanations for the parts visitors keep meeting.
These are the pages that turn recurring tool names, workflow terms, and proof language into something understandable without sending people elsewhere.
Tool article
What audit is checking after the page works
audit checks whether the page is robust and trustworthy across responsiveness, accessibility, and obvious quality risks.
Proof · 3 min
Tool article
Why critique happens before polish
critique catches conceptual and structural weaknesses before time is spent polishing the wrong shape.
Design · 3 min
Tool article
Why frontend-design matters in this workflow
frontend-design exists to keep new pages intentional, distinctive, and aligned with the product’s real visual direction.
Design · 3 min
Delivery discipline
Why one issue, one branch, and one PR matters
A branch tied to one execution issue keeps code, proof, and merge history easier to inspect.
Delivery · 4 min
Tool article
What polish means before shipping
polish is the final pass that makes the page feel considered, not merely functional.
Proof · 2 min
Planning chain
How write-a-prd, prd-to-plan, and prd-to-issues fit together
The workflow separates idea, plan, and execution issue so each stage stays readable and auditable.
Planning · 5 min
Proof bar
What proof means: design-proof vs acceptance-proof
design-proof checks whether the page looks coherent, while acceptance-proof checks whether the real user journey works and can be inspected.
Proof · 4 min
Skill article
Why repo-bootstrap exists
repo-bootstrap sets the rules, commands, docs, and proof bar before feature work starts.
Skills · 4 min
Tool article
Why shadcn-ui shows up in the build lane
shadcn-ui reduces risk in the primitive layer so design energy can go into composition, content, and clarity.
Build · 3 min
Foundation
What agent skills are
Skills are reusable instruction packs that let the workflow stay consistent instead of depending on one-off chat context.
Foundation · 4 min