DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to block new UI drift in CI with a design system check with Design How

Fail the build when a screen stops following the design system's tokens and components.

Who it is forA developer on a team whose new screens keep adding one-off colors and spacing after the design system is in place.

The problemWithout an automatic check, every new screen can quietly pick a different gray, radius or button.

The outcomeA check script that fails when a screen drifts from the system, run locally and in CI.

What you need first

  • A coding agent that reads skills, such as Claude Code
  • Node.js, since the install and scripts run through npx and node
  • Your app in a git repository, since the skills commit to a run branch
  • Playwright and a Chromium browser for the scripts that drive a browser

Steps

  1. Install the skills with npx skills@latest add arla6ka/design.how --skill build-design-system.
  2. Locate check-system.mjs in the installed build-design-system skill folder and run it with --help to read its options. (inferred, check the README)
  3. Run check-system.mjs --self-test to confirm the script works in your environment. (inferred, check the README)
  4. Add the same check command as a step in your CI configuration so it runs on each pull request. (inferred, check the README)

Prompt for your agent

In the arla6ka/design.how repo's build-design-system skill, find check-system.mjs, run its --help and --self-test, then add a CI step in <target CI config path> that runs it. Expected output: a passing self-test and a CI step. Verify the step fails on a deliberately drifted screen.

Caveat. The README names check-system.mjs and says the system can be enforced in CI, but it does not show the CI configuration, so the exact wiring is up to you.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page