CF design-philosophy
The VS Code design philosophy — a shared Values→Principles→Moves vocabulary for reasoning about UI in design terms instead of raw pixels. Use when designing, building, reviewing, or giving feedback on any visual surface; when deciding a radius, spacing, type role, icon size, border, color, or motion; or when translating a "this feels off" observation into a concrete, principled fix.
The skill promises a shared vocabulary for UI design — Values→Principles→Moves framework to discuss interfaces in principled terms instead of pixel-level tweaks. Use when picking radius, spacing, icon size, or explaining why something feels off.
One file, 6110 tokens. Quality score 53 out of 100 — half the maximum. Process score 31: broken links and missing files present. No critical errors found, but the structure is clearly incomplete. Never tested on models.
Works as a reference if you're willing to fix broken links yourself and fill in gaps. Install as supplementary material, not as a complete guide.
The VS Code design philosophy — a shared Values→Principles→Moves vocabulary for reasoning about UI in design terms instead of raw pixels.
As a process F 31/100 · No process to follow — References files that are not bundled: ../../../src/vs/platform/theme/common/sizes/baseSizes.ts, ../../instructions/design-tokens.instructions.md, ../../instructions/coding-guidelines.instructions.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 · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6110 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../../../src/vs/platform/theme/common/sizes/baseSizes.ts - warning
missing-refreference to a missing file: ../../instructions/design-tokens.instructions.md - warning
missing-refreference to a missing file: ../../instructions/coding-guidelines.instructions.md
Process rating: all ten parameters 31/100
- 0Tools and files. 3 referenced file(s) missing: ../../../src/vs/platform/theme/common/sizes/baseSizes.ts, ../../instructions/design-tokens.instructions.md, ../../instructions/coding-guidelines.instructions.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 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
- 70Execution cost. Instruction body is 6110 tokens
- 100Steps. 41 steps
- 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
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
- +4No input/output examples
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 385: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 41 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.