How it works
Describe the feature
Share what you want to build—a rough idea, a design mockup, or a feature request from product.
Generate the spec
The skill produces a detailed spec covering states, interactions, edge cases, copy, and error handling.
Refine and hand off
Iterate on the spec with your team, then hand off to engineering with confidence.
Describe the feature
Share what you want to build—a rough idea, a design mockup, or a feature request from product.
Generate the spec
The skill produces a detailed spec covering states, interactions, edge cases, copy, and error handling.
Refine and hand off
Iterate on the spec with your team, then hand off to engineering with confidence.
Why use Design Briefs & UX Specs
Fewer surprises in dev
Edge cases and error states are documented before development starts, not discovered during.
Faster engineering handoff
Engineers get clear specs instead of ambiguous mockups that require follow-up questions.
Grounded in your product
Specs reference your existing components, patterns, and terminology—not generic solutions.
Better cross-team alignment
A written spec creates a shared reference point for design, product, and engineering.
When to use Design Briefs & UX Specs
New feature kickoff
You have a rough idea or mockup and need to think through the details before building.
Write a spec for adding dark mode to our settings page. Cover toggle behavior, persistence, and edge cases.
Complex interaction flows
A feature with multiple states or conditional logic that needs thorough documentation.
Spec out the multi-step checkout flow including validation, error states, and loading indicators.
Design review preparation
Preparing for a stakeholder review and want to anticipate questions before the meeting.
Create a spec for this onboarding redesign so I can walk through edge cases with the team.