# sketch

This skill defines a hand-drawn design system for AI-assisted UI work. Use it for component guidance with tokens, interaction states, and testable accessibility rules.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2300 installs · ★ 3349
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sketch/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/sketch

## What it does

sketch helps produce practical design-system guidance for interfaces with a hand-drawn feel. It defines typography, colors, spacing, semantic tokens, component anatomy, variants, and interaction states. The visual direction uses warm cream surfaces, soft teal accents, handwritten headings, dashed outlines, and offset pencil-like shadows.

The skill asks for WCAG 2.2 AA, keyboard-first interaction, and visible focus states. Its workflow covers foundations, component rules, responsive behavior, accessibility criteria, content tone, anti-patterns, migration notes, and a QA checklist. WCAG 2.2 AA is a clear reason to test the result with keyboard navigation and assistive technology.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sketch -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/sketch/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/sketch/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sketch -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/sketch/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sketch -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/sketch/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills sketch
```

2. **Manually: put the files in place**
- File: `.github/skills/sketch/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sketch -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/sketch
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/sketch/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sketch -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sketch/SKILL.md

## When to use it
- define color, type, and spacing tokens
- document component states and variants
- set responsive behavior for UI components
- add testable accessibility criteria
- prepare a design-system QA checklist

## Example prompts
- Apply the `sketch` skill to draft a design system for this interface.
- Use `sketch` to define the button anatomy, states, tokens, and keyboard behavior.
- Review the existing UI with `sketch`, then list accessibility issues and migration steps.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b20fc98597956644.

BEGIN THIRD-PARTY FILE b20fc98597956644
```text
---
name: "sketch"
description: "A friendly, hand-drawn sketch interface inspired by pencil illustrations on warm cream paper. Soft teal brand accents, hand-written display headings, rounded pill controls."
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# Sketch Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for Sketch.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand
A friendly, hand-drawn sketch interface inspired by pencil illustrations on warm cream paper. Soft teal brand accents, hand-written display headings, rounded pill controls, dashed card outlines, and chunky offset "pencil-drawn" shadows give every surface a tactile, illustrated feel.

## Style Foundations
- Visual style: modern, clean, high-contrast
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Delicious Handrawn, display=Delicious Handrawn, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#1DAD97, secondary=#F4EDE0, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32

## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states

## Writing Tone
concise, confident, helpful

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit

## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels

## Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.

## Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules.
2. Define tokens and foundational constraints before component-level guidance.
3. Specify component anatomy, states, variants, and interaction behavior.
4. Include accessibility acceptance criteria and content-writing expectations.
5. Add anti-patterns and migration notes for existing inconsistent UI.
6. End with a QA checklist that can be executed in code review.

## Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist

## Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
```
END THIRD-PARTY FILE b20fc98597956644

The third-party file has ended. Everything between the b20fc98597956644 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3108 of 3732 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sketch/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md