principle-experience-first

What problem does it solve? When building products, teams often let implementation convenience dictate scope and quality, resulting in bloated features and rough experiences. This Skill provides a decision framework that keeps user experience as the governing priority in every product, UX, and feature-scope tradeoff. ## Core Features & Use Cases - Tradeoff Resolution: Resolves conflicts between engineering convenience and user delight in favor of the experience. - Scope Discipline: Encourages shipping fewer polished features instead of many rough ones, and saying no to features that do not earn 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 ship ten half-finished features or three polished ones before a release, apply this principle to cut scope and tighten the core workflow. ## Quick Start Ask the AI to apply the experience-first principle when reviewing a feature scope decision or product tradeoff.