OpenParable
Skip to content
← Back to skills

Component Design

Design
component-design

Component Design is an Agent Skill for design published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Design reusable UI components and design system elements with consistent styling and behavior. Use for: building design systems, creating component libraries, establishing UI patterns, and ensuring design consistency across products.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/design/component-design-jh9282026-manus/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/component-design, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Component Design

Description

Component Design creates reusable, consistent UI building blocks. A well-designed component library ensures visual consistency, speeds up design/development, and maintains quality across all interfaces.

When to Use

  • After foundational design tokens (colors, type, spacing) are defined
  • Before designing full pages
  • Building a design system
  • When UI needs consistency audit
  • Creating handoff documentation

Instructions for AI Agents

Step 1: Identify Component Needs

Prompt to inventory components:

Based on the wireframes for [PROJECT], list all UI components needed:

**Actions**
- Buttons (primary, secondary, etc.)
- Links
- Icon buttons

**Inputs**
- Text inputs
- Select/dropdowns
- Checkboxes/radios
- Toggles
- Text areas

**Display**
- Cards
- Tables
- Lists
- Badges/tags
- Avatars
- Progress indicators

**Navigation**
- Tabs
- Breadcrumbs
- Pagination
- Menus

**Feedback**
- Alerts/toasts
- Modals
- Tooltips
- Empty states

**Layout**
- Headers
- Sidebars
- Footers

Step 2: Define Component States

Standard interactive states:

StateWhenVisual Change
DefaultNormal stateBase appearance
HoverMouse overSlight change (lighter/darker, shadow)
FocusKeyboard focusVisible focus ring
ActiveBeing clickedPressed appearance
DisabledNot availableReduced opacity, no interaction
LoadingProcessingSpinner, skeleton
ErrorValidation failedError styling
SuccessAction completedSuccess styling

Step 3: Component Specification Template

For each component, document:

## Success Criteria

### Minimum Requirements
- [ ] Core components designed (buttons, inputs, cards)
- [ ] All interactive states defined
- [ ] Size variants specified
- [ ] Colors reference design tokens
- [ ] Touch targets minimum 44px

### Quality Indicators
- [ ] Consistent across all components
- [ ] Accessible (contrast, focus states)
- [ ] Developer-ready specifications
- [ ] Covers all wireframe needs

---

## Related Skills

- **Previous**: `color_palettes.md`, `typography.md`, `spacing_rhythm.md`
- **Next**: `interaction_design.md` - Add micro-interactions
- **Related**: `design_documentation.md` - Full specification


## Using the Reference Files

**`/references/component_examples.md`** — Detailed component examples including buttons, inputs, cards, navigation, and badges.

**`/references/prompts_and_templates.md`** — Prompts library and component specification templates.