design-empty-states

What problem does it solve?

Users get stuck when an interface has no content, because generic or blank empty states don’t explain what belongs there or what to do next.

Core Features & Use Cases

• Expectation-setting copy: Creates a friendly headline and short description that explains what should appear in the area.
• Actionable recovery: Recommends a clear primary call-to-action plus optional secondary guidance (e.g., learn more or templates).
• Context-aware empty-state types: Adapts output for first-time, user-cleared, no-results, no-access, and error-as-empty scenarios.
• Assessment & refactoring guidance: Produces pass/fail evaluation and identifies failure modes like dead ends, negative framing, and generic illustrations.

Quick Start

Provide your current empty-state context (type of user state, what content should normally be present, and available user actions) and ask the skill to generate an empty-state design spec with copy and a primary CTA.