Hand-drawn component kit

Give reusable web components a sketchbook look and dependable interactions.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Hand-drawn component kit

Give reusable web components a sketchbook look and dependable interactions.

## Deliverable
A component kit with editable tokens, documentation and example states.

## Stack and visual direction
- Recommended starting stack: React and TypeScript with semantic CSS variables. Use Storybook when isolated examples serve the deliverable.
- Hand-drawn: Use sketch-like strokes, ink textures and occasional handwritten accents. Keep labels in readable text and retain semantic interactive controls. Apply this direction to the interface while keeping data and controls easy to read.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [Frontend Design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) (Skill) — Plan distinct typography, composition and interaction details before building UI.
  Fallback: Write a short plan for hierarchy, palette, spacing and interaction states, then review the actual screens against it.
- [Wired Elements](https://github.com/rough-stuff/wired-elements) (Repository) — Reference hand-drawn controls and preserve the semantics of each native interaction.
- [Storybook](https://github.com/storybookjs/storybook) (Repository) — Exercise reusable components and document visual and interactive states in isolation.
- [Web Design Guidelines](https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines) (Skill) — Review frontend UI against usability and accessibility guidance.
  Access to the current upstream guidelines for the skill's full review. Fallback: Perform the recipe's keyboard, focus, responsive and feedback checks manually.

## Workflow
1. Define ink, surface and accent tokens. Apply sketch strokes to a small kit of buttons, inputs, navigation and cards while retaining semantic HTML, visible focus and readable body text.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] Sketch effects never obscure labels or focus outlines.
- [ ] Button, input and navigation examples work by keyboard in isolation.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path.
- [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.

Recipe resources

Source, setup, and compatibility details.