ai-assist-prototype
Build self-contained, double-click-to-open HTML prototypes so the user can vet an interface before it gets built. One file holds several structurally different variants of a page, app screen, component, flow, or terminal/TUI layout (rendered in-browser), plus a draggable Design Deck for flipping between variants, tuning fonts, colors, spacing, shape, motion and 'feel' with live dials, trying vibe presets, checking viewport sizes and light/dark, pinning comments on elements, and an 'Export to LLM' button that copies the chosen variant and every dial value as a handoff block to paste back to the agent. Use this whenever the user wants to prototype, mock up, wireframe, explore options for, or sanity-check a UI (landing page, dashboard, settings page, onboarding, form, mobile screen, component, CLI/TUI layout), or says 'what should this look like', 'show me a few options', 'let me tweak it before we build', 'vet the design'. Also use it when the user pastes a block starting with 'AI-ASSIST
jparkerweb · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add jparkerweb/ai-assist-skills --skill ai-assist-prototype技能说明
name: ai-assist-prototype description: "Build self-contained, double-click-to-open HTML prototypes so the user can vet an interface before it gets built. One file holds several structurally different variants of a page, app screen, component, flow, or terminal/TUI layout (rendered in-browser), plus a draggable Design Deck for flipping between variants, tuning fonts, colors, spacing, shape, motion and 'feel' with live dials, trying vibe presets, checking viewport sizes and light/dark, pinning comments on elements, and an 'Export to LLM' button that copies the chosen variant and every dial value as a handoff block to paste back to the agent. Use this whenever the user wants to prototype, mock up, wireframe, explore options for, or sanity-check a UI (landing page, dashboard, settings page, onboarding, form, mobile screen, component, CLI/TUI layout), or says 'what should this look like', 'show me a few options', 'let me tweak it before we build', 'vet the design'. Also use it when the user pastes a block starting with 'AI-ASSIST PROTOTYPE HANDOFF': that is this skill's export and tells you which variant and settings they chose. Triggers on: prototype, mockup, wireframe, design options, variations, vet the UI, tweak the look, TUI mockup, design handoff." argument-hint: "[what to prototype, e.g. 'settings page, 3 variants' | or paste an AI-ASSIST PROTOTYPE HANDOFF block]"
Prototype
Build a throwaway-but-polished prototype the user can open by double-clicking, explore, tune, and hand back to you with a structured export. The spine is: brief → plan variants → build one file → verify → hand over → receive the handoff → iterate or implement.
Three ideas make this useful rather than another mockup generator:
- Variants explore structure, dials explore feel. Variants differ in layout, information hierarchy and primary affordance. Colors, fonts, spacing, radius, elevation and motion are live dials that work on every variant, so never spend a variant on a recolor.
- One self-contained file. No server, no build, no dependencies, no account. It survives being emailed to a PM or designer, who can tune it and export their decision without you in the room.
- The export closes the loop. "Export to LLM" copies a handoff block (chosen variant, changed dials, notes, pinned comments, resolved CSS variables). The user pastes it back; you read it and either iterate or implement the real thing.
Modes: detect from the input
| Input | Mode |
|---|---|
| A brief, a feature, a page, "what should this look like", "show me options" | Build (this is the bullseye) |
"add a variant", "make B denser", "tweak the prototype", an existing prototypes/*.html mentioned | Iterate |
A pasted block starting with AI-ASSIST PROTOTYPE HANDOFF or JSON with "schema": "ai-assist-prototype/handoff@1" | Receive (see "Receiving a handoff") |
What you produce
prototypes/<slug>.parts.html: the source you author. A JSON manifest plus one<template data-variant="…">per variant. Small, readable, diffable.prototypes/<slug>.html: the deliverable, assembled byscripts/build-prototype.mjsfrom the parts file and the harness inassets/template.html. Never hand-copy or retype the harness; it is large and must stay intact.
Default location is prototypes/ at the project root (create it). Put it next to the feature instead if the repo clearly organizes design artifacts elsewhere, and follow an explicit user path over either.
The built file contains the Design Deck, a draggable floating panel that:
- flips between variants (◀ ▶, or ← → keys), and between screens inside a variant when the variant declares them
- offers vibe presets (Neutral, Calm, Bold, Editorial, Playful, Technical, Midnight, Mono, plus any you add) and ~25 dials: Feel macros (warmth, energy), Type (display/body fonts from a curated Google Fonts list, base size, scale, line height, tracking, weights), Color (light/dark, accent hue/sat/light, secondary hue shift, neutral hue/tint, surface depth, contrast), Shape (radius, border, elevation), Space (density, container width), Motion, and any custom controls the manifest adds
- previews at Fit / 390 / 820 / 1280 / 1536 widths (each variant is its own document, so real media queries respond)
- collects notes and click-to-pin comments on elements, saves snapshots to compare looks, and persists everything in
localStorageper prototype - Export to LLM copies the handoff block; JSON copies only the JSON; View shows it for manual copy when the clipboard is blocked
TUI prototypes use the same file and deck with a terminal-specific dial set (theme, font, columns/rows, border glyphs, cursor, CRT scanlines).
Step 1: Get the brief (fast)
Pin these down, from $ARGUMENTS, the conversation, and the repo, before planning:
- Subject and audience: what is being designed, for whom, and the one job the screen has.
- The design question: what the prototype should settle ("table or cards?", "wizard or single form?", "does the sidebar earn its space?"). The export carries this brief, so write it as a real sentence.
- Kind:
webby default;tuiwhen the subject is a terminal/CLI tool (ncurses, Ink, Bubble Tea, Textual, ratatui, a curses dashboard, a CLI wizard). - Variant count: default 3, cap 5. Fewer when the question is narrow, never more than five (they stop being different and start being noise).
- Where to save: default
prototypes/<slug>as above.
Look around the repo for things that make the prototype feel like their product rather than a generic page: a DESIGN.md (the ai-assist-design-creator output), tailwind.config.*, CSS custom properties, an existing nav/header, brand name, real entity names and data shapes, existing copy. Seed the manifest defaults and a brand preset from them and use the real content. Say what you reused.
Ask at most one or two questions, and only ones whose answer changes the work (for example, whi
阅读完整来源 ↗