What problem does it solve?
Frontend developers often lack a consistent methodology when building components, leading to poor reusability, inconsistent styling, missing accessibility attributes, and insufficient test coverage. This Skill provides a structured methodology for designing, implementing, and testing frontend components.
Core Features & Use Cases
- Component Design Principles: Enforces single-responsibility, reusability via props and slots, and consistent PascalCase naming conventions.
- State & API Contract Management: Classifies local, shared, server, and URL state with appropriate management strategies, and aligns API calls with architecture.md endpoint definitions including mock strategies.
- Design Token Integration: Reads ui-design.json tokens, pages, and prototype links to derive CSS variables, layouts, and navigation flows.
- Testing Pyramid: Defines unit (70%), integration (20%), and mandatory E2E (10%) test coverage with concrete checklists.
- Use Case: When implementing a new user profile page, follow this methodology to read the UI design spec, build reusable components with proper state management, wire up API calls per the architecture contract, and ship with full test coverage.
Quick Start
Use the frontend component development methodology to implement the user profile page components based on the ui-design.json and architecture.md in this project.