unhappy

What problem does it solve?

This Skill helps you design and audit the non-happy paths that make interfaces trustworthy, so users are not left staring at blank screens, vague errors, or broken interactions when data is missing or systems fail.

Core Features & Use Cases

• State Inventory: Map every surface in the target UI and identify loading, empty, error, partial, conflict, and offline behavior.
• Gap Filling: Add missing state copy, skeletons, retry actions, support IDs, and offline reconciliation patterns where the happy path assumes everything works.
• Use Case: A product team wants to harden a member list, settings page, or dashboard before release; this Skill turns each surface into a complete state-by-state plan and flags what still needs implementation.

Quick Start

Use the unhappy skill to audit the target UI, enumerate every surface and state, and fill any missing non-happy states with clear recovery behavior.