Skip to content
Back to skills

Design Context

ASecurity

Refresh UI/UX context from design system, Storybook, and codebase

  • 342 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 1, 2026
toolsdocumentation

Works with

  • mcp

Security analysis

A100/100

Scanned September 1, 2026

npx -y skills add WellApp-ai/Well --skill design-context --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Design Context?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Design Context
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wellapp-ai-design-context/badge)](https://www.skillsdirectory.com/skills/wellapp-ai-design-context)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: design-context
description: Refresh UI/UX context from design system, Storybook, and codebase
---

# Design Context Skill

Ensures wireframes and UI decisions leverage existing patterns from the design system, Storybook, and codebase.

## When to Use

- Before presenting wireframes (Ask mode DIVERGE)
- Before implementing UI changes (Agent mode)
- At every DIVERGE Loop to stay grounded in existing patterns

## Instructions

### Phase 1: Design System Check

Read the design system documentation:

```
Read /docs/design-system/components.md
Read /docs/design-system/spacing.md
Read /docs/design-system/colors.md (if color decisions needed)
Read /docs/design-system/interactions.md (if interaction patterns needed)
```

**Note applicable:**
- Design tokens (`h-13`, `px-4`, `gap-3`)
- Component patterns (Button variants, DataTable, Dialog)
- Spacing conventions (p-4 for cards, gap-6 for sections)

### Phase 2: Storybook Patterns

Find existing component stories:

```
Glob **/*.stories.tsx
```

**Identify:**
- Components matching current wireframe needs
- Existing variants and props
- Documented states (loading, error, empty)

**Key story locations:**
- `/src/stories/` - General component stories
- `/features/*/components/*.stories.tsx` - Feature-specific stories

### Phase 3: Codebase Search

Search for similar UI patterns:

```
SemanticSearch "How is [pattern] implemented in the codebase?"
```

**Look for:**
- Similar features already built
- Reusable hooks and utilities
- Existing layout patterns

### Phase 4: Library Documentation (Context7 MCP)

Query library docs for unfamiliar patterns:

```
1. resolve-library-id with libraryName (e.g., "radix-ui")
2. query-docs with libraryId and specific question
```

**Common libraries:**
- `/radix-ui/primitives` - Dialog, Dropdown, Select patterns
- `/tanstack/query` - Data fetching patterns
- `/tanstack/table` - Table patterns

## Output Format

After running this skill, output:

```markdown
## Design Context

| Source | Relevant Patterns |
|--------|-------------------|
| Design System | [tokens, components] |
| Storybook | [stories that apply] |
| Codebase | [existing implementations] |
| Libraries | [patterns from docs] |

### Applicable Components
- [Component]: [How it applies to current wireframe]

### Design Tokens to Use
- Spacing: [tokens]
- Colors: [tokens]
- Typography: [tokens]
```

## Invocation

Invoke manually with "use design-context skill" or follow Ask mode DIVERGE loop which references this skill's phases.

## Related Skills

- `problem-framing` - Run before design-context
- `competitor-scan` - Compare with external patterns

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.