Audit repositories for dead code, unreachable control flow, unused imports, and unused package dependencies, then triage cleanup candidates and produce a structured report. Use when asked to scan an entire codebase for dead code, technical-debt cleanup, unused exports, unreachable branches, phantom dependencies, or safe-to-delete files.
Maintain technical design docs for services, components, workers, modules, and APIs. Use when implementation design, contracts, schema, integrations, runtime behavior, or operational concerns change.
Maintain feature docs that explain user-visible behavior, goals, flows, and business rules without implementation detail. Use when feature scope, user workflows, or product behavior changes.
Maintain system and domain architecture docs such as `docs/ARCHITECTURE.md`, `web-architecture.md`, or `api-architecture.md`. Use when topology, shared patterns, cross-component flows, deployment model, or ownership boundaries change.