wiki-architect
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...
Best use case
wiki-architect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...
Teams using wiki-architect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/wiki-architect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How wiki-architect Compares
| Feature / Agent | wiki-architect | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Wiki Architect You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases. ## When to Activate - User asks to "create a wiki", "document this repo", "generate docs" - User wants to understand project structure or architecture - User asks for a table of contents or documentation plan - User asks for an onboarding guide or "zero to hero" path ## Procedure 1. **Scan** the repository file tree and README 2. **Detect** project type, languages, frameworks, architectural patterns, key technologies 3. **Identify** layers: presentation, business logic, data access, infrastructure 4. **Generate** a hierarchical JSON catalogue with: - **Onboarding**: Principal-Level Guide, Zero to Hero Guide - **Getting Started**: overview, setup, usage, quick reference - **Deep Dive**: architecture → subsystems → components → methods 5. **Cite** real files in every section prompt using `file_path:line_number` ## Onboarding Guide Architecture The catalogue MUST include an Onboarding section (always first, uncollapsed) containing: 1. **Principal-Level Guide** — For senior/principal ICs. Dense, opinionated. Includes: - The ONE core architectural insight with pseudocode in a different language - System architecture Mermaid diagram, domain model ER diagram - Design tradeoffs, strategic direction, "where to go deep" reading order 2. **Zero-to-Hero Learning Path** — For newcomers. Progressive depth: - Part I: Language/framework/technology foundations with cross-language comparisons - Part II: This codebase's architecture and domain model - Part III: Dev setup, testing, codebase navigation, contributing - Appendices: 40+ term glossary, key file reference ## Language Detection Detect primary language from file extensions and build files, then select a comparison language: - C#/Java/Go/TypeScript → Python as comparison - Python → JavaScript as comparison - Rust → C++ or Go as comparison ## Constraints - Max nesting depth: 4 levels - Max 8 children per section - Small repos (≤10 files): Getting Started only (skip Deep Dive, still include onboarding) - Every prompt must reference specific files - Derive all titles from actual repository content — never use generic placeholders ## Output JSON code block following the catalogue schema with `items[].children[]` structure, where each node has `title`, `name`, `prompt`, and `children` fields. ## When to Use This skill is applicable to execute the workflow or actions described in the overview.
Related Skills
wiki-researcher
Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...
wiki-page-writer
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...
wiki-onboarding
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 fo...
software-architecture
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
skill-architect
Expert guide for designing and building high-quality skills from scratch through structured conversation. Use when someone wants to create a new skill, build a skill, design a skill, or asks for help making Agents do something consistently. Also use when someone says "turn this into a skill", "I want to automate this workflow", "how do I teach my Agent to do X", or mentions creating SKILL.md files. Covers standalone skills and MCP-enhanced workflows. Do NOT use for creating subagents (use subagent-creator) or technical design documents (use create-technical-design-doc).
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,
langchain-architecture
Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM w...
hexagonal-architecture-layers-java
Hexagonal architecture layering for Java services with strict boundaries. Trigger: When structuring Java apps by Domain/Application/Infrastructure, or refactoring toward clean architecture.
event-sourcing-architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e...
dotnet-architect
Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns.
docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks.
clean-architecture
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", or "use case boundary". Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.