📝
WritingHTML

Decision Record

by murphytrueman

Decision Record is a Writing skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22
claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills
Install in seconds
Install Decision Record
Copy Decision Record into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/decision-record ~/.claude/skills/decision-record

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/decision-record/SKILL.md in murphytrueman/design-system-ops
Installs to
~/.claude/skills/decision-record
Collection
One of 25 skills cataloged from this repository
Category
Writing1328 skills

What Decision Record does

Decision Record creates a structured narrative document for design system choices, including context, options, trade-offs, and rationale. Use it when you need to capture why a decision was made for future reference.

Decision Record is cataloged under Writing on DirSkills. Decision Record comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Decision record

A skill for creating structured decision records for design system choices. Covers component decisions, token architecture choices, tooling selections, governance policies, and any other decision worth recording so future contributors do not have to reverse-engineer the reasoning.

Context

Design systems accumulate decisions faster than they accumulate documentation. The result is a system where the current state is known but the reasoning is not — which means the same debates recur, constraints get ignored because their origin is forgotten, and new team members spend weeks learning by collision what a thirty-minute conversation would have covered.

This is the opening of the README. Read the full README on GitHub.

Commands Decision Record provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

  • /decisions
  • /adr

Frequently asked about Decision Record

  • What else does murphytrueman publish alongside Decision Record?

    Decision Record is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Accessibility Per Component and Adoption Report. Each one is a separate skill with its own page in this directory, installs the same way Decision Record does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.

  • How does Decision Record compare to other Writing skills?

    Decision Record ranks #1134 by stars among the 1328 Writing skills in this catalog. The most-starred ones next to it are Article Writing, Social Media Content Calendar and Knowledge Comic Creator. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Decision Record against them. Open each page to compare what they document and how they install.

More from murphytrueman/design-system-ops

Decision Record is one of 25 skills cataloged on DirSkills from murphytrueman/design-system-ops.

See all 25 skills
🤖
2h ago

AI Component Description

AI Component Description generates six-section prose descriptions for components so LLMs can understand purpose, props, composition, accessibility, and examples. Use it when writing Figma MCP descriptions or other text meant to make components legible to Claude and similar agents.
AI Engineering
1767
2h ago

Accessibility Per Component

Accessibility Per Component runs a structured accessibility audit on a single design system component. It checks keyboard use, screen reader behavior, colour contrast, focus, and ARIA against WCAG 2.1 AA.
Quality
1767
📈
2h ago

Adoption Report

Adoption Report separates design system coverage from actual adoption, with trend direction and risk flags. Use it when you need to measure which teams are using the system and where usage is low or declining.
Data
1767
🗂️
2h ago

Backlog Generator

Backlog Generator turns audit findings into sprint-ready work items with titles, effort estimates, acceptance criteria, and rationale. Use it when you need to convert review output into actionable tickets instead of running an audit or defining contribution guidelines.
Automation
1767
⚙️
2h ago

CI/CD Integration

CI/CD Integration generates pipeline files that automate design system checks such as token validation, component linting, accessibility scans, visual regression, and release gating. Use it when you need CI to enforce the same rules audit skills check manually.
DevOps
1767
📣
2h ago

Change Communication

Change Communication produces release notes, migration guidance, and team announcements for design system changes that have already been decided. Use it when you need to communicate a patch, enhancement, breaking change, or system update to consuming teams.
Writing
1767