design-feature
Installation
SKILL.md
Purpose
Technical design interview -> design document. Pipeline: plan-feature -> write-a-prd -> review-prd -> glossary -> (design-ux) -> design-feature -> review-plan.
Starting
Before asking anything:
- Look in
./plans/for: PRD (*-prd.md), scope doc (*-scope.md), glossary (*-glossary.md), UX spec (*-ux.md). Read all found. Use glossary canonical terms for data models, APIs, modules, variables. UX flows map to behavior specs; UX screens/components map to frontend architecture. - Explore the codebase thoroughly — tech stack, patterns, data models, auth, API conventions, testing patterns, deployment setup.
- Search for architecture docs, ADRs, domain glossaries, process docs, READMEs.
- If docs and code disagree, note the discrepancy to surface during interview.
If prior docs exist: "I've read the PRD, UX spec, and explored the codebase. Requirements call for [items]. UX defines [N flows] across [N screens]. Stack uses [tech]. First: [question about architecture/patterns]."
No PRD? Works — but note that defined requirements make for a better design. No UX spec? Interview will cover frontend concerns as needed. No glossary? Be consistent in naming and note decisions in the Decisions Log.