shadcn-project-workflow
Skill111 starsChanged 5 months agoMITView on GitHub
Work with shadcn/ui in Ordinus. Use when adding, updating, composing, debugging, or styling shadcn-style components; touching components.json; using npx shadcn; changing src/renderer/src/components/ui; applying registry items or presets; or deciding whether to install a UI primitive.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lavishSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- documentation-and-adrsSkill
- electron-secure-boundarySkill
- grill-meSkill
- idea-discoverySkill
- ipc-contract-designSkill
- ordinus-ui-systemSkill
- provider-runtime-adapterSkill
- sqlite-minimal-persistenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 6 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use shadcn/ui as the standard path for reusable UI primitives while preserving Ordinus product direction.
- Very specific: line 12
Use this with ordinus-ui-system: this skill governs shadcn mechanics.
- Very specific: line 13
Use DESIGN.md as the canonical source for theme tokens, component vocabulary, status language, and UI density when changing shadcn-style …
- Very specific: line 17
Run or inspect project context before making component decisions: npm run ui:info
- Very specific: line 19
Read DESIGN.md before changing theme tokens, variants, component styling, status surfaces, or user-facing UI copy.
- Distinctive: line 20
Check existing installed components before adding new ones.
- Very specific: line 21
Prefer shadcn CLI for registry components: npm run ui:add -- <component>
- Distinctive: line 28
Read files added by the CLI and fix imports, aliases, composition, and lint issues.
- Very specific: line 29
Run npm run ui:check, npm run typecheck, npm run lint, and npm run build.
- Very specific: line 36
Run shadcn and npm commands from app unless the user explicitly changes the project layout.
- Distinctive: line 47
Use built-in variants before custom class overrides.
- Very specific: line 48
Use semantic tokens such as bg-background, text-muted-foreground, border, and bg-primary.
- Distinctive: line 49
Avoid raw Tailwind colors for product UI unless adding an intentional semantic token or variant.
- Very specific: line 50
Use gap-* for spacing, not space-x-* or space-y-*.
- Very specific: line 51
Use size-* for equal width and height.
- Very specific: line 52
Use cn() for conditional class composition.
- Distinctive: line 53
Do not apply presets, overwrite components, or change global theme without explicit user approval.
- Distinctive: line 57
Read only the relevant reference when needed:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
shadcn Project Workflow
Objective
Use shadcn/ui as the standard path for reusable UI primitives while preserving Ordinus product direction.
Use this with ordinus-ui-system: this skill governs shadcn mechanics; ordinus-ui-system governs product feel.
Use DESIGN.md as the canonical source for theme tokens, component vocabulary, status language, and UI density when changing shadcn-style components or renderer styling.
Required Workflow
- Run or inspect project context before making component decisions:
npm run ui:info - Read
DESIGN.mdbefore changing theme tokens, variants, component styling, status surfaces, or user-facing UI copy. - Check existing installed components before adding new ones.
- Prefer shadcn CLI for registry components:
npm run ui:add -- <component> - For unfamiliar components, get docs first:
npx shadcn@latest docs <component> - For updates, preview before changing:
npm run ui:add -- <component> --dry-runnpm run ui:add -- <component> --diff <file> - Read files added by the CLI and fix imports, aliases, composition, and lint issues.
- Run
npm run ui:check,npm run typecheck,npm run lint, andnpm run build.
Ordinus Defaults
- Package manager: npm.
- Electron app directory:
app. - Renderer alias:
@renderer/*. - Run shadcn and npm commands from
appunless the user explicitly changes the project layout. - UI components path:
app/src/renderer/src/components/ui. - Utility path:
app/src/renderer/src/lib/utils.ts. - Tailwind version: v3.
- Icon library:
lucide-react. - Product style: calm, operational, work-focused.
Critical Rules
- Align reusable variants and semantic CSS variables with
DESIGN.mdbefore adding one-off styling. - Compose existing components before writing custom styled markup.
- Use built-in variants before custom class overrides.
- Use semantic tokens such as
bg-background,text-muted-foreground,border, andbg-primary. - Avoid raw Tailwind colors for product UI unless adding an intentional semantic token or variant.
- Use
gap-*for spacing, notspace-x-*orspace-y-*. - Use
size-*for equal width and height. - Use
cn()for conditional class composition. - Do not apply presets, overwrite components, or change global theme without explicit user approval.
Detailed References
Read only the relevant reference when needed:
- rules/styling.md for Tailwind and token rules.
- rules/composition.md for component composition and accessibility.
- rules/forms.md for forms and validation layouts.
- rules/icons.md for lucide icon usage.
- rules/base-vs-radix.md for primitive API differences.
- references/cli.md for shadcn CLI commands.
- references/customization.md for theming and CSS variables.
Notes
The official shadcn skill includes broader registry, MCP, asset, and eval infrastructure. Ordinus keeps a smaller adapted version focused on this Electron/Vite app.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

