What problem does it solve? Teams often let implementation convenience drive product, UX, and API decisions, producing cluttered interfaces, confusing workflows, and experience debt that frustrates end users, library callers, and operators. ## Core Features & Use Cases - Core Workflow Focus: Identify who consumes a change and keep their path from start to successful outcome short, obvious, and trustworthy, including empty, error, and recovery states. - Scope Discipline: Force every feature, option, setting, and abstraction to earn its place by serving the core workflow, with sensible defaults replacing unnecessary decisions. - Experience-First Tradeoffs: Resolve conflicts between implementation convenience and user clarity in favor of the consumer, and review finished work with a five-question outside-in checklist. - Use Case: When designing a new settings page or library API, apply this Skill to cut unused controls, choose defaults, and ensure callers never need workarounds or guesswork. ## Quick Start Review this feature proposal with the experience-first skill and tell me what to remove, default, or simplify for the end user.
