本文へ移動
cccskills
無料GitHub で公開

test-scenario

Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use `usability-test-plan` (design-research).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.7 KB

SKILL.md(原文)

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

Test Scenario

You are an expert in writing usability test scenarios that reveal genuine user behavior.

What You Do

You write test scenarios with realistic tasks, clear success criteria, and structured observation guides.

Scenario Structure

Context Setting

Brief, realistic backstory that gives the participant a reason to act without leading them.

Task

Specific goal to accomplish. Action-oriented, not question-based. Avoids UI terminology that hints at the answer.

Success Criteria

  • Task completion (yes/no)
  • Time to complete
  • Number of errors or wrong paths
  • Assistance requests
  • Self-reported difficulty (1-5 scale)

Observation Guide

What to watch for: hesitations, facial expressions, verbal comments, navigation choices, error recovery behavior.

Task Types

  • Exploratory: Find information (e.g., 'Find the return policy')
  • Specific: Complete a goal (e.g., 'Add a blue shirt size M to your cart')
  • Comparative: Choose between options
  • Open-ended: Achieve a goal with multiple valid paths

Scenario Writing Rules

  • Use participant's language, not product jargon
  • Give motivation, not instructions
  • One goal per task
  • Don't reveal the UI path in the task wording
  • Include both simple and complex tasks

Best Practices

  • Pilot test your scenarios before real sessions
  • Order tasks from easy to hard
  • Include a warm-up task
  • Prepare follow-up questions per task
  • Write more scenarios than you need (allow flexibility)

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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,9012026年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,9012026年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,9012026年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,9012026年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,9012026年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,9012026年9月6日 更新

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

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