agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/claude-wireframe-skill/SKILL.md

claude-wireframe-skill

Skill32 starsChanged 6 months agoMITView on GitHub

Generates 5 UX design approaches as interactive prototypes — 1 safe design-system extension and 4 exploratory variants — starting as B&W wireframes then producing color variants via parallel agents. Scans codebase on first run to build persistent design context.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you want a fast single-pass result without parallel agent overhead

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

claude-wireframe-skill

Catalogue stub — full skill: Magdoub/claude-wireframe-skill

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed? Upstream names this skill wireframe, so it installs next to this pointer (the pointer is not replaced).
    • Global: f=~/.agents/skills/wireframe/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/wireframe/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as wireframe, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/claude-wireframe-skill ] && echo "global" || echo "project"

    Global:

    npx skills add Magdoub/claude-wireframe-skill --skill wireframe -g -y

    Project:

    npx skills add Magdoub/claude-wireframe-skill --skill wireframe -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Heads-up

  • License: MIT
  • Name collision: wireframe is also written by wireframe-skill (its install or its catalogue pointer); installing both overwrites the earlier one.
<!-- das:install:end -->

Invoke after install

  • Skill name: wireframe
  • Trigger phrases: "claude-wireframe-skill", "5 UX approaches", "exploratory wireframe", "Magdoub wireframe"

What it does

Launches a multi-agent wireframing workflow that produces 5 distinct UX design approaches for any given UI problem: 1 safe variant that extends the existing design system and 4 exploratory variants that challenge conventions. The skill first scans the codebase to extract persistent design context (colors, components, patterns), then produces black-and-white wireframes before generating color variants in parallel. Useful when you need divergent thinking, not just a single best guess. On first run it asks for screenshots of your current app and writes a wireframe/ folder (design-taste and design-context files plus the generated HTML) into the project root.

When NOT to use

  • Single wireframe output — use wireframer, or wireframe-skill (a different skill that installs into the same wireframe directory, so keep only one of the two)
  • Excalidraw diagrams — use excalidraw-diagram instead
  • When you want a fast single-pass result without parallel agent overhead

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free