The product itself
- pages and navigation
- content and data
- product workflows
- business behavior
- specialist layouts that still serve the product
Build
Change the look. Keep the product.
A kit swap should feel surgical: repair what is broken, preserve what makes the product work, and make the new visual system easy to undo.
The broken experience
- overlap and clipped content
- page-level horizontal overflow
- unclear scroll ownership
- controls smaller than 44 pixels
- unreachable keyboard actions
- fixed panels that do not fit phones
The visual language
- color roles
- type roles
- spacing and control density
- shape, borders, and depth
- focus, state, and purposeful motion
- icons and selected fonts
Kit fit check
Not startedClassify the real things people need to do.
Decide how each real product journey relates to Kit before adopting or swapping a visual system.
This assessment covers design-system fit only. Checklist remains the authority for full-project launch readiness.
No journeys added yet.
Add the product’s main jobs one at a time. This is about design-system fit, not launch readiness.
Describe the product in ordinary English.
The Studio turns these choices into the exact brief used for the audit, repair, swap, proof, and rollback.
The same work, newly expressed.
The layout, content, and behavior stay familiar. The new kit carries color, type, spacing, controls, focus, and motion.
- Everyday pieces
- 142 available for existing product needs
- Specialist patterns
- 37 available, none forced
- Rollback
- One appearance switch