What is migrate-design-system-to-shadcn?

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.

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.

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.

migrate-design-system-to-shadcn — Skill by bishopZ/2026-Boilerplate

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.

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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.00558
Opus 5.5	$0.00012	$0.00223
Sonnet 5.5	$0.00006	$0.00112
Haiku 4.5	$0.00003	$0.00056

Measured 2mo ago against content hash b18da4d422a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

2mo 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 3mo ago), licensed MIT. It adds 29 tokens to every session and 558 once invoked, about $0.0001 per session on Opus 5.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.

Design and UX Frontend React javascript nodejs passportjs vite

migrate-design-system-to-shadcn next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
migrate-design-system-to-shadcnbishopZ/2026-Boilerplate	Skill	24	3mo ago	MIT	A	29	Claude Code, Codex
build-ghost-app-uiTryGhost/Ghost	Skill	56k	yesterday	MIT	A	45	Claude Code, Codex
building-canvasesPostHog/posthog	Skill	41k	yesterday	none	A	148	Claude Code, Codex
image-studio-ui-testsAutomattic/wp-calypso	Skill	13k	today	GPL-2.0	A	52	Claude Code, Codex
composing-grid-canvasesPostHog/posthog	Skill	41k	yesterday	none	A	136	Claude Code, Codex
formatting-slack-messagesPostHog/posthog	Skill	41k	yesterday	none	A	66	Claude Code, Codex
visualizing-change-over-timePostHog/posthog	Skill	41k	yesterday	none	A	169	Claude Code, Codex