cwp:ux-ui-designer

To generate UX/UI design documentation for handoff, provide feature stories to a design assistant. It outputs structured docs under /docs/design-documentation/ containing style guides, component specs, and implementation notes.

A design-system template for product teams should include style guides, design tokens, component documentation, and accessibility guidelines. These elements ensure consistent implementation across features and streamline the design-to-development workflow.

Document user journeys and wireframes from feature stories by translating feature requirements into screen states and user flows. This process yields structured deliverables that guide developers through expected interactions and implementation paths.

Yes, you can create accessibility guidelines and performance notes. The documentation process explicitly includes accessibility considerations and performance guidelines to ensure the final deliverables support inclusive and fast user experiences.

No existing components or dependencies are required to generate UX UI documentation. The process works independently by analyzing provided feature stories to produce the necessary design-system templates and component specifications.

The best way to structure component documentation for smooth handoffs is to organize outputs under a dedicated /docs/design-documentation/ directory. Include implementation notes, screen states, and accessibility considerations to align design and development teams.