What problem does it solve? Backend features often get marked as complete without any proof they actually work. This Skill enforces a verification step for the Peajes / Transporte Ibarra project: every backend change must be tested against a local Supabase CLI instance with pgTAP, and the evidence must be recorded before a feature can be marked as passing. ## Core Features & Use Cases - Local-first testing: Runs schema rebuilds (supabase db reset --local --no-seed) and pgTAP suites (supabase test db) against the local Supabase CLI, never against remote environments as a source of truth. - Environment guardrails: Clearly separates the local CLI (testing) from the DESARROLLO remote project (optional app smoke checks only), and forbids reusing OrdenCompra project refs. - Structured evidence recording: Defines exact formats for logging verification results in feature_list.json and docs/claude-progress.md, including command, exit code, environment, and date. - Use Case: After implementing a new Postgres RPC and writing its documentation, run this Skill to rebuild the local schema, execute the pgTAP test file, and record a supabase_db_test evidence entry proving the feature passes. ## Quick Start Verify the latest backend change by resetting the local Supabase database, running the pgTAP test suite, and recording the results as evidence in feature_list.json.
