frontend-architecture

Run this Skill after defining your product and design docs. It scans existing documentation, identifies which architectural decisions matter for your project, interviews you on those decisions, and writes the result to docs/04_tech/frontend_architecture.md.

The Skill presents framework-matched options during its interview. For React it offers local state, Zustand, Redux, or server-state-only with React Query, and records your choice with rationale in the generated document.

Yes. If no existing docs are found, it falls back to a baseline interview covering framework, state management, routing, styling, and data fetching. However, richer docs produce more targeted questions and a better-tailored document.

It reads the PRD, product principles, domain model, business rules, UX spec, UI spec, backend architecture, and slice discovery files if they exist. Each document informs specific decision areas such as data fetching patterns or client-side rule enforcement.

The generated document is written to docs/04_tech/frontend_architecture.md, and the folder is created if missing. If multiple docs folders are detected, the Skill asks which one to use before writing.