storyboard

Generates a single HTML page embedding related UX mocks with audit checklists, flow diagrams, and gap cards.

Updated May 18, 2024
One-click install
npx skills add https://github.com/joshhornby/dotfiles --skill storyboard-joshhornby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: storyboard
Source: https://github.com/joshhornby/dotfiles/tree/main/.claude/skills/storyboard
Command: npx skills add https://github.com/joshhornby/dotfiles --skill storyboard-joshhornby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a multi-step user flow means opening many separate mock files and holding transitions, inconsistencies, and missing states in your head. This Skill consolidates every UX surface in a scope of work into one scrollable HTML page so cross-surface gaps and inconsistencies become visible in a single review pass. ## Core Features & Use Cases - Side-by-side mock embedding: Existing mocks are embedded as sandboxed iframes in a responsive grid, each paired with a per-mock audit checklist covering disciplines like critique, clarify, audit, polish, and harden. - Flow diagram and gap cards: An ASCII flow diagram in a <pre> block colour-codes existing mocks, gaps, and adjacent surfaces, while each missing mock gets a card with brainstorm questions that must be answered before drafting. - Safe embedding and project-native styling: Enforces iframe sandbox attributes, restrictive CSP, Prettier-safe markup, and reuse of the project's existing design tokens rather than inventing new ones. - Use Case: Before implementing an onboarding flow spanning signup, verification, and empty/error states, run the skill to produce one audit page showing all existing mocks, flagging the missing loading state, and listing the decisions needed for each gap. ## Quick Start Ask the assistant to run /storyboard for your scope, for example: create a storyboard for the onboarding v2 flow covering all mocks in the design-mocks folder.

Frequently Asked Questions about storyboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review multiple UX design mocks in one place?

Run the storyboard skill with a scope name to generate a single HTML page embedding all related mocks as sandboxed iframes in a responsive grid. Each mock gets an audit checklist, and a flow diagram at the top shows how the user moves between surfaces.

When should I create a design mock storyboard?

Create one when a flow spans enough related surfaces or states that separate review hides transitions and gaps, such as signup through onboarding or a feature with loading, empty, and error states. Skip it for single-mock fixes, non-UX work, or features already built.

Can I embed interactive HTML mocks safely in a review page?

Yes, but each iframe needs a sandbox attribute granting only required capabilities. Same-origin untrusted content must not combine allow-scripts and allow-same-origin; if that pairing is genuinely needed, serve it from an isolated origin or use a labelled static fallback.

Why does Prettier break ASCII diagrams in HTML files?

Prettier reformats HTML inside div elements with whitespace-pre classes, destroying ASCII layout. Wrap diagrams in a pre element instead, which Prettier leaves untouched, and run prettier --write on the storyboard before committing.

What are the limitations of a mock storyboard?

It is a pre-implementation review artifact, not a permanent record, and should be deleted once the reviewed outcome ships. Static image fallbacks cannot demonstrate scrolling, transitions, focus, or runtime states and must be labelled non-interactive.