`experience-design` — guides
Start from the outcome a user is trying to reach, derive the screens it needs, design them completely, and get an independent review before engineering builds.
These guides help you go from a customer’s goal to reviewed screens that are ready to build. A design slot you leave empty is not an error: the frontend pre-flight resolves it from a lower rung of its visual-authority precedence.
Start here
Section titled “Start here”- Design the experience — Go from a customer’s goal to reviewed screens that are ready to build.
- Thread a feature from journey to screens — Thread a feature from journey to screens, with a review at the end.
- Establish design intent — Set design principles, an aesthetic direction, and a design system first.
- Choose how much design a screen owes — Pick the risk tier that sets how much design a surface owes.
- Choose the right copy mode — Route a copy task to the right content mode or to microcopy.
- How to write a product’s voice and microcopy — Set the product’s voice once, then write error, empty-state, button, and label copy in it.
- The experience thread — How design artifacts link into one traceable thread.
experience-design— skill and reviewer reference — Each design skill and reviewer, with inputs, outputs, and routing.