docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "This criteria evaluates how well the engineer uses postcss-modules-extract-imports to handle CSS Module composition with proper import deduplication. The focus is on correct usage of the plugin's deduplication features when processing composes declarations.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Plugin initialization",
"description": "Uses postcss-modules-extract-imports plugin correctly by requiring it and integrating it with PostCSS (e.g., using postcss() with the plugin in the plugins array)",
"max_score": 20
},
{
"name": "CSS processing execution",
"description": "Correctly invokes PostCSS to process CSS input, calling the process() method on the PostCSS instance and handling the result appropriately",
"max_score": 20
},
{
"name": "Import deduplication verification",
"description": "The implementation demonstrates that postcss-modules-extract-imports automatically deduplicates imports from the same file by reusing generated identifiers (e.g., when button is composed multiple times from the same file, only one :import() entry is created)",
"max_score": 30
},
{
"name": "Multiple class handling",
"description": "Correctly processes multiple class names in composes declarations where some are duplicated and some are unique, showing that the plugin creates separate identifiers for different classes while reusing identifiers for duplicates",
"max_score": 20
},
{
"name": "Different source separation",
"description": "Demonstrates that the plugin maintains separate :import() rules and identifiers when the same class name is composed from different source files",
"max_score": 10
}
]
}