Can this skill help with external tool conflicts?

Yes, it includes specific strategies for the External System Layer, focusing on isolation, idempotency, and managing side effects of external commands.

Why does this skill recommend fixing top-down?

Higher-layer bugs often make lower-layer bugs untestable. Fixing the architecture first clarifies constraints for implementation fixes and prevents redundant work.

When should I use this debugging skill?

Use it when a fix doesn't resolve the visible issue, symptoms span multiple layers (like CLI to database), or when fixing one bug reveals another.

How does this help with integration testing?

It provides a structured approach to validate individual layer contracts before running full end-to-end tests, making it easier to pinpoint exactly where an integration fails.

Layered System Debugger

Name: Layered System Debugger
Author: delorenj

bydelorenj

•

보안 및 테스팅

Provides a structured reasoning pattern for diagnosing and resolving complex bugs that span multiple abstraction layers in software systems.

The Layered System Debugger skill equips Claude with a methodical framework for tackling 'Russian Doll' bugs where fixing one issue reveals another. By systematically mapping system layers—from CLI handlers to external tool integrations—this skill helps identify whether symptoms are architectural or implementation-based. It enforces a top-down fix strategy to prevent wasted effort on compounded issues, ensuring each layer's contract is validated through isolation testing before proceeding to full integration verification. This is especially useful for complex systems where UI, services, data, and external dependencies interact in non-obvious ways.

주요 기능

01Top-down fix prioritization to prevent redundant debugging

025 GitHub stars

03Systematic mapping of abstraction layers from UI to external tools

04Diagnostic decision tree for handling changing error messages

05Categorization of symptoms into architectural or implementation issues

06Isolation testing patterns for individual layer contracts

사용 사례

01Mapping complex system architectures to identify root causes of architectural regressions

02Diagnosing bugs that persist or change error messages after an initial fix is applied

03Debugging integration issues between local code and external CLI tools or APIs

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add delorenj/skills debugging-complex-multi-layer-systems

For use in Claude.ai and ChatGPT

Download Skill