本文へ移動
cccskills
無料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).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Owl-Listener のスキルをすべて見る

このスキルの問題を報告する