migrate-design-system-to-shadcn

migrate-design-system-to-shadcn is a skill for Claude Code, Codex from bishopZ/2026-Boilerplate. It costs 29 tokens per session (558 once invoked), scanned A, original, MIT.

A migration guide for replacing Chakra UI, a React component library, with shadcn/ui, a collection of components built into the project. It requires removing Chakra packages and code while preserving accessibility, routing, and existing feature behavior.

In plain words
What is it for?
Use it to migrate the client UI, update dependencies and providers, replace Chakra components, and check that routes, themes, translations, state management, and accessibility continue to work.
Why use it?
It provides a defined path for changing the client interface system without leaving old Chakra dependencies behind. It also highlights behavior and keyboard-access requirements that could otherwise be lost during the migration.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it to migrate the client UI, update dependencies and providers, replace Chakra components, and check that routes, themes, translations, state management, and accessibility continue to work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bishopz/2026-boilerplate/migrate-design-system-to-shadcn
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add bishopZ/2026-Boilerplate --skill migrate-design-system-to-shadcn
Clone the repo
git clone --depth 1 https://github.com/bishopZ/2026-Boilerplate

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for migrate-design-system-to-shadcn

README.md
[![agentmods](https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-design-system-to-shadcn/github.svg)](https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-design-system-to-shadcn)
Your own site
<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-design-system-to-shadcn"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-design-system-to-shadcn/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for migrate-design-system-to-shadcn

Your own site · 80×15
<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-design-system-to-shadcn"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-design-system-to-shadcn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 558 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00558
Opus 5 $0.00015 $0.00279
Sonnet 5 $0.00006 $0.00112
Haiku 4.5 $0.00003 $0.00056

Measured 12d ago against content hash b18da4d422a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

migrate-design-system-to-shadcn scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/migrate-design-system-to-shadcn/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migrate Design System to shadcn/ui

Use this skill when replacing Chakra UI with shadcn/ui as the primary component system.

Goal

Adopt shadcn/ui for component primitives and styling, and completely remove Chakra UI from the repository.

Hard Requirement

At completion, no Chakra runtime or Chakra-specific code should remain:

  • no @chakra-ui/* dependencies
  • no Chakra providers/components/hooks
  • no Chakra-specific imports in client code

Files To Update

1) Dependencies (package.json)

  • Add shadcn prerequisites (typically Tailwind CSS + required utility libs).
  • Install selected shadcn component dependencies.
  • Remove Chakra packages:
    • @chakra-ui/react
    • @emotion/react
    • @emotion/styled
    • any Chakra-only addons

2) App/provider bootstrap

  • Replace Chakra provider setup in src/client/main.tsx.
  • Keep existing Redux, i18n, and theme responsibilities functioning after migration.

3) Component migration

  • Replace components in:
    • src/client/ui/components/
    • src/client/ui/layout/
    • src/client/pages/
  • Preserve accessibility semantics, focus states, and keyboard interactions.
  • Keep route behavior and existing feature logic unchanged.

4) Styling system migration

  • Introduce shadcn-compatible global styling strategy.
  • Move Chakra prop-based styles to className/utility-driven styles.
  • Keep dark/light mode behavior equivalent (or document differences explicitly).

5) Docs and guidance

  • Update docs where Chakra is referenced:
    • README.md
    • AGENTS.md
    • docs/ARCHITECTURE.md
    • docs/TECHNOLOGY.md
  • Add CHANGELOG.md entry in Unreleased.

Validation Checklist

  • Run npm run lint
  • Run npm run type-check
  • Run focused E2E tests for primary UI flows:
    • playwright/e2e/auth/login.spec.ts
    • playwright/e2e/accessibility/skip-link.spec.ts
    • playwright/e2e/layout/footer-position.spec.ts
  • Verify Chakra is fully removed:
    • rg \"@chakra-ui|Chakra|chakra\" src package.json docs AGENTS.md

Read the full file on GitHub · 80 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 80 lines · 29 tokens per session scan A b18da4d422a5

Subscribe to this mod's changes

migrate-design-system-to-shadcn is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 558 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

quill-code

Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the…

PostHog/posthog · 84 tokens

stitch-react-vite-dashboard

Convert approved Stitch exports into accessible React and Vite dashboards with DESIGN.md tokens, TanStack Query data boundaries, responsive layouts, and optional read-only Web3 integrations.

PracticalSwan/agent-skills · 40 tokens

3d-web-experience

Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing dep.

ranbot-ai/awesome-skills · 53 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

compiler-port

Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.

react/react · 35 tokens

migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

oxc-project/oxc · 44 tokens