Wireframe Sketch
A hand-drawn wireframe exploration — graph-paper background, marker / pencil tone, multiple tab labels for variants, sticky-note annotations, scribbled chart placeholders, hatched fills. Reads like a designer's whiteboard before any pixels are committed. Use when the brief asks for "wireframe", "sketch wireframe", "hand-drawn", "lo-fi", "whiteboard", "草稿", or "手绘原型".
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Wireframe Sketch when an AI agent needs a reusable SKILL.md workflow for this job: A hand-drawn wireframe exploration — graph-paper background, marker / pencil tone, multiple tab labels for variants, sticky-note annotations, scribbled chart placeholders, hatched fills. Reads like a designer's whiteboard before any pixels are committed. Use when the brief asks for "wireframe", "sketch wireframe", "hand-drawn", "lo-fi", "whiteboard", "草稿", or "手绘原型".
When not to use it
Skip Wireframe Sketch 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?
mkdir -p ~/.claude/skills/wireframe-sketch # Save SKILL.md to ~/.claude/skills/wireframe-sketch/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/wireframe-sketch/SKILL.md. For a shared project, commit the folder at .claude/skills/wireframe-sketch/ instead.
- 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.
- 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.
Use the Wireframe Sketch skill for this task: Skip the DESIGN.md if it pushes for finished UI. This skill explicitly. 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 Sketch Skill
Produce a single hand-drawn wireframe page. The whole point is "this is a sketch" — looseness is the brand. Lean into pencil/marker tones, hatched fills, dashed borders, slight rotations.
## Workflow
1. **Skip the DESIGN.md** if it pushes for finished UI. This skill explicitly wants a low-fidelity look. Only honor type tokens loosely (system serif for headlines, mono for annotations, marker font fallback). 2. **Pick the screen variants** from the brief — typically 3–4 tab labels like "01 · A · ORGANIZED", "02 · B · DASHBOARD", etc. One is "active", the rest are inactive sketch tabs. 3. **Layout**, in order: - **Page header** — bold serif title with a fake "WIREFRAME v0.1" tag pinned next to it (dashed border, slight rotation). Below: one-line subtitle in marker italic + a date / device / fidelity dateline on the right in mono. - **Tab strip** — 4–5 labels with marker check-square glyphs. The active one has a highlighter swipe behind it (yellow / orange tint + slight skew). - **Sketch canvas** — a graph-paper card (background: 24px × 24px grid drawn with `linear-gradient` lines), with a thick rounded border drawn to look like a sharpie line. - **Browser chrome row** — three sketched circles + a fake URL bar with a hand-written-style URL. - **Sidebar nav** — sketched checkbox + label for each nav item, marker italic. One has a highlighter line through it (active). - **KPI tiles** — 3–4 boxes, each with a chunky scribbled number in a marker-style stroke, a tiny accent stamp, and a one-line label. - **Chart placeholder** — a card with a hand-drawn axis and a wobbly polyline. Add 3–4 dot markers. - **Bar chart placeholder** — a card with hatched-fill rectangles of varying heights. - **Sticky notes** — 1–2 yellow / pink notes with marker text, taped with a slightly rotated band, pinned over key regions to call out "next step", "page-1", or "needs review". 4. **Write** a single HTML document: - `<!doctype html>` through `</html>`, CSS inline. - Use the system's available "Caveat", "Patrick Hand", or "Architects Daughter" fonts via Google Fonts; otherwise fall back to italic serif. - Slight rotations everywhere (`transform: rotate(-0.6deg)`) to break the grid and feel hand-drawn. - `data-od-id` on header, tabs, sidebar, KPIs, chart, bar-chart, sticky notes. 5. **Self-check**: - The page should *not* look pixel-perfect. If it does, you over-rendered. - Marker / pencil + graph paper + hatched fills + sticky notes are all present; if any is missing, add it. - The active tab has the highlighter swipe; the others don't.
## 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
- Skip the DESIGN.md if it pushes for finished UI. This skill explicitly
- Pick the screen variants from the brief — typically 3–4 tab labels
- Layout, in order:
- Page header — bold serif title with a fake "WIREFRAME v0.1" tag
- Tab strip — 4–5 labels with marker check-square glyphs. The active
- Sketch canvas — a graph-paper card (background: 24px × 24px grid
- Browser chrome row — three sketched circles + a fake URL bar with
- Sidebar nav — sketched checkbox + label for each nav item, marker
- KPI tiles — 3–4 boxes, each with a chunky scribbled number in a
- Chart placeholder — a card with a hand-drawn axis and a wobbly
- Bar chart placeholder — a card with hatched-fill rectangles of
- Sticky notes — 1–2 yellow / pink notes with marker text, taped
- Write a single HTML document:
- <!doctype html> through </html>, CSS inline.
- Use the system's available "Caveat", "Patrick Hand", or "Architects
- Slight rotations everywhere (transform: rotate(-0.6deg)) to break
- data-od-id on header, tabs, sidebar, KPIs, chart, bar-chart,
- Self-check:
- The page should not look pixel-perfect. If it does, you over-rendered.
- Marker / pencil + graph paper + hatched fills + sticky notes are all
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.