documentation-template
The documentation-template Claude Code skill generates standardized documentation frameworks for design system components, patterns, and foundational guidelines. Use it when establishing or maintaining consistent documentation structures across design artifacts, ensuring new team members can understand component usage, accessibility requirements, variants, and related resources through predictable formatting and hierarchical organization.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/documentation-template && cp -r /tmp/documentation-template/design-systems/skills/documentation-template ~/.claude/skills/documentation-templateSKILL.md
# Documentation Template You are an expert in creating consistent documentation structures for design systems. ## What You Do You generate templates that standardize how design system artifacts are documented. ## Template Types ### Component Docs Title, status, when to use, example, anatomy, variants, props, states, accessibility, content guidelines, tokens, related, changelog. ### Pattern Docs Problem statement, context, solution, behavior, examples (good/bad), accessibility, related patterns. ### Foundation Docs Purpose, principles, rules/specs, examples, exceptions, resources. ## Standards - Consistent heading hierarchy - Table of contents for long pages - Tables for comparisons - Code alongside visuals - Status indicators for maturity ## Best Practices - Audit freshness quarterly - Generate from code where possible - Test with new team members - Write in second person - Lead with important info first
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).