ideation-prototype

Included with Lifetime

$97 forever

Build interactive React prototypes from selected UI concepts using the web-artifacts-builder skill. Each prototype is a React + TypeScript + Tailwind + shadcn/ui app bundled to a single HTML file. Supports incremental runs. Use when the user says "build prototype", "create HTML", "make it interactive", or invokes /ideation:prototype.

Design

What this skill does


# Ideation Prototype Builder

Build interactive prototypes from selected UI concepts. Each prototype is a React app (TypeScript + Tailwind + shadcn/ui) bundled to a single self-contained HTML file via the **web-artifacts-builder** skill.

## Prerequisites

The `web-artifacts-builder` skill must be installed. Install it with:
```
/install-skill https://skills.sh/anthropics/skills/web-artifacts-builder
```

## Steps

1. **Read both files** from the run folder:
   - `reviewed_solutions.md` — for full solution specs (embedded in blockquotes)
   - `ui_concepts.md` — for ASCII UI concepts

2. **Validate inputs**:
   - Both files exist with valid YAML frontmatter
   - At least 1 solution has UI concepts
   - If invalid, report and stop

3. **Parse user selection**. The user specifies which UI(s) to prototype. Accepted formats:
   - **Pick one**: "Use ui_01_01_C" — Build from that single concept
   - **Combine**: "Combine ui_01_01_C layout with ui_01_01_F's navigation" — Merge elements
   - **Describe**: "Like C but with the data table from E" — Interpret and synthesize
   - **Batch**: "Prototype sol_01_01 and sol_01_02" — Use the first/best concept for each
   - **All**: "Prototype everything" — Use concept A for each passed solution

   If the user doesn't specify, ask which solutions and UI concepts they want prototyped.

4. **Create `prototypes/` directory** inside the run folder if it doesn't exist.

5. **For each selected solution+UI combination**, build a prototype using web-artifacts-builder:

   ### Step 5a: Initialize the React project

   ```bash
   bash scripts/init-artifact.sh {run-folder}/prototypes/solution_{sol_id}
   cd {run-folder}/prototypes/solution_{sol_id}
   ```

   This creates a fully configured project with React 18, TypeScript, Tailwind CSS, and 40+ shadcn/ui components.

   ### Step 5b: Develop the artifact

   Build the React app by editing the generated source files. Translate the selected ASCII UI concept into real components:

   **Content requirements**:
   - Header: solution name, tagline, problem area
   - Footer: `Prototype — {solution_id} — generated {date}`
   - Realistic placeholder data matching the solution's domain (never lorem ipsum)
   - Responsive layout (800px–1400px width)
   - Dark/light mode support via Tailwind's dark mode classes

   **Interaction model fidelity** — match components to the solution type:

   | Model | Build with |
   |-------|-----------|
   | **web** | shadcn/ui Tables, Tabs, NavigationMenu, Accordion, Card. Filterable/sortable data, working nav. |
   | **cli** | Custom terminal component with monospace font, fake command/response pairs, keyboard input handler. |
   | **bot** | Chat layout with message bubbles, ScrollArea, Input + Button for send, typing indicator animation. |
   | **api** | Tabs for methods, code blocks for JSON payloads, a "Try it" Button + response panel. |
   | **notification** | Card list with Badge for read/unread, dismiss buttons, filter Tabs (All/Unread). |
   | **extension** | Browser chrome frame (div mockup), Popover panel, settings Sheet. |
   | **mobile** | Max-width container (~390px), bottom navigation bar, touch-sized Button targets. |
   | **embedded** | Host application frame with embedded widget panel, ResizablePanel for the widget area. |

   **Design guidelines** (from web-artifacts-builder):
   - Avoid excessive centered layouts, purple gradients, uniform rounded corners, and Inter font
   - Use shadcn/ui components and Tailwind utilities — do not write raw CSS unless necessary
   - Keep it visually distinctive and production-grade

   ### Step 5c: Bundle to single HTML

   ```bash
   bash scripts/bundle-artifact.sh
   ```

   This produces `bundle.html` with all JS, CSS, and dependencies inlined.

   ### Step 5d: Move the bundle

   ```bash
   cp bundle.html {run-folder}/prototypes/solution_{sol_id}.html
   ```

6. **Incremental support**: If `prototypes/` already contains `.html` files from a previous run, do not overwrite them unless the user explicitly asks. New prototypes are added alongside existing ones. Project directories from previous builds can be reused if the user wants to iterate.

7. **Report**: List the `.html` files created with their paths. Suggest the user open them in a browser to test.

## Reference

- Build tool: [web-artifacts-builder](https://skills.sh/anthropics/skills/web-artifacts-builder) — React 18 + TypeScript + Vite + Tailwind + shadcn/ui
- Prototype requirements: [html-prototype-spec.md](../ideation/references/html-prototype-spec.md)
- Output path pattern: [data-contracts.md](../ideation/references/data-contracts.md) (Stage 5 section)

Files: 1

Size: 5.1 KB

Complexity: 15/100

Category: Design

Source: https://github.com/kjgarza/marketplace-claude/tree/main/plugins/ideation/skills/ideation-prototype

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts