network-debugging
>
Works with
--- name: network-debugging description: > license: MIT --- # Network Debugging ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Network debugging identifies connectivity issues, latency problems, and data transmission errors that impact application performance. ## When to Use - Slow loading times - Failed requests - Intermittent connectivity - CORS errors - SSL/TLS issues - API communication problems ## Quick Start Minimal working example: ```yaml Chrome DevTools Network Tab: Columns: - Name: Request file/endpoint - Status: HTTP status code - Type: Resource type (xhr, fetch, etc) - Initiator: What triggered request - Size: Resource size / transferred size - Time: Total time to complete - Waterfall: Timeline visualization Timeline Breakdown: - Queueing: Waiting in queue - DNS: Domain name resolution - Initial connection: TCP handshake - SSL: SSL/TLS negotiation - Request sent: Time to send request - Waiting (TTFB): Time to first byte - Content Download: Receiving response --- Network Conditions: Throttling Presets: - Fast 3G: 1.6 Mbps down, 750 Kbps up // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Browser Network Tools](references/browser-network-tools.md) | Browser Network Tools | | [Common Network Issues](references/common-network-issues.md) | Common Network Issues | | [Debugging Tools & Techniques](references/debugging-tools-techniques.md) | Debugging Tools & Techniques | | [Checklist](references/checklist.md) | Checklist | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
