wireframe
/wireframe
Use when the user wants to explore the design space quickly — many rough ideas, not one polished direction. Low-fi, handwritten-font sketches; 3–5 structurally distinct options per idea, not recolors.
- Author
- manalkaff ↗
- Repository
- opendesign ↗
- Licence
- MIT
- Last repository change
- 27.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user wants to explore the design space quickly — many rough ideas, not one polished direction. Low-fi, handwritten-font sketches; 3–5 structurally distinct options per idea, not recolors.
Original author description
Use when the user wants to explore the design space quickly — many rough ideas, not one polished direction. Low-fi, handwritten-font sketches; 3–5 structurally distinct options per idea, not recolors.
How it works
- Output location
- Role framing
- Quantity and spread
- Visual style
- Structure of each wireframe
- Tweaks and iteration
- What to avoid
SKILL.md preview
---
name: wireframe
description: Use when the user wants to explore the design space quickly — many rough ideas, not one polished direction. Low-fi, handwritten-font sketches; 3–5 structurally distinct options per idea, not recolors.
---
Loaded when the user wants to explore the design space quickly — many rough ideas, not one polished direction.
## Output location
Write all output files to `./opendesign/mockups/<task-slug>/`. Derive the slug from the task name (e.g. `dashboard-redesign`, `onboarding-flow`).
## Role framing
The goal is breadth, not polish. The output is a map of the design space, not a finished artifact. Use this skill early in a project, before the user has committed to a direction.
Interview the user first to understand the problem, then generate multiple rough takes in one pass.
## Quantity and spread
- Produce 3 to 5 distinctly different approaches per idea. "Distinct" means different structural logic, not different colors of the same layout. If two wireframes could be swapped by changing a class, they are the same wireframe.
- Lay options out side by side so the user can compare them in one glance. For small sets, use a single canvas. For larger sets, use tabbed or paginated groupings so the comparison stays readable.
## Visual style
- Low-fidelity, sketchy vibe. Handwritten-but-readable fonts (e.g. Caveat, Patrick Hand, Shadows Into Light, Kalam).
- Mostly black and white. Sparing color accents only to call out active or emphasized elements.
- Simple shapes: rectangles, lines, circles. No real imagery, no real icons. Placeholder text is fine and expected.
- No polished typography. No real brand colors. No hover states. These are thinking aids, not mockups.
## Structure of each wireframe
- Focus on layout and flow. Where things sit, what reads as primary, what sequence the user moves through.
- Label sections clearly in plain language ("search bar", "filters", "results list", "primary action") so the user can discuss them without pointing.
- When a wireframe implies an interaction, annotate it with a short note. Do not implement it.
## Tweaks and iteration
- Expose a small set of simple tweaks: toggle between variants, change density, swap an optional section in or out. Keep the tweak surface minimal. Wireframes should not compete with prototypes for fidelity.
## What to avoid
- Do not polish a wireframe. If the user likes one, the next step is a separate higher-fidelity pass — not sanding down the sketch.
- Do not let wireframes converge visually. If five options all look the same, you have one option, not five.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · manalkaff/opendesign | 90 | MIT |
| paperclipai/paperclip | 100 | MIT |
| bendrucker/claude | 100 | MIT |
| kurtstohrer/wireframe | 100 | MIT |
| teezeit/wiremd | 100 | MIT |
| event4u-app/agent-config | 90 | MIT |
| yesith0106/craft3d | 87 | MIT |
Database snapshot: 13.11.2026 · package version b8edb4274bb7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ux-polish
Visual design quality skill — elevates HTML wireframes from structural prototypes to polished UI. Applies typography, color, spacing, motion, interaction polish. Works on /ux-wireframe output or any HTML. Use when "ux polish", "polish wireframe", "colorize", "design audit",… - 95design-spec
[Project Management] Use when a workflow step or the user asks for UI/UX specs for views, flows, states and accessibility. --mode=wireframe converts sketches or wireframes. - 95design-spec
[Project Management] Use when a workflow step or the user asks for UI/UX specs for views, flows, states and accessibility. --mode=wireframe converts sketches or wireframes. - 100wireframe-explorations
Builds three to five lo-fi HTML wireframe options for a product surface that differ in approach rather than styling, with real data and a contact sheet to compare them. Use when a product doc and user journey exist and the user says "explore approaches", "wireframes", "lo-fi… - 90wireframe-progressive
Progressive UX generation — Phase 1 generates 5 B&W wireframe options instantly (1 safe + 4 exploratory), then Phase 2 renders Clean + Polished color variants via 5 parallel Task agents (one per option). Supports wireframes-only or wireframes+visuals. Extracts optimization… - 90wireframe-spec
Specify wireframe layout — content priority, component placement, and annotation. Use when defining structure before visual design. For grid mechanics, use `layout-grid` (ui-design).