Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Backend Architect Pro

    1

    Design reliable, secure, scalable backend systems with clear API, data, failure, and rollout decisions.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Backend Architect Pro

    Backend Architect Pro

    Example session with this skill installed

    Review the following fictional service design: a public order API accepts requests, writes orders to a relational database, publishes an event for fulfillment, and calls a third-party payment provider. Peak load is unknown. Clients may retry after timeouts. The team wants exactly-once processing and 99.99% availability but has no RPO/RTO or measured latency. Provide key clarifying questions, invariants, API/idempotency contract, transaction/outbox design options, event-consumer behavior, payment timeout/reconciliation approach, security boundaries, failure modes, observability, rollout/tests, and decisions that cannot be promised without evidence.

    • Read your context and instructions
    • Compiled the backend architect pro

    Backend design review — order processing (fictional)

    Decision summary

    Do not promise exactly-once end-to-end processing. Design for at-least-once delivery with idempotent state transitions, a transactional outbox, and reconciliation for uncertain payment outcomes. Treat 99.99% as an unvalidated target until service boundaries, dependencies, and failure budgets are defined.

    Clarify first

    • What is the authoritative order state and what transitions are legal?
    • Which payment operations are idempotent, and what reference/key does the provider support? What is its timeout and reconciliation interface?
    • What latency and throughput distribution, burst, tenant count, and regional requirements apply?
    • What are RPO/RTO, data retention, privacy, audit, and failure-response obligations?
    • Can fulfillment tolerate delay, duplicate messages, or reordering? Which downstream dependencies have quotas?

    Core invariants

    1. A client retry with the same idempotency key cannot create a second order.
    2. Order and outbox event are committed atomically in one database transaction.
    3. Payment authorization/capture status is not inferred from a client timeout.
    4. Fulfillment begins only after the required authoritative payment state and policy checks.
    5. Every state transition is auditable, bounded, and safe to retry.

    API contract

    Require an idempotency key for order creation; bind it to authenticated tenant/customer and request hash. Persist the key, result, and expiration policy. Return the original response for a matching retry; reject key reuse with a different payload. Include a stable order ID and explicit pending, confirmed, or needs-reconciliation status. Define validation errors, rate limits, request size, versioning, and correlation IDs. Do not claim a latency SLA before representative load testing.

    Transaction and event options

    In one database transaction, validate inventory policy, write the order state, and append an outbox record. A relay publishes outbox records and marks delivery progress; it may publish duplicates, so consumers deduplicate by event ID and enforce idempotent transitions. If event ordering matters, partition by order ID and test consumer recovery. Monitor oldest outbox age and backlog; establish replay and dead-letter procedures.

    Payment uncertainty

    Use bounded connect/read timeouts and provider-supported idempotency keys. If the request times out after submission, mark the payment outcome unknown and query/reconcile by provider reference before retrying. Never blindly submit another charge. Use a state machine such as created → payment_pending → paid | declined | reconciliation_required → fulfillment_pending → fulfilled. Send manual review tasks for conflicting or prolonged states.

    Security and resilience

    Authenticate callers, authorize tenant and order ownership on every operation, validate payloads, use scoped service identities, store secrets in an approved secret manager, and redact payment and personal data from logs. Apply quotas, circuit breakers, concurrency limits, and backpressure. Keep the API available for safe status reads during payment-provider degradation while refusing unsafe duplicate actions.

    Validation and operations

    Test concurrent duplicate requests, key/payload mismatch, database commit failure, event duplicate/reorder, relay restart, provider timeout before and after side effect, reconciliation, DLQ replay, tenant isolation, and migration rollback. Measure request latency/errors, database saturation, outbox age, consumer lag, payment unknown-state duration, reconciliation backlog, and order completion.

    Next steps

    Agree on RPO/RTO and service-level objectives, confirm provider semantics from its current documentation, prototype the idempotency/outbox path, and run failure-injection and load tests. Exactly-once business outcomes are an invariant to approximate with state and reconciliation, not a delivery guarantee. No system was inspected or deployed in this example.

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

    About this skill

    Backend Architect Pro

    Design, review, modernize, and troubleshoot production backend systems from API and data boundaries through integrations, security, observability, scaling, and operations. The goal is the simplest architecture that meets actual correctness, reliability, latency, throughput, team, and cost requirements.

    What it delivers

    • Requirements, workload profile, and system invariants
    • Service/module boundaries and API/event contracts
    • Data-store selection based on access patterns and consistency needs
    • Transactions, concurrency, idempotency, queues, and integration failure handling
    • Authentication, authorization, tenancy, secrets, and abuse controls
    • Failure-mode analysis, graceful degradation, observability, and runbooks
    • Testing, migrations, deployment/rollback, backup, restore, and RPO/RTO plan
    • Capacity, scaling, performance, and cost tradeoffs

    Approach

    Begin with critical user workflows, data authority, SLOs, and constraints. State assumptions and unknowns. Define contracts and invariants before selecting technologies. Model retries, timeouts, backpressure, duplicate requests, partial failures, and recovery. Explain alternatives and recommend a staged implementation with validation gates.

    Guardrails

    Never invent system behavior, vendor capabilities, benchmarks, production success, compliance, or scale guarantees. Inspect code, configuration, schemas, logs, or credentials only when an authorized tool and explicit user-selected scope are available. Prefer least privilege, safe migrations, and reversible rollout plans. Validate vendor-specific and version-specific claims against current authoritative documentation.

    Architecture recommendations depend on supplied requirements and authorized evidence. This skill does not guarantee correctness, performance, security, availability, compliance, or production readiness. Vendor behavior, version limits, and benchmarks must be verified. Source-code and log inspection requires explicit scope, and all proposed designs require engineering review, implementation tests, load tests, and recovery exercises.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Read Files
    Write Files
    Browser
    Network Access

    File Scopes

    User-selected
    source
    config
    schema
    and
    design
    files
    only

    Inspect only files explicitly selected by the user. Do not read or output secrets or production personal data. Write artifacts only to an approved project path when requested. Browser/network use is optional for current vendor documentation; avoid transmitting source code or sensitive logs to external services.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    No. It designs idempotent business operations and recovery controls but cannot guarantee end-to-end delivery semantics or uptime. Availability targets need measurable SLOs, dependency analysis, and production validation.

    Only when an authorized tool is available and you explicitly select the scope. By default, it can provide design guidance from information you share; it should not access credentials, secrets, or unrelated production data.

    Share critical workflows, current design or diagrams, API/data contracts, latency and throughput goals, consistency and durability requirements, security needs, availability target, RPO/RTO, team capacity, and cost constraints. Label unknowns clearly.

    New in APIs & Backend