Compressed caveman-style prose for AI coding agents — cuts ~65% output tokens while keeping full technical accuracy
96
100%
Does it follow best practices?
Impact
96%
1.00xAverage score across 38 eval scenarios
Passed
No known issues
{
"context": "Tests whether the response implements a correct React error boundary with all required features.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses class component",
"description": "Error boundary is a class component (error boundaries cannot be function components in React)",
"max_score": 12
},
{
"name": "Implements getDerivedStateFromError or componentDidCatch",
"description": "Implements static getDerivedStateFromError to update state and/or componentDidCatch for side effects",
"max_score": 15
},
{
"name": "Renders fallback UI on error",
"description": "The render method checks error state and shows a fallback UI instead of children when an error has occurred",
"max_score": 12
},
{
"name": "Retry button resets state",
"description": "Fallback UI includes a retry/reset button that clears the error state so children re-render",
"max_score": 12
},
{
"name": "Logs error details",
"description": "Error information is logged (console.error, external service, or callback prop)",
"max_score": 10
},
{
"name": "No incorrect information",
"description": "Code is syntactically valid React and correctly uses the error boundary API",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37