Designing Wireframes

Create ASCII wireframes for every screen and window, user flow diagrams, and per-screen states (empty, loading, error) from a requirements document, for desktop (macOS windows, menu-bar popovers, settings), web (responsive app shells), and mobile. Writes into the requirements document in place, or into a separate file the caller names. Use when asked for a wireframe, screen layout, screen design, window layout, or user flow, to visualize screens before implementation, or as the UX stage of kicking-off-apps.

5 starsFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tomada1114/tomada-claude-plugins

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tomada1114/tomada-claude-plugins --skill designing-wireframes
Manual install
git clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/designing-wireframes ~/.claude/skills/designing-wireframes

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Designing Wireframes

**Before:** `refining-requirements`. **Alongside:** `ui-ux-designing` owns app-wide UX
policy (navigation model, state rules, validation, motion, accessibility targets); this
skill owns what each screen looks like and how a user moves between them.
**After:** `planning-tickets`.

## Input and output

Input is a requirements document. Output goes to the path the caller names (the kickoff
passes a separate `ux-flows.md`); with no path, add the wireframes to the requirements
document in place, section by section.

## 1. Screen inventory

List every screen, window, sheet, and popover the MVP features need, with the feature
section each serves. Show the list to the user before drawing: a missing or extra
screen is cheaper to catch here than after twenty diagrams.

## 2. Wireframes

Draw each screen with ASCII or box-drawing characters, following the platform's
conventions:

- **Desktop / web:** [templates/desktop-web-patterns.md](templates/desktop-web-patterns.md) —
  minimum window size and what collapses first, the shortcut for every primary action,
  menu-bar placement of every command on macOS, breakpoints on the web.
- **Mobile:** [templates/mobile-patterns.md](templates/mobile-patterns.md) — primary
  actions in the reachable bottom zone, destructive and rare actions higher up.

Annotate with real values from the requirements (labels, limits, sizes), and draw the
empty, loading, and error variants of each screen that has them.

## 3. Flows
Read the full skill on GitHub

Details

Skill name
designing-wireframes
Path
tomada-kit/skills/designing-wireframes/SKILL.md
Repo updated
12 November 2026

FAQ

What does the Designing Wireframes skill do?

Create ASCII wireframes for every screen and window, user flow diagrams, and per-screen states (empty, loading, error) from a requirements document, for desktop (macOS windows, menu-bar popovers, settings), web (responsive app shells), and mobile. Writes into the requirements document in place, or into a separate file the caller names. Use when asked for a wireframe, screen layout, screen design, window layout, or user flow, to visualize screens before implementation, or as the UX stage of kicking-off-apps.

How do I install the Designing Wireframes skill?

Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Designing Wireframes popular?

It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.

Related skills

Auditing Prompt Docs

5

tomada1114/tomada-claude-plugins

Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m

AI, LLMs & Agents

Auditing Repositories

5

tomada1114/tomada-claude-plugins

Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst

Testing & QA

Authoring Goal Prompts

5

tomada1114/tomada-claude-plugins

Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de

AI, LLMs & Agents

Kicking Off Apps

5

tomada1114/tomada-claude-plugins

Take a rough app idea ("I want an app that…") to a new public GitHub repository cut from one of the user's template repositories, with signed-off requirements, UX flows, a researched design system, design decisions in the template's skills (no architecture docs), loose project permissions, and a dependency-ordered issue backlog for the template's shipping-issues. Orchestrates one child skill per stage — refining-requirements, designing-wireframes, ui-ux-designing, a design skill, bootstrapping-from-templates, configuring-project-permissions, designing-architecture, planning-tickets — and defer

Frontend & Design

Bun HTMLRewriter

9

jarle/bun-skills

Use Bun's HTMLRewriter to transform HTML documents with CSS selectors

Frontend & Design

Refero Design

5

tomada1114/tomada-claude-plugins

Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this even when the user does not mention Refero and even when live Refero MCP tools are not configured. Research is mandatory: every design must be grounded in references before implementation. Provides research-first methodology, bundled craft knowledge, reference locks, decision ledg

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.