Skill UI

Provide step-by-step explanations of specific files, functions, or modules, leveraging the understand-explain workflow to map graph context, layer placement, internal structure, and data flow for developers needing deep clarity.

Used for systematic deep-dive repair of broken features or modules. It involves five strict phases: Scope, Trace, Diagnose, Fix, and Verify. Unlike quick bug fixes, this method maps all dependencies, checks logs, and ensures the entire feature works end-to-end before proposing solutions.

This skill analyzes an existing codebase using domain context and architectural decisions to identify architectural friction and "deepening opportunities." It proposes refactored improvements to increase module depth, enhancing testability, improving maintainer locality, and making the codebase more navigable for AI tools. It focuses on transforming shallow modules into robust, deeply leveraged components.

A comprehensive guide and shared vocabulary for designing and structuring complex software modules. Use this when you need to refine an existing module's interface, identify opportunities for deepening its capabilities, determine optimal internal seams, or improve code testability and AI-navigability. It establishes clear principles for Module, Interface, Depth, and Seam.

This critical protocol is the ultimate measure for dealing with deeply corrupted, unmaintainable, or structurally rotten code modules. Instead of risky patching, it mandates a controlled, multi-phase process to completely delete the target and rebuild it from scratch. It ensures precise identification of all public interfaces, implicit contracts, and working behaviors (the Preservation List) before any removal occurs, guaranteeing the new implementation matches the original functionality while resolving deep architectural debt.

This skill provides comprehensive pull request (PR) code reviews that go beyond simple syntax checks. It aggressively surfaces deep-rooted decay risks, architectural design smells, and maintainability issues. Findings are reported using a structured Symptom → Source → Consequence → Remedy framework, drawing insights from classic engineering principles. Ideal for reviewing complex or crucial code modules.

A comprehensive guide and shared vocabulary for designing and structuring complex software modules. Use this when you need to refine an existing module's interface, identify opportunities for deepening its capabilities, determine optimal internal seams, or improve code testability and AI-navigability. It establishes clear principles for Module, Interface, Depth, and Seam.

This critical protocol is the ultimate measure for dealing with deeply corrupted, unmaintainable, or structurally rotten code modules. Instead of risky patching, it mandates a controlled, multi-phase process to completely delete the target and rebuild it from scratch. It ensures precise identification of all public interfaces, implicit contracts, and working behaviors (the Preservation List) before any removal occurs, guaranteeing the new implementation matches the original functionality while resolving deep architectural debt.

Shared vocabulary and principles for designing deep modules with small interfaces, clean seams, and testable, AI-navigable codebases.