architecture

Document high-level system architecture with components, boundaries, and data flows.

77|11|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/mcouthon/agents --skill architecture-mcouthon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/mcouthon/agents/tree/main/.github/skills/architecture
Command: npx skills add https://github.com/mcouthon/agents --skill architecture-mcouthon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture mode helps teams capture high-level system structures, interfaces, and design decisions to improve clarity and alignment without getting bogged down in implementation details.

Core Features & Use Cases

  • Identify system boundaries, contracts, and responsibilities across components.
  • Map data flows and integration points to reveal dependencies and API surfaces.
  • Produce diagrams (component, data-flow, and sequence-like views) to communicate design decisions.
  • Highlight key trade-offs and failure modes to guide planning and risk assessment.

Quick Start

Provide a concise high-level overview of the current system by asking Architecture mode to generate a diagram and a contract outline.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document system architecture and define component boundaries?

To document system architecture, you outline high-level components, boundaries, and public APIs to reduce ambiguity. This approach captures responsibilities and contracts across components without delving into implementation details.

What is the best way to map data flows and integration points for system redesign?

Mapping data flows involves identifying dependencies and API surfaces across integration points. This reveals how data moves between components and highlights key trade-offs to guide planning and risk assessment.

Can I generate architecture diagrams and interface contracts without writing implementation code?

Yes, you can generate architecture diagrams and interface contracts without implementation code. The process produces component, data-flow, and sequence-like views to communicate design decisions clearly.

How do I highlight failure modes and design trade-offs during system onboarding?

Highlighting failure modes and design trade-offs during system onboarding involves documenting key architectural decisions. This clarifies system structure and risk factors to improve team alignment without implementation specifics.

Does system design documentation help with analyzing API surfaces and integration points?

System design documentation helps analyze API surfaces by mapping data flows and integration points. It identifies dependencies and outlines public interfaces to reveal how components interact across system boundaries.