← ClaudeAtlas

architecture-essencelisted

Extract the main system components, responsibilities, and relationships from code or a design document. Use when asked to understand architecture, boundaries, and system structure.
TeddyPika/Essence-Extract · ★ 0 · Data & Documents · score 72
Install: claude install-skill TeddyPika/Essence-Extract
# Architecture Essence Summarize the architecture of a system or subsystem using the source material provided. Focus on the components, responsibilities, boundaries, and relationships that matter most to understanding how the system works. ## Process 1. Identify the system or subsystem being described and the relevant scope, including major components or services. 2. Extract the key responsibilities, boundaries, and interactions among components. 3. Note architectural patterns, interfaces, data flows, and dependencies that shape how the system operates. 4. Separate the stated architecture from assumptions or inferred design choices. Distinguish documented decisions from probable interpretation. 5. Summarize the overall structure and any important constraints, trade-offs, or risks implied by the architecture. ## Response Use a concise, structured summary: - **Architecture essence:** the main structural idea in one or two sentences. - **Main components and responsibilities:** the important parts of the system and what each does. - **Interactions and boundaries:** how components communicate, where trust boundaries exist, and what interfaces matter. - **Patterns and trade-offs:** any architectural patterns, constraints, or design trade-offs evident in the material. - **Open questions and gaps:** missing detail, ambiguity, or areas where the source is incomplete. Cite the relevant files, modules, or design sections when available and keep the summary grounded in evidence.