principle-experience-first
About principle-experience-first
A design skill for prioritizing the experience of people who use a product, library, or internal API. It guides teams to justify features, prototype decisions, and refine the central workflow and details.
Key features
- 01Prioritize user experience over implementation convenience
- 02Justify every feature and control
- 03Prototype before committing to design decisions
- 04Refine transitions, layout, feedback, and errors
- 05Keep features focused on the core workflow
Use cases
- 01Evaluating whether a feature belongs in a product
- 02Prototyping UI choices before implementation
- 03Improving feedback and error states
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/principle-experience-firstin Claude Code to confirm it loaded.
Details
From the project READMEExperience First
When implementation convenience conflicts with user delight, choose delight.
- Every feature, control, and option must be justified
- Ship less, ship better (polished experience with three features beats rough one with ten)
- Prototype before committing (design decisions are cheaper in throwaway HTML than production code)
- Get the details right (transitions, alignment, spacing, feedback, error states)
- Tighten the core loop (every feature should serve the central workflow or get out of the way)
The user is whoever consumes the work. For a UI that is the end user. For a library or an internal API it is the colleague who imports it. The engineer who maintains the code next is a user too. Weigh their experience the same way, and explain impact from their perspective.
Foundations should serve the experience. Foundational thinking governs the sequence of work. This principle governs the target.