How does the three-phase process work?

The skill follows a sequence: Phase 1 maps the system components, Phase 2 extracts global rules and invariants, and Phase 3 creates detailed profiles (dossiers) for each specific component.

Can I run specific phases individually?

Yes, you can use arguments like 'map', 'invariants', or 'dossiers' to trigger a specific phase of the investigation independently.

What kind of 'invariants' does this skill identify?

It extracts rules across 8 categories including Security, Data Ownership, API Contracts, Idempotency, and Failure Modes to ensure system integrity.

Does it support large repositories?

Yes, it is designed for quality by investigating one item or component at a time and tracking progress via YAML files to handle large-scale systems incrementally.

Where is the architectural data stored?

The skill generates structured YAML files directly within your repository in the system-map/ and component-dossiers/ directories for version-controlled documentation.

System Architecture Understanding

Name: System Architecture Understanding
Author: CAPHTECH

byCAPHTECH

0•

Herramientas para Desarrolladores

Analyzes codebases to generate structured system maps, architectural invariants, and detailed component documentation in YAML format.

This skill provides a structured framework for reverse-engineering and documenting complex codebases through a three-phase approach. It begins by mapping core system components and boundaries, progresses to extracting global architectural invariants (such as security rules and data ownership), and concludes by creating deep-dive dossiers for individual modules. By transforming raw code into high-fidelity, machine-readable documentation, it helps developers maintain a consistent mental model of system-wide constraints and dependency chains.

Características Principales

01Deep-dive component profiling including APIs, failure modes, and dependencies

02Automated extraction of security, data, and architectural constraints

03Standardized YAML output for all system components and boundaries

040 GitHub stars

05Three-phase architectural discovery: Mapping, Invariants, and Dossiers

06Incremental progress tracking for large-scale codebase investigations

Casos de Uso

01Rapidly onboarding developers to large or legacy codebases

02Performing architectural audits to identify security and logic gaps

03Maintaining living documentation of system rules and service contracts

Características Principales

01Deep-dive component profiling including APIs, failure modes, and dependencies

02Automated extraction of security, data, and architectural constraints

03Standardized YAML output for all system components and boundaries

040 GitHub stars

05Three-phase architectural discovery: Mapping, Invariants, and Dossiers

06Incremental progress tracking for large-scale codebase investigations

Casos de Uso

01Rapidly onboarding developers to large or legacy codebases

02Performing architectural audits to identify security and logic gaps

03Maintaining living documentation of system rules and service contracts