Skip to main content
Agent skill

Wireframe Annotated

An annotated / redline lo-fi wireframe — a desktop landing/marketing page drawn as flat greyboxes inside a browser chrome frame, overlaid with numbered annotation pins (①②③④⑤) in a single accent color, paired with a right-hand SPEC PANEL that lists each numbered pin with a short engineering / UX note. This is the "wireframe + redline spec" style — clean, flat, low-fidelity, NOT hand-drawn. Use when the brief asks for "annotated wireframe", "redline wireframe", "wireframe with spec", "lo-fi landing wireframe", "low fidelity", "线框图", "标注线框", or "redline".

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Wireframe Annotated when an AI agent needs a reusable SKILL.md workflow for this job: An annotated / redline lo-fi wireframe — a desktop landing/marketing page drawn as flat greyboxes inside a browser chrome frame, overlaid with numbered annotation pins (①②③④⑤) in a single accent color, paired with a right-hand SPEC PANEL that lists each numbered pin with a short engineering / UX note. This is the "wireframe + redline spec" style — clean, flat, low-fidelity, NOT hand-drawn. Use when the brief asks for "annotated wireframe", "redline wireframe", "wireframe with spec", "lo-fi landing wireframe", "low fidelity", "线框图", "标注线框", or "redline".

When not to use it

Skip Wireframe Annotated when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/wireframe-annotated
# Save SKILL.md to ~/.claude/skills/wireframe-annotated/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/wireframe-annotated/SKILL.md. For a shared project, commit the folder at .claude/skills/wireframe-annotated/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Wireframe Annotated skill for this task: Skip finished UI. This skill explicitly wants a low-fidelity greybox. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Wireframe Annotated Skill

Produce a single flat, low-fidelity landing-page wireframe with a redline spec. The whole point is "structure + handoff notes, not pixels" — greyboxes carry the layout, numbered pins call out regions, and a right-hand spec panel turns each pin into a short engineering / UX note. Keep it clean and flat; never hand-drawn or scribbly.

## Workflow

1. **Skip finished UI.** This skill explicitly wants a low-fidelity greybox look. Honor type tokens only loosely (one clean sans like Inter / system-ui for labels, one mono like IBM Plex Mono for the spec notes and pin numbers). Use medium-grey fills with defined darker borders so the page reads as a thumbnail — avoid near-white-on-white, which renders blank.

2. **Set the two-column shell.** LEFT is the wireframe canvas: a browser-chrome framed greybox page. RIGHT is a narrow "ANNOTATIONS / SPEC" panel. Pick ONE accent color (coral or blue) and use it ONLY for the numbered pins and the matching spec numbers — everything else stays greyscale.

3. **Lay out the canvas**, top to bottom, each block a greybox with a numbered pin absolutely positioned on it: - **Top nav** — logo greybox + nav lorem-bars + a primary button block. Pin ①. - **Hero** — big headline lorem bars + subhead + two CTA button blocks on the left; a large image placeholder (rect with a diagonal X) on the right. Pin ②. - **Logo strip** — a row of 5 small greybox partner logos. Pin ③. - **Feature grid** — 3 cards, each an icon square + title bar + 2 text bars. Pin ④. - **Footer** — columns of lorem link-bars. Pin ⑤.

4. **Mirror every pin in the spec panel.** Each spec row = the circled number in the accent color + a short mono/sans note, e.g. "① Sticky nav, 64px, condenses on scroll", "② Hero H1 48/56, CTA pair primary+ghost", "③ 5 partner logos, greyscale", "④ 3-up at ≥960px → 1-up mobile", "⑤ 4-col footer, legal row". Mark the panel and each row with `data-od-id`.

5. **Self-check**: - Every numbered pin on the canvas has exactly one matching spec row. - The accent color appears ONLY on pins + spec numbers; the rest is greyscale. - The page should read clearly at thumbnail size; if blocks vanish into the background, darken the fills/borders. - It must NOT look pixel-perfect or hand-drawn — flat greyboxes only.

## Output contract

Emit between `<artifact>` tags:

``` <artifact identifier="wireframe-slug" type="text/html" title="Annotated Wireframe — Title"> <!doctype html> <html>...</html> </artifact> ```

One sentence before the artifact, nothing after.

Intended uses

  • Skip finished UI. This skill explicitly wants a low-fidelity greybox
  • Set the two-column shell. LEFT is the wireframe canvas: a browser-chrome
  • Lay out the canvas, top to bottom, each block a greybox with a numbered
  • Top nav — logo greybox + nav lorem-bars + a primary button block. Pin ①.
  • Hero — big headline lorem bars + subhead + two CTA button blocks on the
  • Logo strip — a row of 5 small greybox partner logos. Pin ③.
  • Feature grid — 3 cards, each an icon square + title bar + 2 text bars. Pin ④.
  • Footer — columns of lorem link-bars. Pin ⑤.
  • Mirror every pin in the spec panel. Each spec row = the circled number in
  • Self-check:
  • Every numbered pin on the canvas has exactly one matching spec row.
  • The accent color appears ONLY on pins + spec numbers; the rest is greyscale.
  • The page should read clearly at thumbnail size; if blocks vanish into the
  • It must NOT look pixel-perfect or hand-drawn — flat greyboxes only.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.