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 chalk's chainable styling is used to build reusable stylers and apply level-specific prefixes per the spec, including defaults, overrides, and opt-out behavior. Focuses solely on leveraging chalk APIs rather than manual ANSI handling.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Token chaining",
"description": "`makeStyler` builds a chalk chain (e.g., `chalk.bgBlue.white.bold`) from the provided token order and returns a reusable function instead of applying tokens ad hoc; token order is preserved.",
"max_score": 30
},
{
"name": "Default prefixes",
"description": "`formatLog` uses chalk to apply the default token sets (`info` cyan+bold, `warn` yellow+bold, `error` whiteBright+bgRed, `debug` gray) to the `[LEVEL]` prefix only.",
"max_score": 25
},
{
"name": "Custom overrides",
"description": "When `customStyles` are provided, the warn (or other) styler is rebuilt from the supplied tokens using the same chalk chaining rather than string concatenation.",
"max_score": 20
},
{
"name": "Color opt-out",
"description": "Setting `disableColor` results in a chalk instance or level change (e.g., `new Chalk({ level: 0 })` or using `chalk.visible`) that emits plain text with no ANSI codes.",
"max_score": 15
},
{
"name": "No ANSI literals",
"description": "Implementation relies on chalk's builders for styling and avoids manually writing ANSI escape sequences.",
"max_score": 10
}
]
}