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 well the solution uses @tailwindcss/node to run Lightning CSS optimization, normalize media queries, and preserve accurate source maps for modern CSS input. Also checks whether the implementation surfaces the package-produced warnings with useful context instead of inventing its own handling.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Optimize call",
"description": "Uses the package's `optimize` function (with the dependency imported from `@tailwindcss/node`) as the primary transformer, enabling its Lightning CSS features (nesting/custom media) and minify toggle instead of reimplementing or manually rewriting CSS.",
"max_score": 30
},
{
"name": "Range fix",
"description": "Relies on `optimize` output to normalize media query range syntax (e.g., `@media not (width < 768px)` becoming `@media not all and (width < 768px)`) rather than custom string replacements.",
"max_score": 20
},
{
"name": "Source map chain",
"description": "Passes `file` and incoming `map` options into `optimize`, consumes the returned map, and when emitting inline or serialized maps uses the package's `toSourceMap` helper (not hand-crafted JSON) so `sources`/`sourcesContent` stay aligned with the original CSS.",
"max_score": 30
},
{
"name": "Warnings surfaced",
"description": "Reads `warnings` from the `TransformResult` produced by `optimize`, filters only noise, and surfaces message/line/column/snippet details from those warnings instead of inventing or ignoring them.",
"max_score": 20
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10