🌲
AI EngineeringHTML

Component Decision Tree

by murphytrueman

Component Decision Tree is an AI Engineering 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 Component Decision Tree
Copy Component Decision Tree 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/component-decision-tree ~/.claude/skills/component-decision-tree

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/component-decision-tree/SKILL.md in murphytrueman/design-system-ops
Installs to
~/.claude/skills/component-decision-tree
Collection
One of 25 skills cataloged from this repository
Category
AI Engineering3475 skills

What Component Decision Tree does

Component Decision Tree builds structured YAML decision trees that help agents choose the right component from alternatives. Use it when you need intent-to-component mapping and narrowing questions, not usage guidance for a single component.

Component Decision Tree is cataloged under AI Engineering on DirSkills. Component Decision Tree comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Component decision tree

A skill for building structured decision trees that map user intents and requirements to specific component selections. The output is a queryable framework that AI agents traverse to select the right component for a given need — eliminating the guesswork that leads to component misuse, duplication, and inconsistency.

Context

Component selection is the first decision in any design system interaction, and it is the one that AI agents get wrong most often. The failure mode is not random — it follows predictable patterns. An agent selects a Modal when a Dialog was appropriate. It uses a Card where a List Item fits better. It creates a custom component because it could not find the existing one that serves the need.

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

Frequently asked about Component Decision Tree

  • What else does murphytrueman publish alongside Component Decision Tree?

    Component Decision Tree 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 Component Decision Tree 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 Component Decision Tree compare to other AI Engineering skills?

    Component Decision Tree ranks #3144 by stars among the 3475 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. 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 Component Decision Tree against them. Open each page to compare what they document and how they install.

More from murphytrueman/design-system-ops

Component Decision Tree 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