Borrowing it
Nothing to install: this file belongs to muratgur/ordinus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/muratgur/ordinus/master/.claude/skills/shadcn-project-workflow/SKILL.mdgit clone --depth 1 https://github.com/muratgur/ordinusWrote 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.
[](https://agentmods.dev/skills/muratgur/ordinus/shadcn-project-workflow)<a href="https://agentmods.dev/skills/muratgur/ordinus/shadcn-project-workflow"><img src="https://agentmods.dev/badge/skills/muratgur/ordinus/shadcn-project-workflow/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.
<a href="https://agentmods.dev/skills/muratgur/ordinus/shadcn-project-workflow"><img src="https://agentmods.dev/badge/skills/muratgur/ordinus/shadcn-project-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 3 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 24 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00069 | $0.00791 |
| Opus 5 | $0.00034 | $0.00396 |
| Sonnet 5 | $0.00014 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
shadcn-project-workflow 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 70 lines · 69 tokens per session scan A 234e4ea9ce11
shadcn-project-workflow is a skill published in the GitHub repository muratgur/ordinus (111 stars, last pushed 6d ago), licensed MIT. It adds 69 tokens to every session and 791 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
ui-html-renderer
Use this specialist for unusually complex stateful HTML, blank/runtime-risk repair, strict source-to-HTML fidelity, reusable component galleries, brand boards, or detailed implementation handoff. Ordinary single-page HTML uses ui-design-executor, which already preserves HTML-default delivery and baseline…
product-ui
Use this skill when UI design and UI implementation should happen together. It turns product context into usable frontend screens, components, layout decisions, design-system choices, accessibility rules, and visual polish.
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.