Ted Mosby - Architecture Wiki Generator
Generate comprehensive architectural documentation for any codebase with source code traceability (file:line references).
Overview
Ted Mosby creates architectural wikis that help developers understand codebases. Every concept links directly to source code, so you can navigate from documentation to implementation.
Output includes:
- Architecture overview with Mermaid diagrams
- Module documentation with source traceability
- Data flow documentation
- Getting started guides
- Interactive static site with search, keyboard nav, dark mode
When to Use This Skill
Use this skill when the user wants to:
- Document a codebase or project architecture
- Generate a wiki or documentation site
- Create architecture diagrams with source references
- Understand and document how a project is structured
- Produce navigable documentation with file:line traceability
Trigger phrases:
- "Generate docs for this project"
- "Create architecture documentation"
- "Document this codebase"
- "Make a wiki for this repo"
- "Help me understand this project's structure"
Prerequisites
Required
- Node.js >= 18.0.0
- Anthropic API key ( environment variable)
Check Prerequisites
bash
# Verify Node.js version
node --version # Should be >= 18.0.0
# Verify API key is set
echo $ANTHROPIC_API_KEY # Should show your key
Install Ted Mosby
Quick Start Commands
Basic Wiki Generation
bash
# Generate wiki for current directory
ted-mosby generate -r .
# Generate wiki for a specific project
ted-mosby generate -r ./my-project
# Generate wiki for a GitHub repository
ted-mosby generate -r https://github.com/user/repo
With Interactive Site
bash
# Generate wiki + interactive static site
ted-mosby generate -r ./my-project --site
# Custom title and theme
ted-mosby generate -r ./my-project --site --site-title "My Project Docs" --theme dark
# Generate site only (if wiki already exists)
ted-mosby generate -r ./my-project --site-only
Other Useful Options
bash
# Focus on specific subdirectory
ted-mosby generate -r ./my-project -p src/core
# Custom output directory
ted-mosby generate -r ./my-project -o ./docs/architecture
# Verbose output (see agent progress)
ted-mosby generate -r ./my-project -v
# Estimate time/cost before running (dry run)
ted-mosby generate -r ./my-project -e
Workflow
Step 1: Gather Requirements
Before running Ted Mosby, clarify with the user:
- Target path - What directory or repo to document?
- Output location - Where should the wiki go? (default: )
- Site generation - Do they want an interactive static site?
- Focus area - Any specific subdirectory to focus on?
- Theme preference - Light, dark, or auto?
Step 2: Pre-flight Checks
Verify the environment is ready:
bash
# Check Node.js version
node --version
# Verify ted-mosby is installed
which ted-mosby || echo "Run: npm install -g ted-mosby"
# Check API key
[ -z "$ANTHROPIC_API_KEY" ] && echo "Set ANTHROPIC_API_KEY environment variable"
Step 3: Run Generation
Choose the appropriate command based on user needs:
| User Wants | Command |
|---|
| Basic wiki only | ted-mosby generate -r ./project
|
| Wiki + interactive site | ted-mosby generate -r ./project --site
|
| Site with custom title | ted-mosby generate -r ./project --site --site-title "Docs"
|
| Dark theme site | ted-mosby generate -r ./project --site --theme dark
|
| Focus on subdirectory | ted-mosby generate -r ./project -p src/core
|
| Large codebase | ted-mosby generate -r ./project --max-chunks 5000
|
| Quick iteration | ted-mosby generate -r ./project --skip-index
|
Step 4: Review Output
After generation completes:
- Wiki location: (or custom output dir)
- Site location: (if used)
- Open site: Open in browser
Step 5: Fix Issues (if needed)
If there are broken links or missing pages:
bash
# Check for and generate missing pages
ted-mosby continue -r ./my-project -o ./wiki
# Verify only (don't generate)
ted-mosby continue -r ./my-project -o ./wiki --verify-only
Output Structure
wiki/
├── README.md # Navigation entry point
├── architecture/
│ ├── overview.md # System architecture + Mermaid diagrams
│ └── data-flow.md # Data flow documentation
├── components/
│ └── {module}/
│ └── index.md # Per-module documentation
├── guides/
│ └── getting-started.md # Quick start guide
├── glossary.md # Concept index
└── site/ # (with --site flag)
├── index.html # Interactive site entry
├── styles.css
└── scripts.js
Source Traceability
Every architectural concept includes clickable source references:
markdown
## Authentication Flow
The authentication system uses JWT tokens for stateless auth.
**Source:** [`src/auth/jwt-provider.ts:23-67`](../../../src/auth/jwt-provider.ts#L23-L67)
This allows developers to navigate directly from documentation to implementation.
Interactive Site Features
When
is used, the generated site includes:
| Feature | Description |
|---|
| Full-text search | Instant search across all pages (Cmd/Ctrl+K) |
| Keyboard navigation | Arrow keys, vim-style (j/k/h/l) |
| Dark/light mode | Respects system preference or manual toggle |
| Table of contents | Auto-generated from headings |
| Mobile responsive | Works on all devices |
| Offline capable | No server required |
| Mermaid diagrams | Rendered automatically |
Command Reference
- Create wiki documentation
| Option | Description | Default |
|---|
| Repository path or GitHub URL (required) | - |
| Output directory for wiki | |
| Focus on specific directory | - |
| Generate interactive static site | - |
| Generate site only (skip wiki) | - |
| Custom site title | Project name |
| Site theme: light, dark, auto | |
| Show detailed progress | - |
| Estimate time/cost (dry run) | - |
| Limit indexed chunks (for large repos) | unlimited |
| Use cached embeddings index | - |
| Use Anthropic API directly | - |
| Claude model to use | |
| Limit agent iterations | 200 |
- Resume/fix wiki generation
| Option | Description | Default |
|---|
| Repository path (required) | - |
| Wiki output directory | |
| Only check, don't generate | - |
| Use cached embeddings index | - |
| Show detailed progress | - |
Large Codebase Options
For repositories with 10,000+ files:
bash
# Limit indexed chunks (reduces memory usage)
ted-mosby generate -r ./large-project --max-chunks 5000
# Reduce search results per query
ted-mosby generate -r ./large-project --max-results 5
# Batched processing (for very large repos)
ted-mosby generate -r ./large-project --batch-size 3000
Typical Runtime
| Codebase Size | Approximate Time |
|---|
| Small (<50 files) | 1-2 minutes |
| Medium (50-200 files) | 2-5 minutes |
| Large (200+ files) | 5-10 minutes |
Use
to get a cost/time estimate before running.
Troubleshooting
"Credit balance is too low" error
Use direct API mode:
bash
ted-mosby generate -r ./my-project --direct-api
Out of memory on large repos
Limit indexed chunks:
bash
ted-mosby generate -r ./large-project --max-chunks 5000 --batch-size 3000
Slow re-runs during development
Skip re-indexing:
bash
ted-mosby generate -r ./my-project --skip-index
Missing pages / broken links
Use the continue command:
bash
ted-mosby continue -r ./my-project -o ./wiki
Example Conversation
User: "Can you document this project's architecture?"
Assistant: I'll use Ted Mosby to generate architectural documentation for your project.
First, let me verify the prerequisites are in place, then generate the wiki with an interactive site:
bash
# Generate wiki with interactive site
ted-mosby generate -r . --site --site-title "Project Architecture"
This will create:
- - Main navigation
wiki/architecture/overview.md
- Architecture diagrams
- - Interactive documentation site
Resources