docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "This evaluation assesses how well the engineer uses postcss-modules-extract-imports to handle nested CSS rules with composes declarations. The focus is on correctly using the package's nested rule handling capabilities, specifically tracking parent-child relationships and maintaining separate import contexts for different nesting levels.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Plugin initialization",
"description": "Uses postcss-modules-extract-imports correctly by requiring it and calling it as a PostCSS plugin (e.g., postcss([extractImports()]) or similar PostCSS plugin initialization pattern)",
"max_score": 20
},
{
"name": "Composes processing",
"description": "Relies on the plugin to automatically process composes declarations and transform them into :import() rules, without manually parsing or transforming composes syntax",
"max_score": 25
},
{
"name": "Nested rule support",
"description": "Allows the plugin to handle nested rules naturally through its parent-child tracking mechanism, without implementing custom nested rule traversal logic",
"max_score": 30
},
{
"name": "Import generation",
"description": "Leverages the plugin's automatic generation of unique imported names and :import() rule creation rather than manually creating these structures",
"max_score": 25
}
]
}