unhappy

Audit and design loading, empty, error, partial, conflict, and offline UI states.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Nweremizu/ekklesia --skill unhappy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unhappy
Source: https://github.com/Nweremizu/ekklesia/tree/main/.junie/skills/unhappy
Command: npx skills add https://github.com/Nweremizu/ekklesia --skill unhappy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about unhappy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design error and loading states for frontend UI?

Design loading and error states by auditing every UI surface to map missing skeleton screens, empty state copy, and error recovery actions, ensuring users never face blank screens or vague errors during async failures.

What is a UI state inventory and how does it handle empty or partial data?

A UI state inventory maps every frontend surface to identify loading, empty, error, partial, conflict, and offline behaviors, filling gaps with clear recovery actions and support IDs where the happy path assumes data is always present.

How do I add optimistic UI and offline reconciliation to a dashboard?

Add optimistic UI and offline reconciliation to dashboards by applying early-return guards for async workflows and defining explicit offline state behaviors that reconcile data when connectivity returns.

Can I audit settings panels and forms for missing non-happy UI states?

Yes, you can audit settings panels and forms to enumerate every surface and state, flagging missing non-happy states like conflict or offline behavior and generating review-ready change notes for implementation.

What is the best way to harden a member list before release?

Harden a member list before release by mapping its complete state-by-state plan, adding missing skeleton screens, retry actions, and empty-state copy to handle async failures and ensure trustworthy interactions.