conventionlisted

# Iceberg Convention ## What this skill does The Iceberg Convention is a coding convention *for senior and staff engineers* whose goal is to make the code juniors (and AI agents) actually touch maximally frictionless. It does this by quarantining complexity behind an **architectural airgap**: seniors absorb the sophistication (types, state machines, custom linters, architecture tests, observability) below the waterline, and the surface above it reads as linear, synchronous-looking, imperative business logic. This skill helps you **apply the convention while writing or reviewing code**. It is organized around three modes: - **Authoring** — you are about to write or modify code. Apply the rules during generation. - **Audit** — you are reviewing an existing codebase against the convention. Produce a structured report. - **Bootstrap** — you are setting up the convention's enforcement scaffolding in a fresh project. ## This is a language-agnostic convention The rules describe **patterns** (airgap separation, branded types, discriminated unions, exhaustive matching, pure cores, runtime tracing, written rationale). The patterns have implementations in every mainstream typed language; their syntax differs and their *native* support varies, but the intent is invariant. When applying the convention: 1. **Detect the target language** from the repo — `package.json`, `pom.xml`, `Cargo.toml`, `pyproject.toml`, `*.csproj`, `go.mod`, `mix.exs`, `Gemfile`, `composer.json`, etc. If mul