crit-edge-states

Generate edge-state HTML wireframes for locked screen inventories.

3|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/metedata/design-crit --skill crit-edge-states
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crit-edge-states
Source: https://github.com/metedata/design-crit/tree/main/skills/crit-edge-states
Command: npx skills add https://github.com/metedata/design-crit --skill crit-edge-states

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many products treat non-happy-path scenarios as an afterthought, leaving users stranded during empty, error, loading, offline, and boundary conditions; this Skill structures and systematizes how every screen behaves when things go wrong so those experiences are deliberate, actionable, and on-brand.

Core Features & Use Cases

  • Audit the locked screen inventory to build a comprehensive edge-state coverage matrix that shows which screens need empty, loading, error, offline, and boundary treatments.
  • Generate 2–3 self-contained HTML wireframe options per round that include coverage summaries, per-screen wireframes, pattern legends, and copy samples for each applicable edge state.
  • Integrate with the crit loop by reading .design-crit state files, producing critique.md and compare.html artifacts, and recording decisions to state.json so edge-state patterns become downstream constraints.

Quick Start

Generate two edge-state wireframe options for the locked screen inventory and save them to .design-crit/facets/edge-states/.

Frequently Asked Questions about crit-edge-states

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

FAQPage Schema
How do I design UI wireframes for empty, loading, and error states?

To design UI edge state wireframes, apply this Skill to a locked screen inventory to generate 2-3 self-contained HTML options per round covering empty, loading, error, offline, and boundary conditions, complete with a coverage matrix and copy samples.

What is an edge-state coverage matrix for app screens?

An edge-state coverage matrix maps which screens in your inventory require empty, loading, error, offline, and boundary treatments. This Skill audits your locked screens to build this matrix, ensuring every non-happy-path scenario receives deliberate wireframe coverage.

Can I integrate edge-state wireframes into a design critique loop?

Yes, this Skill integrates with design critique loops by reading .design-crit project files, producing critique.md and compare.html artifacts, and recording edge-state pattern decisions to state.json so they become downstream constraints.

How do I generate multiple HTML wireframe options for edge states during a design crit?

During a design crit, this Skill produces 2-3 self-contained HTML wireframe options per round. Each option includes coverage summaries, per-screen wireframes, pattern legends, and copy samples for applicable edge states, saved to .design-crit/facets/edge-states/.

What edge state scenarios should I cover when auditing app screen wireframes?

When auditing app screen wireframes, you should cover empty, loading, error, offline, and boundary state scenarios. This Skill systematically structures these non-happy-path conditions so they are actionable and on-brand rather than afterthoughts.

Does this wireframe generation tool require any external design dependencies?

No, this Skill operates with no external dependencies. It generates self-contained HTML wireframes and documentation artifacts directly, requiring only your locked screen inventory and .design-crit project state files to function.