principle-experience-first

What problem does it solve? Engineering teams often let implementation convenience dictate product decisions, resulting in bloated feature sets and rough user experiences. This Skill provides a decision principle that resolves product, UX, and feature-scope tradeoffs in favor of user delight. ## Core Features & Use Cases - Tradeoff Resolution: When convenience conflicts with delight, it directs you to choose delight and explain impact from the user's seat. - Scope Discipline: Encourages shipping fewer polished features instead of many rough ones, and saying no to features that have not earned their place. - Prototyping Guidance: Promotes validating design decisions in throwaway Compose previews before committing to production code. - Use Case: While scoping an Android feature, a developer is tempted to add ten half-finished options. Apply this principle to cut scope to three polished features with refined transitions, spacing, and error states. ## Quick Start Apply the experience-first principle to evaluate whether this feature scope and UX tradeoff prioritizes user delight over implementation convenience.