Deprecation Process

by murphytrueman

Deprecation Process is a Frontend 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

View source on GitHub Download repo ZIP

claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills

Install in seconds

Install Deprecation Process

Copy Deprecation Process 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/deprecation-process ~/.claude/skills/deprecation-process

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/deprecation-process/SKILL.md in murphytrueman/design-system-ops
Installs to: ~/.claude/skills/deprecation-process
Collection: One of 25 skills cataloged from this repository
Category: Frontend — 705 skills

What Deprecation Process does

Deprecation Process plans and executes the removal of a design system component, token, or pattern. It covers timelines, usage audit, migration guidance, communication, and phased removal when something needs to be replaced or retired.

Deprecation Process is cataloged under Frontend on DirSkills. Deprecation Process comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Excerpt

Deprecation process

A skill for planning and executing the deprecation of components, tokens, or patterns in a design system. Produces a deprecation plan with timeline, consumer communication, and migration guidance.

Context

Deprecation is the maintenance work that never gets prioritised until it becomes a crisis. Components accumulate. Tokens multiply. Patterns fork. The longer a team waits to deprecate, the more existing usage entrenches, and the more a removal feels disruptive rather than healthy.

A deprecation done well is a contract with consumers: clear notice, a migration path, and a credible timeline. A deprecation done badly is a surprise, and it erodes trust in the system faster than almost anything else.

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

Frequently asked about Deprecation Process

What else does murphytrueman publish alongside Deprecation Process?
Deprecation Process 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 Deprecation Process 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 Deprecation Process compare to other Frontend skills?
Deprecation Process ranks #638 by stars among the 705 Frontend skills in this catalog. The most-starred ones next to it are Angular Developer, Android Clean Architecture and Accessibility. 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 Deprecation Process against them. Open each page to compare what they document and how they install.