docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates how well the solution leverages Chalk's TypeScript declarations, including deprecated neutral aliases and stream-aware instances, to implement the status palette described in the spec.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Typed palette",
"description": "Uses Chalk's TypeScript types (e.g., ChalkInstance or the Chalk constructor type) for palette creation and avoids `any`, keeping `createStatusPalette` and its helpers strongly typed against Chalk's style API.",
"max_score": 20
},
{
"name": "Default styles",
"description": "Default branch applies `chalk.gray` for info, `chalk.green` for success, `chalk.yellow` for warning, and `chalk.red` for error so `[LABEL] message` is styled with the expected opens/closes and a final reset.",
"max_score": 25
},
{
"name": "Deprecated alias",
"description": "When `neutralTone` is \"deprecated\", switches the info styling to Chalk's deprecated neutral alias (e.g., `chalk.grey`) rather than the canonical name, demonstrating knowledge of the alias typings.",
"max_score": 20
},
{
"name": "Stream binding",
"description": "Palette honors the `stream` option by using `chalkStderr` or a Chalk instance built from `supportsColorStderr` for stderr, while the default uses the standard `chalk`/`supportsColor` detection so disabling stderr color only affects that palette.",
"max_score": 20
},
{
"name": "Reset coverage",
"description": "Ensures Chalk's reset handling is used (e.g., chained calls ending in `.reset` or explicit `chalk.reset`) so styled labels do not leak formatting beyond the returned string.",
"max_score": 15
}
]
}