Wiki architect

Skill aiskillstore/marketplace/skills/sickn33/wiki-architect

Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.

Install

npx -y skills add aiskillstore/marketplace --skill wiki-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

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 understand a project's architecture at a high level.

SKILL.md

2.7 KB, 535 tokens by cl100k_base, as published. Nobody here has run it

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

Scan the repository file tree and README
Detect project type, languages, frameworks, architectural patterns, key technologies
Identify layers: presentation, business logic, data access, infrastructure
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
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:

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
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.