Skip to content
Skillpedia
Interfaces (UI/UX)101k · #512

wireframe-annotated

Creates wireframes with detailed annotations to specify the design. It helps communicate engineering and UX requirements clearly.

What it does

Creates a simple draft of a desktop marketing page, using grey boxes for elements and numbered callouts for explanations. The goal is to show structure and provide instructions, not the final design.

When to use it

  • ✓To plan the structure of a new page.
  • ✓To explain to a developer how a page should be laid out.
  • ✓To get feedback on the layout before detailing the design.

Example of what to ask your AI

“Create an annotated wireframe for a landing page for a new music app.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/nexu-io/open-design/blob/main/design-templates/wireframe-annotated/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/nexu-io/open-design/blob/main/design-templates/wireframe-annotated/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The AI draws grey boxes for page elements within a browser frame. Numbers appear on these boxes and in a side panel, where each number has a brief technical or usability note.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add nexu-io/open-design --skill wireframe-annotated

Or download just the file:

curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/design-templates/wireframe-annotated/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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.

FAQ

Why is the page all grey and without detail?

The focus is on structure and instructions, not the final appearance. The grey boxes help visualize the layout without visual distractions.

What are the annotation notes?

These are short descriptions accompanying each number, providing details about the functionality or design intent of each page section, such as size, behavior, or purpose.

Can I ask for colors or detailed images?

No, this tool is designed to be simple and focused on structure. It uses only grayscale and one accent color for numbers, and placeholders for images.

Details

Original description by the author

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 whe

repo: nexu-io/open-design

Popularity

GitHub stars
101k
Ranking position
#512
License
Apache-2.0
Updated
10/16/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills