verification-patternslisted
Install: claude install-skill emrecdr/devt
# Verification Patterns
## Overview
The most common failure in AI-generated code is "looks done but isn't" — files exist but contain stubs, functions are defined but never called, features are coded but not wired into the system.
## The Iron Law
```
LEVEL 3 MINIMUM FOR ALL ARTIFACTS BEFORE CLAIMING DONE
```
The most common failure mode in AI-assisted development is code that exists but is not connected to anything — a function defined but never imported, a route registered but missing its handler, a service created but not wired into dependency injection. Level 3 (wired) catches these disconnected artifacts that pass superficial review but fail at runtime. Without this minimum bar, "done" means "files exist" rather than "feature works."
Code that exists (L1) but is not wired into the system (L3) is not done. "File is there" is not evidence of completion. Trace imports, check registration, verify reachability.
## The 4 Levels
### Level 1: Exists
- File is present at expected path
- Has non-zero size
- Is not a copy of a template with no modifications
### Level 2: Substantive
Content is real implementation, not placeholder. Scan for:
- `# TODO`, `# FIXME`, `# HACK`
- Empty function bodies: `pass`, `return null/undefined`, `return nil`, `{}`
- Explicit not-implemented markers: `raise NotImplementedError`, `throw new Error("not implemented")`, `panic("not implemented")`
- `return {}`, `return []`, `return ""` where real data expected
- `"placeholder"`, `"example"`, `"