skills.rest
cursor
cursorOFFICIAL
Explore all skills by this author →
WebsiteGitHub

principle-experience-first

Guides product and UX tradeoff decisions toward user delight over implementation convenience.

6.6k|542|Updated Jan 23, 2026
Search Tags:#prototyping#prioritization#User Experience#product decision#feature scope#ux tradeoffs#product principle
One-click install
npx skills add https://github.com/cursor/plugins --skill principle-experience-first
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-experience-first
Source: https://github.com/cursor/plugins/tree/main/pstack/skills/principle-experience-first
Command: npx skills add https://github.com/cursor/plugins --skill principle-experience-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often let implementation convenience dictate product decisions, resulting in bloated feature sets and rough user experiences. This Skill provides a decision framework for resolving product, UX, and feature-scope tradeoffs in favor of user delight.

Core Features & Use Cases

  • Tradeoff Resolution: Applies a clear rule when implementation convenience conflicts with user delight—choose delight.
  • Scope Discipline: Encourages shipping fewer polished features instead of many rough ones, and saying no to features that have not earned their place.
  • Broad User Definition: Treats end users, library consumers, and future maintainers as users whose experience must be weighed.
  • Use Case: When debating whether to add a fifth settings toggle or polish the core workflow, use this Skill to justify cutting the toggle and tightening the main loop.

Quick Start

Ask the agent to evaluate a proposed feature or UX tradeoff using the experience-first principle before committing to implementation.

Frequently Asked Questions about principle-experience-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between shipping more features or polishing fewer ones?▼

Ship fewer polished features rather than more rough ones. A polished experience with three features beats a rough one with ten, and every feature must earn its place in the product.

What should I do when implementation convenience conflicts with user experience?▼

Choose user delight over implementation convenience. Every technical decision either helps or hurts the experience, so resolve the conflict in favor of the person consuming the work.

Who counts as the user for a library or internal API?▼

The user is whoever consumes the work. For a library or internal API it is the colleague who imports it, and the engineer who maintains the code next is also a user whose experience should be weighed.

When should I prototype before committing to production code?▼

Prototype before committing whenever design decisions are involved. Design decisions are cheaper to explore in throwaway HTML than in production code, so validate the experience early.

When is the experience-first principle not the right lens?▼

This principle governs the target of work, not the sequence. Foundational thinking governs sequencing, so use experience-first for deciding what to build rather than the order of underlying infrastructure work.

Related Skills

Explore More Product & Management Skills→
elophantoelophanto
116

feedback-synthesis

Aggregate multi-channel user feedback into actionable product insights.

Community
Advanced
igot-aiigot-ai

quick-spec

Convert feature ideas into engineer-ready Markdown spec files.

Official
Intermediate
Hamza123545Hamza123545

Concept Scaffolding Skill v3.0 (Reasoning-Activated)

Design cognitive scaffolding frameworks for scalable concept learning with progressive complexity.

Community
Basic
danfrdndanfrdn

exp-driven-dev

Implement A/B testing frameworks with feature flagging and statistical significance calculation.

Community
Advanced