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

wireframe-sketch

Creates sketch-style wireframes, like on a whiteboard. It's useful for quickly exploring ideas and getting initial design feedback.

What it does

This agent creates a hand-drawn sketch of a website or app screen, like a draft on graph paper using a marker or pencil. Its purpose is to show initial design ideas without focusing on the final look.

When to use it

  • ✓When you want to show an initial design concept.
  • ✓When the request asks for a 'sketch' or 'wireframe'.
  • ✓To present an idea before deciding on visual details.

Example of what to ask your AI

“Create a wireframe sketch for the homepage of a to-do list 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-sketch/SKILL.md

Ready-to-paste message

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

It uses a hand-drawn style with graph paper, sticky notes, and elements like tabs and checkboxes. The output is an HTML file that looks like a quick draft.

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-sketch

Or download just the file:

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

Original text by the author, straight from GitHub.

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.

FAQ

Why doesn't the output look like a finished website?

The goal is to be a low-fidelity sketch, showing the structure and main ideas, not the final appearance. This helps focus on functionality before visual details.

What are 'tab labels' and 'sticky notes'?

'Tab labels' are like navigation tabs in a browser or program. 'Sticky notes' are the small notes designers use to jot down ideas or next steps.

Can I request specific colors?

The focus is on the sketch style, using pencil/marker tones and some highlight colors like yellow or orange for markings. It's not designed for final customization with specific colors.

Details

Original description by the author

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 "手绘原型".

repo: nexu-io/open-design

Popularity

GitHub stars
101k
Ranking position
#515
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