Agent skill · yeachan-heo
drydock
Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.
What it needs
About 9k tokens when loaded.
What this skill does
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 this harness (use --check instead) Workflow 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yeachan-heo/drydock