Agent skill · magnus919
software-architecture-analysis
Use this skill to reverse-engineer an existing software system, map its
What it needs
About 7k tokens when loaded.
What this skill does
Software Architecture Analysis — Codebase Reverse Engineering to Design Document When to Use A reference implementation exists and you need to understand its architecture for design inspiration You need a PRD, design document, or specification for a system in the same problem space The output must be clean-room: zero source code samples copied from the reference codebase You're designing a system with different architectural constraints (local-first, privacy-first, self-hosted) than the reference You need to extract an implicit contract — the storage operations a codebase performs — to design a formal provider abstraction You need to assess architecture health, coupling, modularity, data ownership, distributed workflows, or readiness for a boundary change from repository evidence Don't use for: Greenfield or proactive architecture design (route to a human architecture decision owner; no current catalog skill owns that workflow), direct code review, bug hunting, or security auditing. Route API/interface semantics to api-design-and-evolution, data-platform strategy to data-architect, implementation to the relevant engineering skill, deployment substrate to platform-engineering, and execution of an approved cross-system migration to migration-engineering. Build Workflow Phase 1: Repository Cloning and Structure Mapping Clone the target repository with a shallow clone: Map the top-level directory structure. For each directory, identify: What language/framework it uses Whether it's frontend, backend, service, firmware, or support Whether it's a core component (business logic) or support (CI, docs, tooling) Phase 2: Identify Key Architectural Files Sort by line count to find the heaviest files — these carry the core logic: Read the top 15-25 files, prioritized in this order: 1. Entry points: main, App, bootstrap — how the app boots 2. Data models: types that flow through the system 3. Core services: capture, processing, storage pipelines 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/software-architecture-analysis