菜单
The craft of building design exploration prototypes. Covers file structure, control wiring, styling conventions, and output validation. Preloaded into the html-prototyper agent. Not intended for direct invocation.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tmchow/tmc-marketplace --skill design-prototyping命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Explore radically different design approaches for any page, component, or feature. Use when the user wants to compare multiple distinct visual directions side by side — not build one specific thing, but see several fundamentally different takes on the same UI. Signals: "explore designs for", "show me different ways to design", "radically different approaches", "what could this look like", "design exploration", "let's see some options before we commit", "different layout approaches", "different visual identities for the same content", wanting to see multiple families or variations before choosing a direction. Also triggers when the user pastes design exploration feedback (starts with "## Design Exploration Feedback") to iterate on a previous round, or pastes a design direction ("## Design Direction") to finalize. Do NOT trigger for building one specific design, visual refreshes, design critiques, brainstorming without visual output, single widget prototypes, or comparing CSS frameworks.
Review PRDs, brainstorm docs, tech plans, design docs, specs, or any planning document for issues. This skill should be used whenever the user wants feedback, critique, or a quality check on an existing planning or requirements document — even if they don't use the word "review." Common triggers include: "review the plan", "check the PRD", "critique my tech plan", "what's wrong with this plan", "poke holes in the requirements", "is this plan solid", "take a look at this spec", "give feedback on the brainstorm", or pointing to a doc file and asking if anything is off. Also triggers after writing a PRD or tech plan (to review what was just created), or when invoked by brainstorming or tech-planning skills. Do NOT trigger for code review (PRs, diffs, source files), writing/creating new plans, debugging, or reviewing non-planning documents (READMEs, CLAUDE.md, test coverage).
This skill should be used when the user says "review my code", "check these changes", or wants feedback on code before creating a PR. Also used after completing a task during iterative implementation.
基于 SOC 职业分类
正在显示 SKILL.md
| name | design-prototyping |
| description | The craft of building design exploration prototypes. Covers file structure, control wiring, styling conventions, and output validation. Preloaded into the html-prototyper agent. Not intended for direct invocation. |
| user-invocable | false |
| disable-model-invocation | false |
How to build a single self-contained design exploration variation file.
Every variation is a single HTML file with embedded metadata. The file is a complete page rendered inside an iframe in the gallery shell.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<script src="https://cdn.tailwindcss.com"></script>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<!-- Google Fonts <link> for specified fonts -->
<script type="application/json" id="variation-meta">
{
"id": "A1",
"family": "A",
"familyName": "...",
"name": "...",
"layoutType": "...",
"aesthetic": "...",
"description": "...",
"controls": [ /* control objects — see Control Schema below */ ]
}
</script>
<style>
:root {
/* All theme values as CSS custom properties */
}
:root * {
transition: color 0.3s ease, background-color 0.3s ease,
border-color 0.3s ease, padding 0.3s ease,
gap 0.3s ease, font-size 0.3s ease,
border-radius 0.3s ease, box-shadow 0.3s ease,
max-width 0.3s ease, width 0.3s ease;
}
</style>
</head>
<body>
<!-- Variation content -->
</body>
</html>
The <script type="application/json" id="variation-meta"> block in <head> contains valid JSON with:
| Field | Type | Description |
|---|---|---|
id | string | Variation code, e.g. "A1", "B2" |
family | string | Family letter, e.g. "A" |
familyName | string | Human-readable family name |
name | string | Memorable variation name |
layoutType | string | Layout description, e.g. "Sidebar + Cards" |
aesthetic | string | Aesthetic description, e.g. "Clean Light" |
description | string | One-line description of the variation |
controls | array | 4-6 control objects (see schema below) |
Populate all fields from the variation brief provided in the prompt.
<style> only for: :root property definitions, @keyframes, transitions, scrollbar styling.:root. All theme values: colors, fonts, spacing, radii. Unprefixed names: --bg, --text, --accent. Never --shell-*. Reference via Tailwind arbitrary values: bg-[var(--bg)], text-[var(--text)], rounded-[var(--radius)].min-h-screen flex items-center justify-center p-8 on <body>.overflow-hidden (or overflow-auto if scrolling is intentional). This prevents content from breaking out of the iframe bounds. Apply to the root layout wrapper, not <body>.:root * { transition: ... } rule (shown in file format above) must be included for smooth control changes.Controls are JSON metadata only. Define them in the controls array inside the variation-meta block. A separate gallery shell reads this JSON and renders the control UI (sliders, dropdowns, toggles) outside the iframe.
Do NOT build any control panel, settings panel, or configuration UI into the variation HTML. The variation contains only the design content. All control rendering and interaction is handled by the shell.
Include 4-6 controls in the controls array.
CSS controls (default) — The shell sets a CSS custom property on :root via style.setProperty(). The HTML references it via var(). This is automatic — no JS needed in the variation. Use for visual parameters: colors, spacing, radii, opacity, font sizes, layout widths.
Event controls — For behavioral parameters that CSS can't express (sort order, filter thresholds, data grouping, expansion mode). The shell sets the CSS var AND dispatches a CustomEvent on the iframe's document. The variation includes a JS listener that reads the value and updates the DOM.
To make a control an event control, add "event": true to the control JSON. The shell dispatches control-change events with { detail: { id, value } } for all controls, but only event controls need a listener.
Event controls still need a cssVar (it can be a dummy like "--sort-order") so the shell has something to set. The actual work happens in your listener.
Value + unit are set directly on the CSS var.
{
"id": "sidebar-width",
"label": "Sidebar Width",
"type": "range",
"min": 180, "max": 320, "step": 10,
"options": null,
"value": 240,
"defaultValue": 240,
"unit": "px",
"cssVar": "--sidebar-width"
}
Maps option labels to CSS values via cssValues.
{
"id": "accent",
"label": "Accent Color",
"type": "select",
"min": null, "max": null, "step": null,
"options": ["coral", "teal", "indigo", "amber"],
"cssValues": { "coral": "#e07a5f", "teal": "#4a9e8f", "indigo": "#5c6bc0", "amber": "#d4a853" },
"value"
When one control changes multiple CSS properties, use an object as the cssValues value and set cssVar: null.
{
"id": "mood",
"label": "Mood",
"type": "select",
"min": null, "max": null, "step": null,
"options": ["light", "dark", "midnight"],
"cssValues": {
"light": { "--bg": "#faf9f7", "--text": "#2d2a26", "--text-dim": "#8a8580", "--border": "#e5e0d8" }
Maps true/false to CSS values. Without cssValues, defaults to "1"/"0".
{
"id": "show-dividers",
"label": "Show Dividers",
"type": "toggle",
"min": null, "max": null, "step": null,
"options": null,
"cssValues": { "true": "1px", "false": "0px" },
"value": true,
"defaultValue": true,
"unit": "",
"cssVar":
When a control needs to drive behavior (not just CSS), mark it with "event": true and add a listener in the variation's <script>:
{
"id": "sort-order",
"label": "Sort By",
"type": "select",
"options": ["status", "last-active", "name"],
"cssValues": { "status": "status", "last-active": "last-active", "name": "name" },
"value": "status",
"defaultValue": "status",
"unit": "",
"cssVar": "--sort-order",
"event": true
}
<script>
document.addEventListener('control-change', (e) => {
const { id, value } = e.detail;
if (id === 'sort-order') {
sortAgents(value); // your function that re-sorts the DOM
}
});
// Also handle initial state — controls-ready fires once after all
// CSS vars are set on first iframe load
document.addEventListener('controls-ready', () => {
const sort = getComputedStyle(document.documentElement)
.getPropertyValue('--sort-order').trim();
if (sort) sortAgents(sort);
});
</script>
The controls-ready event fires once after all controls are applied on iframe load. Use it to read initial CSS var values and set up initial state. Individual control-change events fire on each subsequent control adjustment.
id is required. Unique within the variation. Without it, the control renders but interactions do nothing.value and defaultValue must always be set. Never null or undefined.cssValues must be an object keyed by option labels, never an array. { "compact": "0.75rem" } not ["0.75rem", "1rem"].unit: "%" on range controls. The % breaks calc() expressions. Use unitless values and let CSS handle the math: calc(var(--opacity) * 1%).cssValues. Without it, the CSS var gets a label string like --bg: warm which is useless to CSS.cssVar must be consumed in the HTML. Reference via Tailwind arbitrary values (rounded-[var(--card-radius)]) or in CSS. A control that defines --card-radius is dead if the HTML uses rounded-xl instead.var() for controlled properties. Hover, active, and focus states must reference CSS vars, not hardcoded values. Use color-mix() for derived colors: color-mix(in srgb, var(--accent) 10%, transparent).[style*="..."] attribute selectors for CSS variable detection. They are fragile.:root only. Not scoped by class. The iframe provides isolation. Controls apply via documentElement.style.setProperty().var() references."event": true and a JS listener. If a control drives behavior (sorting, filtering, thresholds, expansion mode), mark it "event": true and add a control-change event listener. Without the listener, the CSS var is set but nothing reads it.CRITICAL: The metadata block MUST use exactly id="variation-meta". This ID is machine-parsed by the assembly script. Not variation-metadata, not exploration-metadata — exactly variation-meta. If the ID is wrong, the variation will silently fail to appear in the gallery.
Verify before writing:
<script type="application/json" id="variation-meta"> block is in <head> with valid JSONid field (unique within this variation)cssVar appears as var(--xxx) in the HTML or is consumed by a control-change event listenercssValues is an object keyed by option labels, never an arrayvar() references, no CSS class togglingunit: "%"var() for any property driven by a control<template> open tag has a matching </template> close tag (balanced nesting is safe; orphaned close tags break assembly):root (not scoped by class)<head>overflow-hidden or overflow-autoAfter writing the HTML, before finishing, audit every control against its wiring:
For each control in the controls array:
var(--{cssVar}) or the control-change listener handling its id.var() reference to the HTML where the property should apply, or (b) add a control-change listener if the control is behavioral.This audit catches the most common failure mode: controls that are defined in JSON but have no effect on the rendered output.
</template> tags. Every </template> must have a matching <template> open tag. The assembly system wraps each file in a <template> element; an orphaned close tag would break the wrapper. Balanced <template> nesting (e.g., Alpine.js <template x-for>, <template x-if>) is safe.