AGENT SKILL

wireframe

Generate JSON wireframe with HTML preview

License 许可
MIT
最近更新
2026-11-06
Stars
★ 0
Forks
0

01 前言 Front Matter

name
wireframe
description
Generate JSON wireframe with HTML preview

02 资源文件 3

03 SKILL.md 正文

/wireframe

Generate a JSON wireframe definition and render it as a self-contained HTML preview.

Input

Two modes:

  1. Conversation: Describe the layout you want to wireframe. Claude generates JSON from the description.
  2. design-id argument: /wireframe {design-id} — reads designs/{design-id}/output/design-spec.md and extracts layout structure from the Information Architecture section.

Output

Two files per screen:

  • {name}.wireframe.json — Machine-readable wireframe definition
  • {name}.wireframe.html — self-contained HTML preview (open in browser)

HTML preview features:

  • Collapsible right panel showing live JSON (syncs on every edit)
  • Drag-and-drop reordering within the same parent
  • Save button (Chrome / Edge — uses File System Access API, first save opens picker, subsequent saves write directly)
  • Copy and Download buttons (all browsers)
  • Panel collapse state persists across sessions via localStorage

Output path:

  • With design-id: designs/{design-id}/output/wireframe/ (automatic)
  • Without design-id: prompted — ask user for directory path

Execution Steps

Step 1: Determine input

If a design-id argument is provided:

  1. Read designs/{design-id}/output/design-spec.md
  2. Extract layout structure from the Information Architecture section
  3. Identify all views/screens described

If no argument:

  1. Use the conversation context to understand the desired layout
  2. Ask clarifying questions if the layout description is ambiguous

Step 2: Load cognitive model and generate wireframe JSON

  1. Load the wireframe designer cognitive model from wireframe-designer.md in this skill's directory
  2. Follow the perception sequence (Phases 1–7) to reason about the layout before producing JSON
  3. Produce a JSON object following the schema below

Schema rules (mechanical — these constrain the JSON format, not design judgment):

  • Every node MUST have a name
  • Layout containers MUST have direction and children
  • Leaf elements SHOULD have a type
  • The JSON maps 1:1 to CSS flexbox — think in flex terms
  • Apply the sizing constraints from the Element types table. In particular: button, link, and text elements must never have fixed width — use height only and let content determine width. input elements use height plus grow or maxWidth, never a fixed width alone

Step 3: Determine output location

Derive {name} (the filename stem) from the JSON name field: English words, lowercase, joined by hyphens. Translate a non-English name into English first.

If design-id was provided:

  • Output directory is designs/{design-id}/output/wireframe/ (no prompt needed)

If no design-id:

  • Ask the user where to save the JSON: "Where should I save the wireframe JSON? Provide a directory path."
  • Use AskUserQuestion with a simple text prompt
  • Create the directory if it doesn't exist

Both .wireframe.json and .wireframe.html go in the same output directory, referred to below as {output_dir}.

Write the JSON to {output_dir}/{name}.wireframe.json with the Write tool.

Step 4: Generate HTML preview

Use a Bash command to splice the JSON into the template. This avoids outputting the ~1300-line template through the Write tool (which is slow because every line becomes output tokens):

python3 -c "
t = open('{skill_dir}/wireframe-template.html').read()
d = open('{output_dir}/{name}.wireframe.json').read()
open('{output_dir}/{name}.wireframe.html', 'w').write(t.replace('const WIREFRAME_DATA = null;', 'const WIREFRAME_DATA = ' + d + ';'))
"

Replace {skill_dir} with the absolute path of the directory that contains this SKILL.md, and {output_dir} and {name} with the values from Step 3. Use absolute paths.

Do NOT read the template with the Read tool or write the HTML with the Write tool. The Python script handles both file operations directly on disk.

Step 5: Output

  1. Open the HTML preview in the browser: open {output_dir}/{name}.wireframe.html
  2. Confirm to the user:
    Wireframe generated:
    - JSON: {output_dir}/{name}.wireframe.json
    - Preview: {output_dir}/{name}.wireframe.html (opened in browser)
    

JSON Wireframe Schema

{
  "name": "Screen Name",
  "viewport": { "width": 1280, "height": 800 },
  "root": {
    "name": "Root",
    "direction": "vertical",
    "children": []
  }
}

Top-level fields

Field Type Required Description
name string Yes Screen/wireframe name
viewport { width, height } Yes Canvas dimensions in px
root node Yes Root layout node

Node fields

Identity:

Field Type Required Description
name string Yes Node label (shown in wireframe)
type string No Element type for placeholder rendering
variant string No Text hierarchy: "display" (32px), "heading" (24px), "caption" (12px). Default body (16px). Only for type: "text".

Layout (for containers with children):

Field Type Default CSS equivalent
direction "vertical" / "horizontal" "vertical" flex-direction
children node[] — child elements
gap number 0 gap (px)
padding number or [v, h] 0 padding (px)
justify string "flex-start" justify-content
align string "stretch" align-items
wrap boolean false flex-wrap: wrap

Sizing:

Field Type Default CSS equivalent
width number — width (px)
height number — height (px)
grow boolean false flex: 1
maxWidth number — max-width (px)

Element types

Type Rendered as Use for Sizing
"text" Gray text label Labels, headings, body text height only. No width — text reflows naturally
"image" Gray box with image icon Photos, thumbnails, hero images width + height, or height + grow
"icon" Small gray circle Action icons, status indicators Fixed width + height always
"button" Rounded rectangle CTAs, primary actions height only. Never width — label length varies
"link" Underlined text Navigation items, secondary actions, text links height only. Never width — label length varies
"input" Bordered rectangle Search fields, form inputs, dropdowns height + grow or maxWidth. Never fixed width alone
"card" Bordered box with light gray fill Content cards, list items height + grow, or height alone in vertical lists
"table" Header row + placeholder data rows Data tables, lists with columns grow or omit. Column widths via columns[].width / columns[].grow
"divider" Thin horizontal line Section separators No sizing needed
(none) Transparent container Structural grouping only grow for flexible, width for fixed (e.g., sidebar)

Table properties

Tables use columns and rows instead of children:

Field Type Default Description
columns array — Column definitions (required for table)
columns[].name string — Column header text
columns[].grow boolean true if width is unset Flexible width (flex: 1). A column without width grows even when grow is omitted
columns[].width number — Fixed width in px
rows number 3 Number of placeholder data rows
{
  "name": "Users Table",
  "type": "table",
  "columns": [
    { "name": "Name", "grow": true },
    { "name": "Email", "grow": true },
    { "name": "Role", "width": 120 },
    { "name": "Status", "width": 100 }
  ],
  "rows": 5
}

Style properties (optional)

Visual properties for downstream consumers. These are purely additive — a wireframe JSON with zero style properties is 100% valid and renders as a monochrome wireframe (current behavior, unchanged). The wireframe HTML renderer ignores style properties.

The /wireframe skill itself produces plain wireframes. Style properties are added by /ui-prompts when a design system is specified, creating a "styled wireframe" that downstream consumers (/pencil-generate, /stitch-generate, Figma Make) use directly.

Field Type Description Applies to
fill string (hex) Background fill color Containers, cards, buttons
color string (hex) Text/icon foreground color Text, icons, links
fontSize number Font size in px Text
fontWeight number Font weight (400, 600) Text
borderRadius number Corner radius in px Containers, cards, buttons, inputs
stroke { color, width } Border definition Containers, cards, inputs
shadow { x, y, blur, color } Drop shadow Containers, cards
opacity number (0–1) Element opacity Any node

Rules:

  • Values MUST be resolved (hex colors, px numbers) — never token names
  • Absence means "use consumer defaults" — omit properties you don't need to specify
  • fill on a container = background; color on text = foreground (avoid ambiguity)
  • stroke and shadow use object notation for clean parsing

Annotation fields:

Field Type Description
_solves string Traces this element to a PRD problem or user need. Metadata only — ignored by all renderers.

Canonical schema: This JSON schema is the canonical layout format used across the pipeline. The ## Layout section in UI prompt files (prompts/*.md) uses this same schema inline, optionally with style properties. Skills that generate prompts (/ui-prompts, /style-exploration, /figma-variation) produce wireframe JSON. Skills that consume prompts (/pencil-generate, /stitch-generate) parse it directly.


Example

A dashboard with proper typographic hierarchy, spacing rhythm, and proportional heights:

{
  "name": "Dashboard",
  "viewport": { "width": 1280, "height": 800 },
  "root": {
    "name": "Page",
    "direction": "vertical",
    "children": [
      {
        "name": "Header",
        "direction": "horizontal",
        "height": 56,
        "padding": [0, 24],
        "justify": "space-between",
        "align": "center",
        "children": [
          { "name": "Logo", "type": "image", "width": 100, "height": 28 },
          { "name": "Search", "type": "input", "grow": true, "maxWidth": 400, "height": 40 },
          { "name": "Avatar", "type": "icon", "width": 32, "height": 32 }
        ]
      },
      {
        "name": "Body",
        "direction": "horizontal",
        "grow": true,
        "children": [
          {
            "name": "Sidebar",
            "width": 240,
            "direction": "vertical",
            "padding": 16,
            "gap": 4,
            "children": [
              { "name": "Overview", "type": "link", "height": 40 },
              { "name": "Projects", "type": "link", "height": 40 },
              { "name": "Settings", "type": "link", "height": 40 }
            ]
          },
          {
            "name": "Main",
            "grow": true,
            "direction": "vertical",
            "padding": 32,
            "gap": 24,
            "children": [
              { "name": "Dashboard", "type": "text", "variant": "display", "height": 48 },
              {
                "name": "Stats Row",
                "direction": "horizontal",
                "gap": 16,
                "children": [
                  { "name": "Total Users", "type": "card", "grow": true, "height": 100 },
                  { "name": "Revenue", "type": "card", "grow": true, "height": 100 },
                  { "name": "Active Today", "type": "card", "grow": true, "height": 100 }
                ]
              },
              {
                "name": "Recent Activity",
                "direction": "vertical",
                "gap": 12,
                "children": [
                  { "name": "Recent Activity", "type": "text", "variant": "heading", "height": 36 },
                  {
                    "name": "Activity Table",
                    "type": "table",
                    "columns": [
                      { "name": "User", "grow": true },
                      { "name": "Action", "grow": true },
                      { "name": "Status", "width": 120 },
                      { "name": "Time", "width": 140 }
                    ],
                    "rows": 6
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  }
}

Cognitive reasoning behind this wireframe:

  • Phase 3 (Task & Scanning Pattern): Dashboard = monitoring intent → F-pattern → top-to-bottom primary content flow, important information along left edge and top
  • Phase 4 (Grid Establishment): Two major zones — sidebar (240px, fixed, persistent navigation) + content area (grow: true). Sidebar exists because content inventory includes navigation that aids the monitoring task.
  • Phase 5 (Hierarchy Assignment): Three levels — display for page identity ("Dashboard"), heading for section identity ("Recent Activity"), body (default) for data content. Caption reserved for table column headers (chrome, not content). Sidebar nav uses link (navigation aids the task but isn't the task itself). Primary CTAs in the content area would use button.
  • Phase 6 (Spacing Logic): Proximity tightens inward — Main padding 32 > section gap 24 > card gap 16 > internal gap 12. Each step inward signals increasing relatedness. Padded containers keep padding ≥ child gap (Main 32 ≥ 24, Sidebar 16 ≥ 4). Unpadded groups (Stats Row, Recent Activity) use a gap smaller than Main's gap of 24, so their children stay aligned with the page title.
  • Phase 7 (Rhythm Verification): Progressive density — spacious at top (title, 48px display text), medium in middle (stat cards, 100px), dense at bottom (table with 6 data rows). Heights accommodate content proportionally.

04 同仓库更多 Skills

mhyahya854
mhyahya854/AI-Second-Brain_Universal-Rules

frontend-slides

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

★ 0
mhyahya854
mhyahya854/AI-Second-Brain_Universal-Rules

design-dna

Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on "design DNA", "extract design style", "analyze design", "design tokens from reference", "generate design from JSON", "design system from screenshot", "design profile", "style guide JSON", "visual effects analysis", "design with effects", "3d design analysis".

★ 0
mhyahya854
mhyahya854/AI-Second-Brain_Universal-Rules

social-publishing

Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.

★ 0
mhyahya854
mhyahya854/AI-Second-Brain_Universal-Rules

hermes-tweet

Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.

★ 0
mhyahya854
mhyahya854/AI-Second-Brain_Universal-Rules

refactoring-ui

Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.

★ 0
mhyahya854
mhyahya854/AI-Second-Brain_Universal-Rules

microinteractions

Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions "microinteraction", "button feedback", "loading state", "toggle design", "animation detail", "state transitions", "input feedback", "the interface feels dead", "make the UI feel responsive", or "add polish to interactions". Also trigger when designing form-validation responses, progress indicators, confirmation dialogs, or any element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

★ 0