Skip to content
cccskills
FreePublished on GitHub

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).

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill