Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation for a codebase.
Add this skill
npx mdskills install sickn33/wiki-onboardingComprehensive dual-audience onboarding generator with strong structure and citation requirements
1---2name: wiki-onboarding3description: Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation for a codebase.4---56# Wiki Onboarding Guide Generator78Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase.910## When to Activate1112- User asks for onboarding docs or getting-started guides13- User runs `/deep-wiki:onboard` command14- User wants to help new team members understand a codebase1516## Language Detection1718Scan the repository for build files to determine the primary language for code examples:19- `package.json` / `tsconfig.json` → TypeScript/JavaScript20- `*.csproj` / `*.sln` → C# / .NET21- `Cargo.toml` → Rust22- `pyproject.toml` / `setup.py` / `requirements.txt` → Python23- `go.mod` → Go24- `pom.xml` / `build.gradle` → Java2526## Guide 1: Principal-Level Onboarding2728**Audience**: Senior/staff+ engineers who need the "why" behind decisions.2930### Required Sections31321. **System Philosophy & Design Principles** — What invariants does the system maintain? What were the key design choices and why?332. **Architecture Overview** — Component map with Mermaid diagram. What owns what, communication patterns.343. **Key Abstractions & Interfaces** — The load-bearing abstractions everything depends on354. **Decision Log** — Major architectural decisions with context, alternatives considered, trade-offs365. **Dependency Rationale** — Why each major dependency was chosen, what it replaced376. **Data Flow & State** — How data moves through the system (traced from actual code, not guessed)387. **Failure Modes & Error Handling** — What breaks, how errors propagate, recovery patterns398. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths409. **Security Model** — Auth, authorization, trust boundaries, data sensitivity4110. **Testing Strategy** — What's tested, what isn't, testing philosophy4211. **Operational Concerns** — Deployment, monitoring, feature flags, configuration4312. **Known Technical Debt** — Honest assessment of shortcuts and their risks4445### Rules46- Every claim backed by `(file_path:line_number)` citation47- Minimum 3 Mermaid diagrams (architecture, data flow, dependency graph)48- All Mermaid diagrams use dark-mode colors (see wiki-vitepress skill)49- Focus on WHY decisions were made, not just WHAT exists5051## Guide 2: Zero-to-Hero Contributor Guide5253**Audience**: New contributors who need step-by-step practical guidance.5455### Required Sections56571. **What This Project Does** — 2-3 sentence elevator pitch582. **Prerequisites** — Tools, versions, accounts needed593. **Environment Setup** — Step-by-step with exact commands, expected output at each step604. **Project Structure** — Annotated directory tree (what lives where and why)615. **Your First Task** — End-to-end walkthrough of adding a simple feature626. **Development Workflow** — Branch strategy, commit conventions, PR process637. **Running Tests** — How to run tests, what to test, how to add a test648. **Debugging Guide** — Common issues and how to diagnose them659. **Key Concepts** — Domain-specific terminology explained with code examples6610. **Code Patterns** — "If you want to add X, follow this pattern" templates6711. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them6812. **Where to Get Help** — Communication channels, documentation, key contacts6913. **Glossary** — Terms used in the codebase that aren't obvious7014. **Quick Reference Card** — Cheat sheet of most-used commands and patterns7172### Rules73- All code examples in the detected primary language74- Every command must be copy-pasteable75- Include expected output for verification steps76- Use Mermaid for workflow diagrams (dark-mode colors)77- Ground all claims in actual code — cite `(file_path:line_number)`78
Full transparency — inspect the skill content before installing.