iada

What problem does it solve? Design decisions often embed cheap-to-change details (storage keys, table shapes, version segments) into expensive-to-change surfaces (identifiers, public APIs), making systems brittle. This Skill applies the IADA doctrine to rank each element of a design by how many external parties must act when it changes, and flags inversions where a lower layer has leaked into a higher one. ## Core Features & Use Cases - Layer classification: Assigns each element under discussion to Identifiers, API, Data, or Architecture based on who must change if it changes. - Inversion detection: Quotes offending elements where lower-layer facts (regions, table shapes, version segments) appear inside identifiers or contracts. - Change-cost verdicts: States the concrete cost of a proposed change by layer and gives one recommendation, not a menu. - Use Case: When reviewing a new REST resource path like /v2/us-east/orders/{uuid}, invoke the skill to identify that the region and version embedded in the identifier are inversions that will become permanent contracts. ## Quick Start Ask the AI to apply the iada doctrine to review whether the identifiers and API shape in your design document are safe to change later.