Wireframe Spec

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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

Instructions onlyDesign & Creative
AI-generated overview

Specifies annotated wireframe layouts covering content priority, component placement, behavior notes, and responsive states.

What it does
This skill guides the creation of annotated wireframe specifications that define content priority, component placement, behavior annotations, and responsive considerations. It covers content blocks, annotation types, content specifications, fidelity levels, and wireframe conventions. The output is a structured wireframe spec document rather than visual design or code.
When to use it
Use it when defining page or screen structure before visual design begins. It fits early product and UX planning where content hierarchy, states, and responsive behavior need to be documented.
Requirements
No scripts or tools are required; it is an instructions-only skill.

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

Source and attribution

Source:owl-listener/designer-skillsinprototyping-testing/skills/wireframe-specat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal