states

Installation
SKILL.md

Screen states

Overview

A screen is not designed until every state it can be in is designed. The happy path is one state out of twenty. List the states in words first, get the list approved, then draw. Agreeing on a list costs a minute. Discovering a missing state in code costs a day.

When to use

  • A new screen, flow or component, or a redesign of one.
  • "Cover all the states", "what are we missing?", "is this ready for dev?"
  • The design shows one perfect case: three orders, short names, everything loaded.

When NOT to use

  • A small edit to an existing screen ("make the button 2px taller", "fix this typo"). Make the edit and stop.
  • Pure copy changes, or a question about the design.

Before you start

Installs
1
Repository
diego3g/craft
GitHub Stars
92
First Seen
2 days ago