← LeaderboardThe Skill Leaderboard

wireframe-spec

Specify wireframe layout — content priority, component placement, and annotation. Use when defining structure before visual design. For grid mechanics, use `layout-grid` (ui-design).

Published by Owl-Listener ↗Owl-Listener/designer-skills

Try your first task

wireframe-spec

Start a fresh conversation. Replace the highlighted placeholders.

Use wireframe-spec to produce an annotated responsive wireframe specification for [page or flow], including hierarchy, component placement, content states, and content-source requirements.

Required inputs

  • [page or flow]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: wireframe-specdescription: 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