Node.js-specific utilities and runtime functionality for Tailwind CSS v4, providing compilation tools, module dependency analysis, source map handling, path normalization, and optimization utilities.
43
Pending
Does it follow best practices?
Impact
43%
1.16xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "Evaluates how the solution leverages @tailwindcss/node's DEBUG environment parsing to decide whether Tailwind instrumentation should run. Checks that every interpretation of the DEBUG flag is delegated to the package rather than reimplemented.",
"type": "weighted_checklist",
"checklist": [
{
"name": "env import",
"description": "Imports `env` from `@tailwindcss/node` and bases debug decisions on `env.DEBUG` instead of custom parsing or duplicated state.",
"max_score": 40
},
{
"name": "Pattern handling",
"description": "Uses the package's DEBUG parsing to honor `*`, `tailwindcss`, and `-tailwindcss` patterns exactly as `env.DEBUG` defines (e.g., wildcard enables, exclusion overrides wildcard).",
"max_score": 25
},
{
"name": "Override parsing",
"description": "When evaluating an override flag, routes it through the package's DEBUG interpreter (e.g., by temporarily setting `process.env.DEBUG` then reading `env.DEBUG` or invoking the package helper) rather than hand-parsing.",
"max_score": 20
},
{
"name": "Truthiness",
"description": "Relies on the package's DEBUG handling for `true`/`1` vs `false`/`0`, avoiding manual coercion rules that differ from `env.DEBUG`.",
"max_score": 15
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10