Wiring Audit

Overview

Diff a project's consumed surface (UI buttons, components, hooks, fetch calls, tRPC client invocations, GraphQL queries, server actions) against its produced capability (route handlers, hook exports, tRPC routers, GraphQL resolvers, exported async functions) and report every mismatch as a prioritized finding with citations on both sides.

The audit's load-bearing claim: every UI consumption should match exactly one backend production, and every production should be consumed somewhere. Orphans, drift, and gaps are the failure modes. The report is the punch list.

When to use

Trigger this skill when the user asks for:

• A wiring/drift audit ("audit our wiring," "find drift")
• Identification of unused or orphan code on the wire (unused endpoints, unused hooks)
• Verification that backend capabilities are surfaced ("what's not exposed in the UI?")
• Verification that UI surfaces are wired ("is anything in the UI broken or stale?")
• Contract violation detection between FE and BE
• Stale label detection (UI copy that lies about what the backend does)