information-hiding

Detect information leakage and hidden dependencies across software module boundaries.

11|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/codybrom/clairvoyance --skill information-hiding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: information-hiding
Source: https://github.com/codybrom/clairvoyance/tree/main/skills/information-hiding
Command: npx skills add https://github.com/codybrom/clairvoyance --skill information-hiding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about information-hiding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find hidden dependencies across software module boundaries during a code review?

Detect information leakage by inventorying design decisions, mapping ownership of formats and protocols, and testing for back-door leakage where duplicated knowledge creates hidden dependencies across module boundaries.

What is temporal decomposition in software architecture and how does it cause interface leakage?

Temporal decomposition is a design fragmentation where processing steps leak ordering assumptions across module boundaries, creating implicit protocols and hidden dependencies that make interface changes fragile and difficult to modify.

How do I review shared formats and protocol assumptions to prevent back-door leakage?

Review shared formats by mapping data structures and protocols to exclusive module owners, identifying duplicated constants or format coupling, and proposing consolidation to centralize knowledge ownership and prevent back-door leakage.

Can I use this to detect over-specialized general-purpose modules and getter setter overexposure?

Yes, you can detect over-specialized general-purpose modules and excessive getter setter exposure by applying structural heuristics to identify parallel switches and interface leakage that expose internal implementation details.

What is the best way to centralize knowledge ownership for a file-processing system with reader and parser modules?

Centralize knowledge ownership by reviewing the reader and parser for shared hidden format assumptions, then recommending a module boundary that exclusively owns the file format to eliminate duplicated knowledge.