What problem does it solve?
This Skill helps identify design decisions that leak across module boundaries, creating hidden dependencies, fragile changes, and interfaces that expose implementation details.
Core Features & Use Cases
- Knowledge Ownership Review: Map formats, algorithms, protocols, and data structures to the modules that should exclusively own them.
- Leakage Detection: Find interface leakage, back-door dependencies, temporal decomposition, getter/setter overexposure, and over-specialized general-purpose modules.
- Use Case: Review a file-processing system to determine whether its reader and parser share hidden format assumptions, then recommend a boundary that centralizes ownership of the file format.
- Reference-Guided Analysis: Apply structural heuristics such as parallel switches, implicit protocols, ordering assumptions, duplicated constants, and format coupling.
Quick Start
Use the information-hiding skill to review the specified module for leaked design decisions and recommend a boundary that centralizes knowledge ownership.