verification-first
Installation
SKILL.md
Verification-First Development
The Core Rule
A task is NOT complete until verification passes. "Almost working" = broken.
No self-attestation. No assumed success. Evidence required.
The 5 Rules
Rule 1 — Prove It Works
Every code change MUST be verified before moving on:
- Run the actual build command
- Run actual tests (not mocked)
- Check actual output
- Confirm expected behaviour
Related skills
More from cleanexpo/unite-hub
tdd
Use when implementing any feature or bug fix. Hard gate — no production code without a failing test first. Applies to vitest (apps/web/) and pytest (apps/backend/). Triggers on "implement", "add feature", "fix bug", "new component", "new endpoint", or any code-writing task.
1idea-to-production
Plain-English pipeline from idea to production — routes user requests to the right phase and agent
1oauth-flow
OAuth 2.0 and OIDC integration with PKCE, Supabase Auth providers, and redirect URI validation
1health-check
>-
1csv-processor
>-
1vector-search
>-
1