borghei/Claude-Skills / engineering/interface-refinement
interface-refinement
VerifiedRefine an existing interface with named commands (critique, polish, distill, typeset, colorize ...), a product and design context file, and a static detector of generic UI patterns. Use when UI looks generic, cluttered or unfinished.
references/command-onboard.md
View on GitHub# onboard — first run, empty states and the path to first value
**Job:** design the first minutes: what a new person sees, the first thing they can accomplish,
and every empty state on the way.
**Run when:** a critique's first-timer persona stalls; a surface ships with blank lists or a
generic "No data"; activation is low on a funnel the owner can show you.
## By mode
- **Operate:** the first task is the tutorial. Defaults, sample data clearly labelled as sample,
and inline hints beat a tour.
- **Persuade:** onboarding begins on the page that sells; the promise there must match the
first screen after sign-up.
- **Read:** a start-here path and a clear "what to read next".
## Change
- **Time to value:** count the steps from sign-up to the first useful outcome; remove or defer
every step that is not needed for it (profile details, invites, preferences).
- **Empty states:** each one says what will appear here, why it matters, and the one action that
fills it. Distinguish first use, no results, filtered out, no permission, and failed to load.
- **Defaults:** pre-fill what can be inferred; let people change it later.
- **Hints:** contextual, dismissible, shown once, tied to the element they describe. Tours only for
genuinely unfamiliar interaction models, always skippable.
- **Sample content:** labelled as sample, removable in one action, never counted in reports.
## Do not touch
- Product capability and pricing claims; onboarding copy must match what the product does now.
- Settings that have legal or billing consequence; never default those to the costly option.
## Steps
1. Walk the first run as a new account, writing down every screen and decision.
2. Mark the first-value moment; cut or defer what stands before it.
3. Write each empty state using `clarify` rules.
4. Make every hint and tour dismissible and remembered.
## Verify
- Step count to first value before and after.
- Every list, table and dashboard has a designed empty state (search the code for the components
and check each).
- A keyboard-only first run completes.
- Dismissed hints stay dismissed after reload.
## Hand-off
`clarify` for the copy if not already done; then `polish`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |