agentleFS
Sign inStart free
phoenixvnphoenixvn/claude-code-agency/.claude/skills/wireframe/SKILL.md

wireframe

Skill0 starsChanged 7 months agoMITView on GitHub

Create text-based wireframes for key pages/screens. Desktop Layout (ASCII box wireframe): Mobile Layout: Stacked single-column version with key differences noted. For each content block: - Purpose (what it communicates) - Content requirements (headline, body, image, CTA) - Interactive elements and behavior - Priority (above/below fold) Annotations: - Navigation flow (where does each CTA lead?) - Accessibility notes (heading levels, ARIA landmarks) - Responsive behavior (what stacks, hides, or rearranges)

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use make-tweakable.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bluzirSkill

    make-tweakable

    Add an in-artifact floating Tweaks panel that lets the user adjust colors, fonts, spacing, layout variants live in the preview. Persists via claude-pipe pattern (pending.yaml + apply-tweaks skill).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create text-based wireframes for key pages/screens.

    line 3
  2. Very specific:

    Read sitemap (deliverables/design/sitemap.md), user flows, and design system (if available).

    line 8
  3. Distinctive:

    USER APPROVAL GATE: before proceeding to visual design.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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

/wireframe — Wireframe Creation

Create text-based wireframes for key pages/screens.

Instructions

Phase 1: Context

Read sitemap (deliverables/design/sitemap.md), user flows, and design system (if available).

Phase 2: Page Selection

Use AskUserQuestion: "Which pages should we wireframe?" (multiSelect) Options: based on sitemap pages — typically Homepage, About, Services, Contact, Blog, Product/Landing Page, Dashboard, etc.

Phase 3: Wireframe Creation

For each selected page, spawn ux-lead to create:

Desktop Layout (ASCII box wireframe):

┌─────────────────────────────────────┐
│  Logo          Nav Item | Nav | CTA │
├─────────────────────────────────────┤
│                                     │
│         Hero: Headline + CTA        │
│                                     │
├───────────┬───────────┬─────────────┤
│ Feature 1 │ Feature 2 │ Feature 3   │
├───────────┴───────────┴─────────────┤
│       Social Proof / Testimonials   │
├─────────────────────────────────────┤
│       CTA Section                   │
├─────────────────────────────────────┤
│  Footer: Links | Contact | Social   │
└─────────────────────────────────────┘

Mobile Layout: Stacked single-column version with key differences noted.

For each content block:

  • Purpose (what it communicates)
  • Content requirements (headline, body, image, CTA)
  • Interactive elements and behavior
  • Priority (above/below fold)

Annotations:

  • Navigation flow (where does each CTA lead?)
  • Accessibility notes (heading levels, ARIA landmarks)
  • Responsive behavior (what stacks, hides, or rearranges)

Phase 4: Save

Save each wireframe to deliverables/design/wireframes/[page-name].md.

Phase 5: Review

Present wireframes to user with option to iterate. USER APPROVAL GATE before proceeding to visual design.

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