How We Released a Major Version of Our Design System in 1 Week
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
The monday.com design system team reduced a major version release from five months to one week by encoding the entire breaking-change lifecycle into a Claude Code skill called /vibe-breaking-change. Instead of manually repeating the same workflow (implement, update usages, generate codemod, update docs, validate, open PR) for each change, they captured it as a reusable automated system. Each run starts from a board item, applies the code change, propagates it across the codebase, generates a codemod when applicable, incrementally updates CHANGELOG and MIGRATION_GUIDE, runs build/lint/tests until clean, and opens a fully described pull request — all without manual intervention between steps.
Table of contents
What This Process Usually Looks LikeRealizing a Breaking Change Is Actually a WorkflowTurning Our monday Board Into InputEncoding the Process as a SkillWhat a Single Run Actually Looks LikeWhat Actually ChangedWhere This LeadsSort: