BF tailwind-v4-+-shadcn/ui-stack
Production-tested setup for Tailwind v4 with shadcn/ui. Prevents 8 documented errors through a mandatory four-step architecture.
Production-tested setup for Tailwind v4 with shadcn/ui.
As a process F 33/100 · Will not run — References files that are not bundled: templates/index.css
ProcedureSoftware developmentMarketingDesigntype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: templates/index.css
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: templates/index.css
- 0Tools and files. 1 referenced file(s) missing: templates/index.css
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (tailwind-v4-+-shadcn/ui-stack) differs from the folder (tailwind-v4-shadcn)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 50 steps
- 100Execution cost. Instruction body is 2182 tokens
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 128: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (20 code blocks)
- +4Reference files are cited in the instructions (3 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.