BF frontend-design
Create distinctive, accessible frontend interfaces with deliberate palette, typography, and layout choices. Use when building UI components, pages, dashboards, or landing pages. Includes 73+ brand DESIGN.md references, HTML slide generation, design system token architecture, and shadcn/ui/Tailwind styling guides.
Create distinctive, accessible frontend interfaces with deliberate palette, typography, and layout choices.
As a process F 32/100 · Will not run — References files that are not bundled: references/design-systems.md, references/design-md-collection/<brand>/DESIGN.md, references/design-md-collection/linear.app/DESIGN.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/design-md-collection/hashicorp/DESIGN.md:331High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **hashicorpSans** — HashiCorp's proprietary marketing typeface. Geometric, clean, slightly humanist. Fallback stack `__ha…0ca` (system font), then `-apple-system, BlinkMacSyst
quoted
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9194 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/design-systems.md - warning
missing-refreference to a missing file: references/design-md-collection/<brand>/DESIGN.md - warning
missing-refreference to a missing file: references/design-md-collection/linear.app/DESIGN.md - warning
missing-refreference to a missing file: references/design-md-collection/midea-wcs/DESIGN.md - warning
missing-refreference to a missing file: references/ux-priorities.md - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 32/100
- 0Tools and files. 5 referenced file(s) missing: references/design-systems.md, references/design-md-collection/<brand>/DESIGN.md, references/design-md-collection/linear.app/DESIGN.md
- 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. 5 mutating operations with no state check
- 40Execution cost. Instruction body is 9194 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 108 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 314: enough signal without eating the budget
- +4Structure: 59 headings
- +3Step-by-step instructions: 108 items
- +4Has examples (19 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.