Agent skill · product strategy · cursor
principle-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
Why this skill is useful
Codifies a user-centric approach to product development that the AI could infer but now doesn't have to guess.
What it needs
About 1k tokens when loaded. Last updated 2026-08-06. 2,555 stars on the source repository.
What this skill does
Experience 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/principle-experience-first