Skip to main content
Agent skill

Wireframe Greybox

A crisp greybox / blueprint lo-fi wireframe — neutral grey blocks on a pale page, image placeholders drawn as a rectangle with a diagonal X, text shown as solid "lorem bars" of varying widths, sharp 1.5–2px borders, and a single monospace redline accent for annotations. Reads like a structural blueprint before any visual design is applied. Use when the brief asks for "greybox", "blueprint wireframe", "lo-fi dashboard", "low fidelity", "线框图", or "灰盒原型".

Get started

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

When to use this skill

Use Wireframe Greybox when an AI agent needs a reusable SKILL.md workflow for this job: A crisp greybox / blueprint lo-fi wireframe — neutral grey blocks on a pale page, image placeholders drawn as a rectangle with a diagonal X, text shown as solid "lorem bars" of varying widths, sharp 1.5–2px borders, and a single monospace redline accent for annotations. Reads like a structural blueprint before any visual design is applied. Use when the brief asks for "greybox", "blueprint wireframe", "lo-fi dashboard", "low fidelity", "线框图", or "灰盒原型".

When not to use it

Skip Wireframe Greybox 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-greybox
# Save SKILL.md to ~/.claude/skills/wireframe-greybox/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/wireframe-greybox/SKILL.md. For a shared project, commit the folder at .claude/skills/wireframe-greybox/ 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 Greybox skill for this task: Stay structural. Ignore any DESIGN.md that pushes finished UI —. 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 Greybox Skill

Produce a single crisp greybox wireframe page. The whole point is *structure, not skin* — communicate hierarchy and layout with neutral grey blocks, never with real color, copy, or imagery. Everything is a placeholder: text is grey "lorem bars", images are rectangles with a diagonal cross, numbers are big solid blocks. The only color on the page is the single redline accent reserved for monospace annotations.

## Workflow

1. **Stay structural.** Ignore any DESIGN.md that pushes finished UI — this is deliberately low fidelity. Use a clean system sans (Inter / system-ui) for shape and a mono (IBM Plex Mono / JetBrains Mono) for the redline annotations only. No hand-drawn fonts, no brand color. 2. **Set the greybox palette.** Page is a pale neutral (`#f7f7f8`), blocks are medium grey (`#e3e3e6`), borders are crisp and defined (`#c9c9cf` for soft edges, `#1c1b1a` for emphasis), and exactly one accent (a blue or coral redline) carries every monospace annotation. Keep contrast high enough to read as a small thumbnail — never near-white-on-white. 3. **Lay out the dashboard**, in order, each on its own `data-od-id`: - **App bar** — a logo greybox, a row of nav lorem-bars, and an avatar circle on the right. - **Sidebar nav** — icon squares + lorem-bar labels; mark one item active with a filled/inverted block. - **KPI row** — four greyboxes, each a small label bar above a big solid "number" bar. - **Chart panel** — an inline SVG greybox: axes plus a few hatched/grey bars or a schematic line. No real data. - **List / table panel** — a header row plus ~5 rows of lorem bars, with one column of image-placeholders drawn as a box with a diagonal X. - **Annotations** — one or two small monospace redlines pinned to the canvas (e.g. `01 · 12-col grid`, `max-width 1280`). 4. **Write** one self-contained HTML document — `<!doctype html>` through `</html>`, CSS inline, no external JS or images. SVG and CSS draw every placeholder. A `max-width` container plus a media query collapses columns under ~1000px. 5. **Self-check.** It should read as a blueprint at thumbnail size: grey blocks, X-crossed image boxes, lorem bars, and exactly one accent color on the monospace redlines. If any greybox is missing, the page looks colored, or it disappears as a blank thumbnail, fix it.

## Output contract

Emit between `<artifact>` tags:

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

One sentence before the artifact, nothing after.

Intended uses

  • Stay structural. Ignore any DESIGN.md that pushes finished UI —
  • Set the greybox palette. Page is a pale neutral (#f7f7f8),
  • Lay out the dashboard, in order, each on its own data-od-id:
  • App bar — a logo greybox, a row of nav lorem-bars, and an
  • Sidebar nav — icon squares + lorem-bar labels; mark one item
  • KPI row — four greyboxes, each a small label bar above a big
  • Chart panel — an inline SVG greybox: axes plus a few
  • List / table panel — a header row plus 5 rows of lorem bars,
  • Annotations — one or two small monospace redlines pinned to the
  • Write one self-contained HTML document — <!doctype html>
  • Self-check. It should read as a blueprint at thumbnail size: grey

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.