Rule reference · Specificity
Unquantified size
Fires when: "short", "a few", "detailed" with no number.
Size words are relative. "A few" is two on one run and six on the next, which breaks layouts, tests, and downstream parsing.
Use a number and a unit: "5 ideas", "under 150 words", "3 paragraphs". Ranges are fine when you mean one ("3 to 5 bullets").
Example that triggers it
Give me a few ideas for blog posts about remote work, as a bulleted list.
info Size words without a number: "a few".
Why it matters. "Short" or "a few" mean different things to different readers, so output length drifts between runs.
Fix. State a number, e.g. "under 150 words" or "3 examples".
Quality 94/100 · 18 tokens · 2 findings
Fixed version
Give me 5 ideas for blog posts about remote work, as a bulleted list.
Quality 97/100 (+3) · 18 tokens · 1 findings
Resolved by the fix
unquantified_size: Size words without a number: "a few".
Scores, token counts (GPT-4.1 tokenizer), and findings on this page are computed by the engine when the site is built.
How it affects the score
Each finding subtracts a fixed penalty from 100: critical 30, warning 10, info 3. This rule counts against the Specificity dimension. See the scoring model for the full formula.
Other specificity rules
- Prompt too short: Fewer than 5 content words.
- Missing programming language: Code requested without a language or framework.