enterprise architecture

    2

    Unified enterprise architecture toolkit for diagrams as code, arc42 documentation, and ADR management.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    enterprise architecture

    Example session with this skill installed

    Create a C4 container diagram for a payment processing system using Mermaid, then write an ADR for choosing PostgreSQL over a NoSQL alternative.

    • Read your context and instructions
    • Compiled the enterprise architecture

    I have generated the C4 container diagram and the corresponding Architectural Decision Record (ADR) using a shared element model for traceability.

    Payment Processing System Architecture

    C4Container
    title Container diagram for Payment Processing System

    Person(customer, "Customer", "A user who wants to pay for goods.")
    System_Boundary(payment_system, "Payment System") {
        Container(api, "Payment API", "Go", "Handles payment requests and validation.")
        Container(processor, "Transaction Processor", "Java", "Processes transactions with external gateways.")
        Container(db, "Payment Database", "PostgreSQL", "Stores transaction logs and audit trails.")
    }
    System_Ext(gateway, "Payment Gateway", "External API for credit card processing.")

    Rel(customer, api, "Makes payment", "HTTPS/JSON")
    Rel(api, processor, "Sends transaction", "gRPC")
    Rel(processor, db, "Reads/Writes", "SQL")
    Rel(processor, gateway, "Authorizes payment", "HTTPS/TLS")

    ADR 001: Choice of Relational Database for Transaction Storage

    Status: Proposed
    Date: 2023-10-27

    Context

    The payment system requires high ACID compliance for financial consistency. We need to choose between a relational database (PostgreSQL) and a NoSQL document store.

    Decision

    We will use PostgreSQL as the primary datastore for the Payment Database (ea:payment:db).

    Rationale

    • Data Integrity: Strong ACID guarantees prevent partial transaction writes.
    • Relational Mapping: Transaction schemas are highly structured and benefit from relational constraints.
    • Operational Maturity: The team has existing expertise in tuning and backing up PostgreSQL.

    Consequences

    • Positive: Guaranteed consistency for financial audits.

    Negative: Horizontal scaling is more complex than with NoSQL, but current load projections do not exceed vertical limits.

    Next steps

    1. Initialize the architecture/ directory and save the Mermaid diagram as container-view.mmd.
    2. Commit the ADR to docs/adr/0001-choice-of-database.md.
    3. Define the detailed table schema for the Payment Database in the next design phase.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Architecture documentation often rots because it uses inconsistent notations and fragmented tools. This skill unifies four open-source standards to deliver diagrams, docs, and decisions that stay traceable and useful across the entire software lifecycle.

    What it does

    • Standardized Diagramming produces C4 model views for software systems or ArchiMate for enterprise landscapes using Mermaid, PlantUML, or Structurizr DSL.
    • Architectural Documentation generates arc42-compliant system docs with a configurable detail level from lean to thorough.
    • Decision Tracking records architectural choices using ADR or MADR formats to capture context, options, and trade-offs.
    • Design Review assesses architectures against ISO/IEC 25010 quality attributes and provides severity-categorized findings.
    • Enterprise Modeling maps business capabilities to application and technology layers to support portfolio rationalization.

    How it works

    1. Select framework based on the required altitude, whether it is a single system (C4), the whole enterprise (ArchiMate), or a process change (TOGAF).
    2. Generate artifacts as code using text-based formats that reside in Git for versioning and diffing.
    3. Apply traceability by assigning stable, human-readable IDs to elements so they remain consistent across diagrams, ADRs, and docs.
    4. Validate consistency by running linting checks to ensure every referenced element is defined and every quality goal has a scenario.

    Frameworks & tools

    This tool works with C4 Model, ArchiMate 3.x, TOGAF ADM, arc42, and ADR/MADR. It outputs Structurizr DSL, Mermaid, and PlantUML.

    Why this beats prompting it yourself

    Generic prompts often mix notation levels or produce "box-and-arrow" soup that lacks semantic meaning. This skill enforces rigorous standards, ensuring your container diagrams actually follow C4 rules and your ADRs capture the "why" instead of just the "what."

    Use cases

    • Document a legacy system using arc42 to onboard new engineers.
    • Visualize a microservices landscape to identify external dependencies.
    • Write an ADR to justify choosing a specific database or messaging queue.
    • Review a proposed solution design for performance and reliability risks.

    Known limitations

    Does not support application code generation, cloud infrastructure as code (Terraform), or database schema design. It focuses on structural and enterprise architecture rather than implementation.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 8 days ago

    • Free to download with an account

    Requires

    Python

    Listed8 days ago

    What's inside

    Frequently Asked Questions