Inside the Chakra UI Plugin for Claude Code

What is the chakra-ui/chakra-ui plugin, actually

chakra-ui/chakra-ui is the Claude Code plugin published straight from Chakra UI's own GitHub repository (40,595 stars, by Flowy's own count), not a third party wrapper built around it. Flowy indexes the repository the way it indexes every crawled plugin: it reads the manifest and lists what actually ships inside, it does not own, bundle, or host the code. The repository's own summary calls Chakra UI a component system for building SaaS products with speed, and Flowy files this listing under the Development category.

The plugin ships 7 components in total: 3 skills, 2 agents, and 2 commands. Read together, they split cleanly into two audiences: people building an interface with Chakra UI, and people working inside the Chakra UI and Ark UI codebases themselves. Install it from the listing page linked at the top of this guide, since that page generates the current install command rather than a copy that can drift out of date.

Which skills help you build or migrate a Chakra UI interface

All three skills are aimed at everyday interface work, not at the Chakra UI project itself.

chakra-ui-builder is the one for starting something new. It builds responsive, accessible components and layouts, installs or configures Chakra UI in a new or existing project, and designs themes using tokens, semantic tokens, recipes, and slot recipes.

chakra-ui-refactor is for code that already exists. It reviews Chakra UI code for issues, converts plain HTML and CSS, Tailwind, CSS Modules, or styled-components into Chakra UI, and cleans up messy components, fixing layout structure or token issues along the way.

chakra-ui-migrate is scoped to one job: moving a project from Chakra UI v2 to v3. Its description lists exactly what it covers, package changes, codemods, provider setup, color mode, prop renaming, compound components, theming, recipes, and Next.js updates. Reach for this one when an upgrade or a breaking change is the actual problem, not a general cleanup.

What do the ark-ui-version-bumper and github-issue-triage agents do

Both agents are maintenance tooling for the Chakra UI project, not for an application built on top of it.

ark-ui-version-bumper is described as a dependency management specialist for the Chakra UI project, with knowledge of Ark UI integration, monorepo package management, and version synchronization. That is a maintainer's job, keeping package versions in step across a monorepo that pulls in Ark UI, not something an outside application team would normally touch.

github-issue-triage is described as an issue triage engineer for the Chakra UI component library, working to debug, reproduce, and fix reported issues. It is built for running a real issue queue, not for debugging arbitrary application code.

What do the ark and github-reviewer commands do

The two commands are short, specific actions rather than open-ended skills.

ark implements a new Ark UI component. It sits on the same contributor facing side of the plugin as the ark-ui-version-bumper agent above it.

github-reviewer drafts a response for a GitHub issue, the kind of writing a maintainer repeats often enough to want a shortcut for.

Is this plugin for building with Chakra UI, or for contributing to it

Both, and the plugin draws a clean line between the two. The 3 skills, chakra-ui-builder, chakra-ui-refactor, and chakra-ui-migrate, are for anyone shipping a product with Chakra UI, whether or not they have ever opened the Chakra UI repository. The 2 agents and 2 commands are for people working inside that repository: bumping Ark UI versions, triaging issues, implementing new Ark UI components, and drafting issue responses. If you only build application UI, the skills are the reason to install this plugin, and the agents and commands will sit unused. If you contribute to Chakra UI or Ark UI directly, it runs the other way around.

How do I install it

Flowy indexes chakra-ui/chakra-ui from its public GitHub repository; it does not host or bundle these components. Install from the listing page linked at the top of this guide rather than from a command written into this text, since the listing page is what stays current. Once installed, check which of the two groups above, interface work or project maintenance, actually matches what you are trying to do, since most readers only need one of them.