What problem does it solve?
This Skill helps you evaluate features from the perspective of the person who will actually live with them, instead of the builder or the demo. It is useful when a proposal looks clever or feasible but may not be wanted, may be frustrating in practice, or may leave the real user stranded when things go wrong.
Core Features & Use Cases
- Desirability Review: Distinguish between something that can be built and something the served person actually asked for.
- Livability Review: Check whether the experience still works for tired, rushed, confused, or edge-case users after the happy path.
- Interface Consumer Lens: Apply the same questions to APIs, CLIs, and libraries by treating the consumer as the user.
- Use Case: Review a cancellation flow, internal API, or feature proposal and ask whether the real person needs it, can understand it, and can recover from mistakes without being trapped.
Quick Start
Ask the user-advocate skill to evaluate this feature from the perspective of the person who will use it and identify where the design is buildable but not actually wanted.