architecture

Analyze filesystem layout and architecture documents to generate Mermaid diagrams and structured overviews.

17|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/insightflo/claude-impl-tools --skill architecture-insightflo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/insightflo/claude-impl-tools/tree/main/plugin/skills/architecture
Command: npx skills add https://github.com/insightflo/claude-impl-tools --skill architecture-insightflo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Querying and visualizing the full architecture of a codebase helps teams onboard, review, and plan evolution by providing a clear map of domains, APIs, layers, and tech stack.

Core Features & Use Cases

  • Full architecture overview with domain maps and Mermaid diagrams to communicate structure quickly.
  • API catalog, layer discovery, and tech-stack summaries to guide decisions during onboarding and reviews.
  • Use Case: When starting a new project or planning a domain refactor, generate a holistic view of the system to align team understanding.

Quick Start

Ask /architecture to generate the full architecture overview for your project.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I visualize a codebase architecture for team onboarding?

You can visualize codebase architecture by analyzing the filesystem layout and architecture documents to produce Mermaid diagrams, domain maps, API catalogs, and tech-stack summaries. This provides a holistic view to align team understanding during onboarding.

What is included in a full architecture overview of a large codebase?

A full architecture overview includes domain maps, API catalogs, layer discovery, and tech-stack summaries. By analyzing the filesystem layout and architecture documents, it outputs Mermaid diagrams and structured overviews to help teams review and plan evolution.

Can I generate an API catalog and layer diagram without modifying source code?

Yes, generating an API catalog and layer diagrams does not modify source code. The process analyzes the filesystem layout and architecture documents to produce Mermaid diagrams and structured overviews, ensuring the project remains unchanged.

Does this approach work for planning a domain refactor in a large codebase?

Yes, this approach works for planning a domain refactor in a large codebase. It generates domain maps and tech-stack summaries that align team understanding and guide evolution decisions without altering the source code.

What are the limitations of using filesystem layout to map project architecture?

Mapping project architecture via filesystem layout relies on existing directory structures and architecture documents. It produces visual diagrams and structured overviews without modifying source code, but may not capture runtime dependencies or dynamic behaviors.

When do I need to generate domain maps and tech-stack summaries for my project?

You need to generate domain maps and tech-stack summaries during onboarding, architecture reviews, or domain planning. These outputs align team understanding and guide decisions when working on large codebases.