Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    Architecture Integrity Reviewer

    1

    Audit service boundaries, data flows, and deployment designs for hidden coupling, failure risk, and change cost before you build it.

    Free

    2 installsSecurity scanned
    Architecture Integrity Reviewer

    Architecture Integrity Reviewer

    Example session with this skill installed

    We're proposing a new order service that will share the existing customer PostgreSQL database and write directly into the inventory tables to keep the migration fast. Checkout currently calls the payment provider synchronously. The team is six engineers with one part-time SRE, and we ship daily. Can you review this design for architectural integrity — boundaries, data consistency, failure modes — compare a minimal option against a target option, and produce a decision record plus a validation plan we can bring to Friday's design review? Context docs are in docs/arch/.

    • Read your context and instructions
    • Compiled the architecture integrity reviewer
    • Generated the UI component

    Summary

    Order-service proposal reviewed: the shared customer database and direct writes into inventory tables create hidden coupling and an unowned failure path. Approved with conditions — establish data ownership and put inventory mutations behind an explicit contract before build starts.

    Findings

    AreaFindingRiskRecommended action
    BoundaryOrder service writes inventory tables directlyHighExpose inventory via versioned API with idempotency keys
    DataCustomer DB shared by two servicesHighSplit schema by domain; add outbox + reconciliation job
    ResilienceSynchronous payment call inside checkoutMediumMove to event stream with dead-letter handling
    ObservabilityNo queue-depth or retry telemetry plannedLowEmit backlog metrics tied to checkout success rate

    Decision record (ADR-014)

    Status: proposed. Chosen: modular monolith with domain-scoped schemas; extract the order service once the read/write split proves stable. Revisit if write volume doubles or a second team consumes order events.

    Next steps

    • Block new cross-service table access with lint/CI rules this sprint
    • Add contract tests for the inventory API before any consumer ships
    • Run a payment-outage chaos drill; define rollback as checkout success dropping below 99.5%

    architecture-integrity-reviewer.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    The problem

    System designs often suffer from hidden coupling, unmanaged failure modes, and high change costs that only surface after deployment. Developers struggle to objectively weigh architectural tradeoffs against team topology and operational reality.

    What it does

    • Identifies boundary erosion and integration leaks in microservices or modular monoliths.
    • Traces failure paths including retries, idempotency, and cascading outages across service boundaries.
    • Evaluates data consistency models, from strong transactional integrity to eventual consistency patterns.
    • Produces formal Architecture Decision Records (ADR) with explicit tradeoffs, validation plans, and rollback conditions.

    Why this beats prompting it yourself

    This skill moves beyond generic design patterns to focus on the economics of change and operational health. It enforces a rigorous multi-step workflow that catches high-risk triggers, such as shared database integration or synchronous fan-out, which standard LLM prompts often overlook.

    Use cases

    • Reviewing a service decomposition plan to ensure independent deployability and clear ownership.
    • Auditing event-driven systems for schema governance, message ordering, and retry safety.
    • Comparing a modular monolith against a microservices transition based on team size and scaling needs.
    • Assessing multi-region deployment designs for data residency and disaster recovery risks.

    Known limitations

    Does not perform local syntax or unit-test reviews. Requires clear business constraints and quality attributes to provide meaningful architectural evaluation.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    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

    2 installs

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 8 days ago

    • Free to download with an account

    Listed8 days ago

    What's inside

    Frequently Asked Questions