evals-first
Evals-First Development
Write the evals before the spec. Write the spec before the code.
The insight: when you give a coding agent strong, clear guardrails first, it writes specs and requirements that are easier to follow and leave less room for interpretation. The agent uses language optimized for its own comprehension — and that makes all the difference. Almost all code works immediately, design is close to perfect, text is almost there.
Why Evals First
Traditional: plan -> implement -> review -> fix
Better: spec -> plan -> implement -> review -> fix -> eval
Best: evals -> spec -> plan -> implement
More from jonmumm/skills
dont-use-use-effect
>
59react-composable-components
>
41grill-me
>
32mutation-testing
Run and interpret Stryker mutation testing; kill survivors to reach ≥95% score. Use when running mutation tests, setting up Stryker, interpreting survivors, or verifying test quality after TDD.
32offensive-typesafety
>
31expo-testing
Build, install, and test Expo/React Native apps on simulators and physical devices. Use when asked to "run on simulator", "install on device", "test on phone", "run detox", "preview build", or "build and test".
30