case-study

GitHub

协助撰写设计作品集案例研究,通过叙事结构展示项目背景、过程、解决方案及业务影响。适用于向外部受众讲述项目故事,强调数据量化与视觉呈现。

designer-toolkit/skills/case-study/SKILL.md Owl-Listener/designer-skills

Trigger Scenarios

需要为作品集或演示文稿撰写设计项目案例 希望以叙事方式展示设计思维与成果

Install

npx skills add Owl-Listener/designer-skills --skill case-study -g -y
More Options

Non-standard path

npx skills add https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/case-study -g -y

Use without installing

npx skills use Owl-Listener/designer-skills@case-study

指定 Agent (Claude Code)

npx skills add Owl-Listener/designer-skills --skill case-study -a claude-code -g -y

安装 repo 全部 skill

npx skills add Owl-Listener/designer-skills --all -g -y

预览 repo 内 skill

npx skills add Owl-Listener/designer-skills --list

SKILL.md

Frontmatter
{
    "name": "case-study",
    "description": "Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`."
}

Case Study

You are an expert in crafting compelling design case studies for portfolios and presentations.

What You Do

You structure case studies that tell the story of a design project, demonstrating process, thinking, and impact.

Case Study Structure

1. Overview

  • Project title and one-line summary
  • Your role and team composition
  • Timeline and scope
  • Key outcome or metric (the hook)

2. Challenge

  • Business context and problem statement
  • User needs and pain points
  • Constraints and requirements
  • Why this problem mattered

3. Process

  • Research methods and key findings
  • Ideation and exploration (show breadth)
  • Key decisions and rationale (show depth)
  • Iteration based on feedback or testing

4. Solution

  • Final design walkthrough
  • Key features and interactions
  • How it addresses the original challenge
  • Design system and technical considerations

5. Impact

  • Quantitative results (metrics, data)
  • Qualitative results (user feedback, team response)
  • Business impact
  • What you would do differently

6. Reflection

  • Key learnings
  • Challenges overcome
  • Skills developed
  • How this work influenced future projects

Visual Storytelling

  • Show the journey, not just the final product
  • Include sketches, wireframes, and iterations
  • Use before/after comparisons
  • Annotate key design decisions
  • Include real screenshots, not just mockups

Writing Tips

  • Write in first person for your contributions
  • Be specific about your role vs team contributions
  • Quantify impact wherever possible
  • Keep it scannable (clear headings, short paragraphs)
  • Edit ruthlessly — shorter is better

Best Practices

  • Lead with the most impressive outcome
  • Show process, but don't document every step
  • Highlight moments of insight or pivots
  • Include enough context for someone unfamiliar
  • Tailor depth to the audience

Version History

  • 20e34c4 Current 2026-08-19 23:20

    优化技能描述,明确使用场景与边界,解决与其他技能的冲突,增强触发准确性。

  • acc3e57 2026-07-25 05:15

Same Skill Collection

design-ops/skills/design-critique/SKILL.md
design-ops/skills/design-debt-audit/SKILL.md
design-ops/skills/design-impact-reporting/SKILL.md
design-ops/skills/design-qa-checklist/SKILL.md
design-ops/skills/design-review-process/SKILL.md
design-ops/skills/design-sprint-plan/SKILL.md
design-ops/skills/handoff-spec/SKILL.md
design-ops/skills/team-workflow/SKILL.md
design-ops/skills/version-control-strategy/SKILL.md
design-research/skills/affinity-diagram/SKILL.md
design-research/skills/card-sort-analysis/SKILL.md
design-research/skills/diary-study-plan/SKILL.md
design-research/skills/empathy-map/SKILL.md
design-research/skills/interview-script/SKILL.md
design-research/skills/jobs-to-be-done/SKILL.md
design-research/skills/journey-map/SKILL.md
design-research/skills/research-repository/SKILL.md
design-research/skills/summarize-interview/SKILL.md
design-research/skills/survey-design/SKILL.md
design-research/skills/usability-test-plan/SKILL.md
design-research/skills/user-persona/SKILL.md
design-systems/skills/accessibility-audit/SKILL.md
design-systems/skills/component-spec/SKILL.md
design-systems/skills/design-system-governance/SKILL.md
design-systems/skills/design-token/SKILL.md
design-systems/skills/documentation-template/SKILL.md
design-systems/skills/icon-system/SKILL.md
design-systems/skills/localization-design/SKILL.md
design-systems/skills/motion-system/SKILL.md
design-systems/skills/naming-convention/SKILL.md
design-systems/skills/pattern-library/SKILL.md
design-systems/skills/theming-system/SKILL.md
designer-toolkit/skills/design-negotiation/SKILL.md
designer-toolkit/skills/design-rationale/SKILL.md
designer-toolkit/skills/design-system-adoption/SKILL.md
designer-toolkit/skills/design-token-audit/SKILL.md
designer-toolkit/skills/presentation-deck/SKILL.md
designer-toolkit/skills/ux-writing/SKILL.md
interaction-design/skills/animation-principles/SKILL.md
interaction-design/skills/conversational-ux/SKILL.md
interaction-design/skills/doherty-threshold/SKILL.md
interaction-design/skills/error-handling-ux/SKILL.md
interaction-design/skills/feedback-patterns/SKILL.md
interaction-design/skills/fitts-law/SKILL.md
interaction-design/skills/form-design/SKILL.md
interaction-design/skills/gesture-patterns/SKILL.md
interaction-design/skills/hicks-law/SKILL.md
interaction-design/skills/interfaces-that-feel/SKILL.md
interaction-design/skills/jakobs-law/SKILL.md

Metadata

Files
0
Version
20e34c4
Hash
bcf066c3
Indexed
2026-07-25 05:15

inicio - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-20 00:56
浙ICP备14020137号-1 $mapa de visitantes$