菜单
Install, configure, and use shadcn/ui in React-style projects. Use when a repo needs shadcn/ui initialization, component installation, monorepo UI package setup, components.json review, registry or MCP guidance, or UI composition rules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Diagnose failed or unreliable agent workflows by classifying bad assumptions, missing observations, tool misuse, wrapper failures, hidden repair loops, incomplete validation, handoff gaps, and repeated failure patterns. Use after a failed harness run, flaky agent output, or confusing validation loop.
Review agent-generated changes against project rules. Use when asked for a review, before opening a PR, after large Codex edits, or when checking diffs for correctness, security, architecture, tests, docs drift, dependencies, migrations, and release risk.
Generate or maintain a minimal high-signal AGENTS.md for coding agents. Use whenever a repo needs agent instructions, an existing AGENTS.md is too long or vague, or project docs/scripts need a concise routing map for Codex.
Define and mechanically enforce architecture boundaries for a repo. Use when a project needs allowed dependency rules, forbidden imports, layer documentation, dependency maps, circular dependency checks, or protection against agent-created architectural drift.
Scaffold a new TypeScript web, mobile, API, or full-stack project with Better-T-Stack, then harden it with the Pax Fullstack Harness. Use whenever the user wants a new TypeScript app scaffold, mentions Better-T-Stack, asks for a modern type-safe stack, or wants Codex to start a repo that is agent-ready from day one.
Use guided Chrome DevTools MCP setup and workflows for browser runtime debugging. Use when a web app needs console, network, DOM, accessibility, Lighthouse, performance, responsive, or live-browser investigation beyond normal tests.
| name | shadcn-ui-integrator |
| description | Install, configure, and use shadcn/ui in React-style projects. Use when a repo needs shadcn/ui initialization, component installation, monorepo UI package setup, components.json review, registry or MCP guidance, or UI composition rules. |
Make shadcn/ui usable in the target repo without guessing framework, aliases, component ownership, or registry setup.
components.json, Tailwind config, UI package, app directory, aliases, and existing componentsDetect setup state.
components.json exists, read it before adding components.bunx, pnpm uses pnpm dlx, npm uses npx, and Yarn uses yarn dlx.<runner> shadcn@latest init -t <framework>.next, vite, start, react-router, and astro.Handle monorepos.
packages/ui.components.json.Add components deliberately.
<runner> shadcn@latest add <component> or the repo's established command.$click-path-and-browser-qa when component changes affect user workflows or browser acceptance paths.Document usage.
docs/development/ui.md from assets/templates/shadcn-ui-usage.md.tmpl.docs/quality/golden-patterns.md with preferred composition examples.[mcp_servers.shadcn] command = "npx" and args = ["shadcn@latest", "mcp"] to ~/.codex/config.toml when desired.project-local-skill-generator to create project-ui-workflow when UI docs, component paths, and e2e commands are stable.components.json paths and aliases match generated imports.