unocss-shadcn
unocss-shadcn
Overview
Apply a deterministic setup flow for UnoCSS and unocss-preset-shadcn without running automatic installers. Detect monorepo strictly, route component targets by project shape, and enforce shadcn MCP plus manual-mode component creation.
Core Rules
- Run in semi-automatic mode only: propose commands and file edits, but do not auto-install dependencies.
- Detect monorepo only when one of these is true:
pnpm-workspace.yamlexists at repo root.- Root
package.jsoncontainsworkspaces.
- Use destination policy:
- Monorepo:
packages/shadcn-ui - Single project:
src/components
- UnoCSS config location policy:
- Monorepo: configure in each
apps/<app>/uno.config.*(NOT at repo root or in packages). - Single project: configure at project root
uno.config.*.
- Default to
presetWind4unless the user explicitly requests a different version (e.g.presetWind3). - For monorepo component package dependencies, write shadcn-related runtime items to
peerDependencies. - Use shadcn MCP before any component usage or creation.
More from jsonlee12138/prompts
design-patterns-principles
Use when a request asks for software design patterns or design principles, including explanations, comparisons, summaries, or quick reference grounded in local docs.
16vite-tanstack
TanStack (Router/Query/Form/Table) configuration guide for Vite + React projects. Covers Vite plugin setup, main.tsx registration, DevTools configuration, and editor settings. Use when setting up or reviewing TanStack config in a Vite project. Triggers on: vite-tanstack, tanstack config, tanstack router setup, tanstack query setup, tanstack form setup, tanstack table setup.
15eslint-config
Use when configuring ESLint with @antfu/eslint-config for a single project or a monorepo workspace, including flat config setup, shared config packages, commit quality hooks, or migrations from legacy ESLint configs.
10brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Turn rough ideas into validated brainstorming/design docs through one-question-at-a-time dialogue, role-based analysis, and explicit user approval. Use when users ask to brainstorm, shape requirements, compare approaches, or produce a planning/design document before implementation.
4solo-ops
>
1claude-design
Unified design workflow router for critique, accessibility review, developer handoff, design system work, UX copy, user research, and research synthesis. Use when users ask naturally for design feedback, mockup review, a11y audit, handoff specs, UX writing, research planning, research synthesis, or mention Figma, Pencil, or HTML design workflows and should not need to invoke separate sub-skills manually.
1