Designing Interaction States

Designs the states screens actually spend their time in — first-run and empty states, loading and skeletons, inline validation and error messages, success feedback, destructive confirmations, and the microcopy for each — so a product feels finished instead of only working on the happy path. Use when building a form, list, dashboard, upload, checkout or settings screen, adding an async action, writing error or empty-state copy, or reviewing a UI that shows blank pages, raw errors or spinners forever.

115 stars 18 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add wdm0006/python-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add wdm0006/python-skills --skill designing-interaction-states
Manual install
git clone --depth 1 https://github.com/wdm0006/python-skills.git /tmp/python-skills
mkdir -p ~/.claude/skills
cp -r /tmp/python-skills/skills/common/interaction-states ~/.claude/skills/designing-interaction-states

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Designing Interaction States

Most screens are designed in one state: full of realistic data, with every request
succeeding. Users mostly see the others — empty on day one, loading on a slow
network, an error on a typo. Those states are where an app feels either finished or
neglected.

## Contents
- The state inventory
- Empty and first-run states
- Loading
- Forms and validation
- Errors
- Success and feedback
- Destructive actions
- Microcopy rules
- Checklist

## The state inventory

For every screen, list and design each of these before calling it done:

| State | Question it answers |
|-------|---------------------|
| First run / empty | "What is this and what do I do first?" |
| Loading | "Is it working?" |
| Partial / some data | "Does it still look intentional with one item?" |
| Full / overflow | "What happens with 500 items or a very long name?" |
| Error | "What went wrong, and what do I do now?" |
| Success | "Did it work?" |
| Offline / permission denied | "Why can't I do this?" |

Seed local data for each and screenshot them; reviewers should see every state.

## Empty and first-run states

An empty state is the product's best onboarding surface. Replace "No items." with:

- a one-line explanation of what will appear here,
- the single primary action that fills it ("Import contacts", "Create your first
  project"), as a real button,
- optionally a secondary path (sample data, docs link).
Read the full skill on GitHub

Details

Skill name
designing-interaction-states
Path
skills/common/interaction-states/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Designing Interaction States skill do?

Designs the states screens actually spend their time in — first-run and empty states, loading and skeletons, inline validation and error messages, success feedback, destructive confirmations, and the microcopy for each — so a product feels finished instead of only working on the happy path. Use when building a form, list, dashboard, upload, checkout or settings screen, adding an async action, writing error or empty-state copy, or reviewing a UI that shows blank pages, raw errors or spinners forever.

How do I install the Designing Interaction States skill?

Claude Code plugin: /plugin marketplace add wdm0006/python-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Designing Interaction States popular?

It lives in wdm0006/python-skills, which has 115 GitHub stars and 18 forks.

Related skills

Auditing Python Security

115

wdm0006/python-skills

Audits Python libraries for security vulnerabilities using Bandit, pip-audit, Semgrep, and detect-secrets. Identifies SQL injection, command injection, hardcoded credentials, secrets exposed through tracebacks, weak cryptography, and insecure deserialization. Use when reviewing library security, setting up security scanning in CI, or implementing secure coding patterns.

Security18

Building Accessible Interfaces

115

wdm0006/python-skills

Makes web and app UIs usable by keyboard, screen-reader, low-vision and motion-sensitive users — semantic HTML before ARIA, labelled controls, visible focus, WCAG AA contrast measured rather than eyeballed, touch targets, reduced motion, and automated axe checks plus a manual keyboard pass in CI or before every UI PR. Use when building or restyling a screen, adding a form, modal, menu or custom control, choosing colors, or reviewing a UI change.

Frontend & Design18

Building Browser Extensions

115

wdm0006/python-skills

Builds and tests Manifest V3 browser extensions — service-worker message channels that survive teardown, chrome.storage read-modify-write safety, settings validation in the popup, and a Jest chrome mock that can actually fail. Use when writing or reviewing a background service worker, a popup that reads/writes chrome.storage, an extension's Jest suite, or debugging an extension whose UI silently stops responding.

Software Development18

Designing Interfaces

115

wdm0006/python-skills

Makes a product's UI look deliberate and current instead of dated or improvised — auditing a screen against hierarchy, type scale, spacing scale, color tokens, layout and component consistency; introducing design tokens before restyling anything; and verifying every change visually with before/after screenshots. Use when building or restyling any web or app screen, reviewing a UI that looks old, cluttered or inconsistent, starting a design system for an existing app, or planning a design-improvement issue.

Frontend & Design18

Pixellab Pip

47

Shilo/pixellab-pip

Use when PixelLab (Pixel Lab) or Pip skill context is present for setup/auth (PIXELLAB_SECRET, bearer token), MCP/API routing, asset generation, endpoint choice, SDK integration, sprites, sprite sheets, characters, portrait characters, objects, tiles, tilesets, tilemaps, maps, Godot/Unity map export, icons/UI/fonts, backgrounds, palettes, image edits, animation/VFX, talking portraits, vocal animations, talking GIFs, lip sync, skeleton/template/preset animation, looping/seamless or multi-shot cinematics, project art styles, animation inspection/repair, blueprints/recipes and `*.blueprint.json`

Frontend & DesignIn 1 list

New Project

75

sneg55/agent-starter

Full project bootstrap - interviews the developer (name, description, stack, components), then scaffolds directory structure, CLAUDE.md, config files, hooks, skills, and first commit.

Frontend & DesignIn 1 list

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.