skills.rest
adjohn
adjohnCOMMUNITY
Explore all skills by this author →
GitHub

principle-experience-first

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

3|2|Updated Aug 28, 2026
Search Tags:#prototyping#user experience#ux#product quality#design decisions#feature scope#product principles
One-click install
npx skills add https://github.com/adjohn/pstack --skill principle-experience-first-adjohn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-experience-first
Source: https://github.com/adjohn/pstack/tree/main/skills/principle-experience-first
Command: npx skills add https://github.com/adjohn/pstack --skill principle-experience-first-adjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams often let implementation convenience dictate product decisions, shipping many rough features instead of a few polished ones. This Skill provides a decision framework that keeps user experience as the governing priority when product, UX, or feature-scope tradeoffs arise. ## Core Features & Use Cases - Tradeoff Resolution: Resolves conflicts between implementation convenience and user delight in favor of the user. - Scope Discipline: Encourages shipping fewer, polished features and requiring every feature, control, and option to earn its place. - Prototyping Guidance: Promotes validating design decisions in throwaway HTML before committing to production code. - Use Case: When debating whether to add a tenth settings toggle or refine the core workflow's transitions and error states, apply this principle to cut the toggle and polish the core loop. ## Quick Start Apply the experience-first principle to evaluate whether this feature scope and UX tradeoff prioritizes user delight over implementation convenience.

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 existing ones?▼

Choose polish over breadth: a polished experience with three features beats a rough one with ten. Every feature, control, and option must earn its place by serving the central workflow, otherwise it should be cut.

When should I prototype a UX design before writing production code?▼

Prototype before committing whenever a design decision is uncertain. Design decisions are cheaper to explore in throwaway HTML than in production code, so validate the experience first and implement second.

Does this principle apply to libraries and internal APIs, not just UIs?▼

Yes. The user is whoever consumes the work: the end user for a UI, the colleague importing a library or internal API, and the engineer who maintains the code next. Weigh each user's experience the same way.

When should implementation convenience override user experience?▼

According to this principle, it should not. When implementation convenience conflicts with user delight, choose delight. Foundations should serve the experience, governing the sequence of work rather than the target.

Related Skills

Explore More Product & Management Skills→
oldwinteroldwinter
5

usability-testing

Plan, execute, and synthesize usability tests into a Usability Test Pack.

Community
Advanced
naviktnavikt
1

adapt

Translate desktop layouts to mobile, tablet, and print experiences.

Official
Intermediate
cursorcursor
6.6k

principle-experience-first

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

Official
Basic
phazurlabsphazurlabs
35

UX Metrics & Measurement

Define and operationalize UX measurement frameworks like HEART, SUS, and UEQ.

Community
Advanced