About principle-experience-first
A product development principle that prioritizes user experience over implementation convenience. It guides teams building interfaces, libraries, and internal APIs to justify features, prototype decisions, and refine the core workflow and its details.
Key features
- 01Prioritize user experience
- 02Justify every feature and control
- 03Prototype before implementation
- 04Refine transitions, spacing, and feedback
- 05Keep features focused on the core workflow
Use cases
- 01Decide whether a proposed feature belongs
- 02Prototype interface decisions before production
- 03Improve feedback and error states
- 04Assess an API from its importer's perspective
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.