skills.rest
hulusi-tunc
hulusi-tuncCOMMUNITY
Explore all skills by this author →
GitHub

decision-documentation

Record accessibility decisions with rationale in a structured ADR-style format.

3|Updated Mar 28, 2026
Search Tags:#documentation#accessibility#adr#reasoning#design-system#tradeoffs#decision-record
One-click install
npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill decision-documentation-hulusi-tunc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-documentation
Source: https://github.com/hulusi-tunc/unicorn-skills/tree/main/.claude/skills/accessibility-decisions--decision-documentation
Command: npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill decision-documentation-hulusi-tunc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document accessibility decisions so that future teams understand not just what was decided, but why — preventing regressions when team composition changes.

Core Features & Use Cases

  • Create structured decision records (ADR-style) for accessibility tradeoffs.
  • Capture context, decisions, alternatives considered, risks, and supporting evidence to guide future work.
  • Use in onboarding, audits, and design-system governance to preserve rationale over time.

Quick Start

Record a recent accessibility decision by detailing the title, date, context, decision, alternatives, impact, and evidence.

Frequently Asked Questions about decision-documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document accessibility decisions to prevent regressions when team composition changes?▼

Document accessibility decisions using an ADR-style format that captures context, alternatives considered, impact, and supporting evidence to preserve rationale over time for future teams.

What is the best way to record accessibility tradeoffs for design-system governance?▼

Record accessibility tradeoffs in a structured decision record detailing the title, date, context, decision, alternatives, impact, and evidence to guide future design-system governance, audits, and onboarding.

How do I create a decision record for accessibility choices during an audit?▼

Create an accessibility decision record by detailing the title, date, context, decision, alternatives considered, impact, and supporting evidence to explain why specific tradeoffs were made during the audit.

Why should I use an ADR format for accessibility decisions instead of standard documentation?▼

An ADR format for accessibility decisions preserves not just what was decided but why, capturing context, alternatives, and evidence to prevent regressions when team composition changes during onboarding or audits.

Can I use decision documentation for onboarding new team members on accessibility rationale?▼

Yes, decision documentation captures accessibility reasoning and tradeoffs in a structured ADR format, providing context, alternatives, and evidence so new team members understand why specific choices were made.

When do I need to record accessibility tradeoffs in a decision record?▼

Record accessibility tradeoffs in a decision record whenever choices involve context, alternatives, and impact that future teams need to understand for onboarding, audits, or design-system governance.

Related Skills

Explore More Design & Creative Skills→
SylphxAISylphxAI
4

uiux

Generate design system documentation with tokens and WCAG AA accessibility criteria.

Official
Basic
d0whc3rd0whc3r
2

documentation-and-adrs

Record architectural decision rationale using a structured ADR template.

Community
Basic
1479089714790897
7

kwp-design-design-system

Audit component libraries for naming inconsistencies and missing documentation.

Community
Intermediate
hulusi-tunchulusi-tunc
3

document

Document feature accessibility decisions, tradeoffs, and WCAG compliance mappings.

Community
Advanced