empirical-validation
Installation
SKILL.md
Empirical Validation
Core Principle
"The code looks correct" is NOT validation.
Every change must be verified with empirical evidence before being marked complete.
Validation Methods by Change Type
| Change Type | Required Validation | Tool |
|---|---|---|
| UI Changes | Screenshot showing expected visual state | browser_subagent |
| API Endpoints | Command showing correct response | run_command |
| Build/Config | Successful build or test output | run_command |
| Data Changes | Query showing expected data state | run_command |
| File Operations | File listing or content verification | run_command |
Validation Protocol
Related skills
More from toonight/get-shit-done-for-antigravity
gsd planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification
27gsd codebase mapper
Analyzes existing codebases to understand structure, patterns, and technical debt
23gsd executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management
22gsd verifier
Validates implemented work against spec requirements with empirical evidence
22gsd debugger
Systematic debugging with persistent state and fresh context advantages
22context health monitor
Monitors context complexity and triggers state dumps before quality degrades
22