ww-architecture

Generate Mermaid architecture diagrams and API references for World Weaver codebases.

3|1|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/astoreyai/claude-skills --skill ww-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ww-architecture
Source: https://github.com/astoreyai/claude-skills/tree/main/skills/memory/world-weaver/skills/ww-architecture
Command: npx skills add https://github.com/astoreyai/claude-skills --skill ww-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation, maintenance, and validation of architecture documentation for World Weaver, reducing drift and manual effort.

Core Features & Use Cases

  • Generate up-to-date architecture diagrams and module documentation from codebases.
  • Validate documentation against code changes and provide updates on demand.
  • Use cases include onboarding new contributors, audits, and architecture reviews.

Quick Start

Document the architecture of the World Weaver project, including modules, data stores, and interactions.

Frequently Asked Questions about ww-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture documentation from a codebase automatically?

You can generate architecture documentation automatically by parsing modules, mapping dependencies, and outputting module summaries, API references, and Mermaid diagrams to ensure consistent, repeatable docs.

What is the best way to create Mermaid diagrams for module dependencies during a refactor?

Creating Mermaid diagrams during a refactor is handled by mapping codebase dependencies and generating visual diagrams automatically, which helps validate architecture changes and maintain accurate documentation.

Can I validate existing architecture docs against recent code changes?

Yes, you can validate architecture documentation against code changes to identify drift, providing on-demand updates to module summaries and diagrams during codebase growth or refactoring.

How do I document modules and API references for onboarding new contributors?

Documenting modules and API references for onboarding involves parsing the codebase to map interactions and data stores, automatically producing module summaries and API documentation outputs.

Does this architecture documentation approach require any external dependencies?

No, this approach requires no external dependencies to automate architecture documentation, applying module parsing and Mermaid diagram generation directly during reviews or audits.

Why does architecture documentation drift from the codebase over time?

Architecture documentation drifts over time due to manual upkeep efforts, which you can reduce by automating module parsing and validation to generate repeatable, up-to-date API references and diagrams.