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.

4,171
installs: 0 up / 0 down, score 0.00
votes: 13,528
repo stars
Updated: less than a month ago
In the catalog since: 1 Oct 2026
From: cursor/plugins

Get it through your agent npx skills add cursor/plugins@principle-experience-first

Skill instructions

Rendered from the published SKILL.md, 14 lines.

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.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "principle-experience-first"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository cursor/plugins
Listing on skills.sh

From cursor/plugins via skills.sh

Related skills

principle-exhaust-the-design-space
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
4,200 installs
shape
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
30,040 installs
principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
4,262 installs
intent-driven-development
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
4,937 installs
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
1,029,907 installs

More from cursor/plugins

unslop
Cut AI tells from any writing.
27,770 installs
thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
22,194 installs
deslop
Remove AI-generated code slop and clean up code style
9,336 installs
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
7,883 installs
how
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
5,933 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.