What problem does it solve? Bringing up a local full-stack environment and finding where a bug actually lives is hard: failures can hide in the browser, frontend proxy, gateway, API, worker, database, cache, queue, or an external dependency. This Skill starts the repository's real local stack, verifies readiness at each layer, reproduces one concrete end-to-end flow, and produces an evidence-backed fault location instead of guesswork. ## Core Features & Use Cases - Topology reconstruction: Builds a runtime map of frontend, proxy/BFF, API, workers, and data services from repository evidence, then runs preflight checks on runtimes, ports, environment variables, and migrations. - Ordered startup with readiness gates: Starts components in dependency order and distinguishes process-started, ready, and integrated states rather than trusting an open port. - Cross-boundary fault localization: Exercises one real end-to-end flow with request/trace ID correlation, then traces the first diverging boundary across browser, proxy, gateway, backend, database, cache, queue, and external services. - Use Case: A user reports that submitting a form locally returns success but no data appears. The Skill starts the stack, replays the flow through the real frontend, correlates logs across layers, and pinpoints whether the fault is in the proxy, API validation, or a failed worker event. ## Quick Start Ask the agent to use $run-local-fullstack-debug to start the local stack, reproduce the failing flow, and trace the failure across layers.
