Illustration-led onboarding

Explain the first useful action through a short, skippable onboarding.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Illustration-led onboarding

Explain the first useful action through a short, skippable onboarding.

## Deliverable
A responsive onboarding experience with original or approved illustrations.

## Stack and visual direction
- Recommended starting stack: React and TypeScript with semantic CSS variables. Use Storybook when isolated examples serve the deliverable.
- Claymorphism: Use rounded, softly lit forms and playful volume for key controls. Keep content surfaces simple and prioritize comfortable touch targets. 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.
- [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure.
  [Official setup](https://nextjs.org/docs/app/getting-started/installation).
- [Motion](https://github.com/motiondivision/motion) (Repository) — Document intentional transitions, including reduced-motion behavior and interruption.

## Workflow
1. Identify the first useful task, create an illustrated path with accessible text, and offer skip, back and resume actions. Use motion in service of transitions and reflect actual progress.
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
- [ ] Skip and complete both land users at useful destinations.
- [ ] Progress and instructions stay understandable with images and motion disabled.
- [ ] 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.