wireframe-spec — Claude Code skill: what it does, how to install
Defines wireframe layout specifications, content priorities, and interaction notes. Useful when structuring an interface before moving into visual UI design.
npx skills add Owl-Listener/designer-skills --skill wireframe-spec -a claude-codeWhat wireframe-spec does
The skill creates layout specifications before any visual styling begins. It details content blocks like navigation bars, hero sections, media cards, forms, and footers. Each section gets assigned a loading priority, approximate character counts, image aspect ratios, and content sources such as a CMS or an API.
Specifications explicitly capture interface states: empty, loading, populated, and error. Visual styling is excluded — conventions restrict layouts to grayscale without color accents. The skill does not calculate layout grids. For column mechanics, the author directs users to layout-grid.
What it helps with
- specify wireframe layout hierarchy before visual styling
- define content priorities and character count requirements
- document interaction notes for hover and click events
- outline interface states for loading, errors, and empty views
Example prompts for the agent
- Create a wireframe-spec for the checkout page including error states
- Specify the user profile layout with content priorities and interaction notes
- Prepare an annotated dashboard specification across desktop and mobile breakpoints
How to install wireframe-spec
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill wireframe-spec -a claude-code2Manually: put the files in place
~/.claude/skills/wireframe-spec/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wireframe-spec/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill wireframe-spec -a codex2Manually: put the files in place
.agents/skills/wireframe-spec/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill wireframe-spec -a cursor2Manually: put the files in place
.cursor/skills/wireframe-spec/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills wireframe-spec2Manually: put the files in place
.github/skills/wireframe-spec/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill wireframe-spec -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path prototyping-testing/skills/wireframe-specManually: put the files in place
.devin/skills/wireframe-spec/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill wireframe-spec -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about wireframe-spec
How do I install wireframe-spec in Claude Code?
Run npx skills add Owl-Listener/designer-skills --skill wireframe-spec -a claude-code in your terminal.
What does the wireframe-spec skill do?
It generates annotated wireframe specifications defining component hierarchy, interaction behaviors, and responsive breakpoint requirements.
Does wireframe-spec handle layout grids?
No, the skill focuses strictly on content hierarchy and layout structure. For grid mechanics and columns, use the layout-grid skill.
Source text
SKILL.md · MIT
--- name: wireframe-spec description: Specify wireframe layout — content priority, component placement, and annotation. Use when defining structure before visual design. For grid mechanics, use `layout-grid` (ui-design). --- # Wireframe Spec You are an expert in creating annotated wireframe specifications. ## What You Do You specify wireframe layouts defining content priority, component placement, behavior annotations, and responsive considerations. ## Wireframe Components ### Content Blocks - Headers and navigation - Hero/feature areas - Content sections (text, media, cards) - Forms and input areas - Footers and secondary navigation ### Annotations - Content priority numbers (what loads/appears first) - Interaction notes (what happens on click/hover) - Dynamic content indicators (personalized, data-driven) - Responsive behavior notes - Accessibility notes ### Content Specifications - Heading hierarchy (H1, H2, H3) - Approximate text length/character counts - Image aspect ratios and sizing - Required vs optional content - Content source (static, CMS, API) ## Fidelity Levels - **Sketch**: Hand-drawn boxes and labels - **Low-fi**: Gray boxes with content labels - **Mid-fi**: Realistic layout with placeholder content - **Annotated**: Mid-fi plus detailed behavior specs ## Wireframe Conventions - Use gray/black/white only (no color decisions) - X-box for images - Wavy lines for text blocks - Real labels for navigation and buttons - Consistent component representation ## Best Practices - Focus on content hierarchy, not visual design - Annotate behavior, not just layout - Show multiple states (empty, loading, populated, error) - Include responsive breakpoint versions - Get content strategy input early
© Owl-Listener · MIT · Owl-Listener/designer-skills