drydock

# Drydock Lay the keel of the **shipyard**: one repo, one shared harness, every contributor inherits it. This skill scaffolds the environment that turns "everyone ships" into "everyone ships on the same design language" — it creates the 5 surfaces, seeds them minimally, wires them to the flows that fill them (launch writes CONTEXT/ADR; the launch C5 sediment pass and reviews sediment standards), and reports what exists, what was created, and what stays empty on purpose. The four pillars and where they physically live: | Pillar | Surfaces | |---|---| | Context (shared background) | `CONTEXT.md` (glossary) + `docs/business/` + `docs/adr/` + OMC wiki | | Rules (boundaries) | `CLAUDE.md` (thin entry: conventions, principles, index) + `docs/standards/` | | Tools (composable capability) | `.omc/skills/` + `.mcp.json` + `scripts/` | | Standards (the classification society) | `design-system/` (tokens, components, patterns) + `docs/standards/` | Metaphor map: the shipyard is the shared facility; the classification society (`docs/standards/` + `design-system/`) sets the rules a ship must pass to be seaworthy; drydock lays the keel; launch ships it. ## When to Use - starting a repo that humans and agents will both build on - a repo where knowledge lives in people's heads and chat history instead of files - onboarding: a new teammate or agent should inherit context by reading, not by asking ## When Not to Use - throwaway prototypes with no collaborators - a repo already running t...