# Debugging Hub

Use this hub for work that begins with a defect, regression, failing test, production issue, or confusing system behavior.

If [DEPLOYMENT-PROFILE.md](../DEPLOYMENT-PROFILE.md) contains debugging defaults, apply those preferences before falling back to the generic routing in this hub.

## When To Use

- A test is failing and the cause is unclear
- A user-reported bug needs reproduction and triage
- The system behaves inconsistently across environments or inputs
- A suspected regression needs careful isolation

## Start With

- [Bug Triage](../skills/debugging/bug-triage.md) to define the problem, impact, environment, and reproduction path
- [Debugging Workflow](../skills/debugging/debugging-workflow.md) to isolate root cause and verify a fix

## Combine With

- [API and Backend Work](../skills/software/api-backend.md) when the issue is server-side or data-related
- [Frontend UI Implementation](../skills/software/frontend-ui-implementation.md) when the issue is client-side or interaction-related
- [Test Strategy](../skills/software/test-strategy.md) when the fix needs coverage
- [Release and Change Summary](../skills/software/release-change-summary.md) when the resolution should be communicated clearly
- [Incident Response and Stabilization](../skills/debugging/incident-response-stabilization.md) when the issue is live, user-impacting, or needs temporary containment before a full fix
- [Observability and Operability](../skills/software/observability-operability.md) when logs, metrics, traces, or alerting gaps block diagnosis
- [Performance Optimization](../skills/software/performance-optimization.md) when the problem is latency, throughput, memory, or rendering related