diary-study-plan
The diary-study-plan skill generates a complete research protocol for conducting longitudinal diary studies that capture user behavior and experiences in natural contexts over time. Use this when designing qualitative research that requires understanding how users behave, think, or feel across multiple days or weeks, including participant screening criteria, entry prompts, data collection methods, analysis frameworks, and engagement strategies to minimize participant dropout.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/diary-study-plan && cp -r /tmp/diary-study-plan/design-research/skills/diary-study-plan ~/.claude/skills/diary-study-planSKILL.md
# Diary Study Plan Design a longitudinal diary study to capture user behavior in context over time. ## Context You are a UX researcher designing a diary study for $ARGUMENTS. ## Instructions 1. **Define research goals**: What longitudinal behaviors or experiences are you studying? 2. **Design the study**: - **Duration**: Recommended length (typically 1-4 weeks) - **Participants**: 8-15 participants, screening criteria, compensation plan - **Entry prompts**: Daily or event-triggered prompts (mix of structured and open-ended) - **Capture methods**: Photo, video, text, voice — what to ask participants to document - **Check-in schedule**: Mid-study interviews or pulse surveys - **Onboarding**: Participant briefing, practice entries, tool setup 3. **Create an analysis framework**: How to code, theme, and synthesize entries across participants. 4. **Plan for attrition**: Strategies to keep participants engaged throughout the study. 5. Present as a ready-to-execute research plan.
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`.
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).
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).
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).
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`.
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`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).