AC senior-frontend
The ultimate frontend design and development skill. Creates production-ready, pixel-perfect web interfaces with Next.js + Tailwind + shadcn/ui. Combines design thinking, UX best practices, accessibility, animation, and real design system patterns inspired by the best sites on the web. Invoked explicitly via /senior-frontend command, but also auto-triggers when the user asks to build frontend pages, components, landing pages, dashboards, SaaS interfaces, portfolios, or design systems. Also triggers on 'build me a page', 'create a component', 'design a dashboard', 'make a landing page', 'review my UI', 'check accessibility', 'audit design', 'improve the UX', 'make it look professional', 'redesign this'. Supersedes frontend-design and web-design-guidelines.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (senior-frontend) differs from the folder (eb-senior-frontend)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 107 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 3956 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 764: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 107 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.