Airgap Repo Design Doc Writer
- Updated June 11, 2026
- junnystateofmind/airgap-repo-design-doc-writer
Airgap Repo Design Doc Writer is a Claude Code skill that generates full-repository architecture documentation offline so developers and agents can understand complex codebases without external references.
About
Airgap Repo Design Doc Writer is a Claude Code marketplace plugin that generates complete repository architecture documentation for teams working without internet access. It balances analysis across layers, maps external dependencies, draws ASCII topology diagrams, traces representative data flows, and grounds design decisions in git history with verified facts only. Use it when onboarding developers or agents to a complex codebase and you need a single trustworthy design document instead of scattered README fragments.
- Writes whole-repository architecture docs for air-gapped environments without internet
- Maps external server dependencies with protocol, port, purpose, and required flags
- Traces two to four end-to-end data flows and restores design rationale from git history
- Verifies ports, versions, and endpoints against code and config instead of guessing
Airgap Repo Design Doc Writer by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add junnystateofmind/airgap-repo-design-doc-writerAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | June 11, 2026 |
|---|---|
| Repository | junnystateofmind/airgap-repo-design-doc-writer ↗ |
How do we produce accurate whole-repo architecture and dependency documentation when engineers or agents cannot rely on internet access or missing design records?
Generate full-repo architecture docs offline, mapping services, external dependencies, and verified data flows for air-gapped teams.
Who is it for?
Teams in air-gapped or documentation-sparse environments who need verified architecture docs, dependency topology, and onboarding-ready design writeups.
Skip if: Small single-file repos, marketing content generation, or teams that already maintain complete up-to-date architecture documentation.
What you get
A design document such as docs/design/architecture.md appears with layer inventory, dependency tables, ASCII topology, data flows, and git-backed rationale.
Recommended Marketplaces
FAQ
What makes this skill suited for air-gapped environments?
It is designed to understand a codebase using local repository files and git history without requiring internet or external documentation.
What artifacts does it produce?
It writes a full architecture design document, typically at docs/design/architecture.md, including dependency topology and verified data flows.
How does it avoid hallucinated infrastructure details?
Ports, versions, and endpoints are cross-checked against code, configuration, and lockfiles; unverified items are explicitly marked.