architecture-extract

Analyze project structure to derive module boundaries, data flows, and service relationships.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill architecture-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-extract
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/cross/architecture-extract
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill architecture-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates complex codebases into understandable architectural diagrams, clarifying module interactions, data flows, and overall system design.

Core Features & Use Cases

  • Module Boundary Analysis: Clearly defines the separation and responsibilities of different code modules.
  • Data Flow Visualization: Illustrates how data moves between services and components.
  • Architectural Pattern Identification: Detects and labels common patterns like microservices, monoliths, or event-driven systems.
  • Use Case: After a new codebase is scanned, use this Skill to generate an initial architectural overview for onboarding new team members or for a high-level system review.

Quick Start

Analyze the provided codebase to understand its architectural structure and key components.

Frequently Asked Questions about architecture-extract

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

FAQPage Schema
How do I map my codebase architecture to understand module boundaries and data flows?

Mapping your codebase architecture involves analyzing the project structure to derive architectural understanding, defining module boundaries, data flows, and overall system design from the scanned codebase files.

What is the best way to visualize system design and service relationships for a new project?

Visualizing system design is done by analyzing project structure to translate complex codebases into understandable architectural diagrams, clarifying module interactions and service relationships.

How do I identify architectural patterns like microservices or monoliths in my code?

Identifying architectural patterns requires analyzing the codebase structure, which detects and labels common patterns like microservices, monoliths, or event-driven systems based on service relationships and module boundaries.

Can I generate an architectural overview for onboarding new team members after a codebase scan?

Yes, generating an architectural overview for onboarding new team members is supported by activating this Skill after a codebase scan during bootstrap or when architectural insights are needed for memory ingestion.

Does this architectural extraction require any specific dependencies or components?

Architectural extraction requires no specific dependencies or components; it activates after codebase scans during bootstrap to satisfy requirements for system structure overview and dependency mapping.

When do I need to analyze architectural structure for memory ingestion?

Analyzing architectural structure for memory ingestion is needed when architectural insights are required during bootstrap or after codebase scans, allowing the system to understand service relationships and module boundaries.