Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    System Architect

    1

    Architect lean infrastructure by defining hosting, topology, backups, and secrets without cloud bloat.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    System Architect

    System Architect

    Example session with this skill installed

    Read docs/architecture.md and define the infrastructure for 'TaskSync', a local-first desktop task manager. Hosting is local-first. Output to docs/infrastructure.md.

    • Read your context and instructions
    • Compiled the system architect

    I have analyzed the TaskSync architecture and non-functional requirements. The infrastructure handoff has been generated at `docs/infrastructure.md` with a status of `ready`. ## docs/infrastructure.md | Field | Value | | :--- | :--- | | **product_name** | TaskSync | | **slice_goal** | Establish local-first persistence and process topology | | **has_ui** | yes | | **hosting** | local-first | | **status** | ready | **Decision** Local-first. The NFR requires "no network" and "zero-latency local storage," which dictates a standalone process with no external cloud dependencies. **Topology** - **Processes**: One Electron-based desktop process owning the UI and local DB lifecycle. - **Listeners**: `none`. No HTTP or REST ports are exposed. - **Storage**: `data/tasks.db` (SQLite) located relative to the application data directory. **Backups** - **What**: `data/tasks.db` - **Where**: Operator-triggered copy to a user-defined external directory or cloud-synced folder (e.g., Dropbox/OneDrive). - **Restore**: Manual replacement of the SQLite file from the backup copy. **Secrets** `none`. The current slice has no identity requirements or external API integrations. **Deploy** Run the packaged executable on the desk machine. Packaging and installer creation are deferred to a later slice. **Observability** Local log file written to `logs/app.log`. No external telemetry. **Cost** $0 monthly infrastructure. **Failure modes** - **Disk full**: SQLite write failure. Recovery: Notify user to clear space. - **Missing data file**: Process start failure. Recovery: Initialize new empty database. **Will-not-build** - No Docker containers. - No REST API or localhost listener. - No managed database or cloud object storage. **Residual** - **implemented**: no - **devops**: skipped (no CI needed for local-only binary this slice) **Next steps** 1. Review the `docs/infrastructure.md` for topology alignment. 2. Initialize the `data/` and `logs/` directories in the project root. 3. Move to the `senior-planner` skill to sequence implementation tasks.

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

    About this skill

    The problem

    Infrastructure planning often devolves into cloud shopping sprees, over-engineering local apps with unnecessary clusters, and stalling projects with vague hosting decisions.

    What it does

    • Evaluates software architecture and non-functional requirements to define a concrete hosting shape.
    • Specifies process topology, storage paths, and listener ports while strictly avoiding unnecessary networking for local-first apps.
    • Outlines durable backup procedures and secret management without introducing external SaaS dependencies.
    • Produces a standardized docs/infrastructure.md contract that dictates deployment strategy without writing implementation code.

    Why this beats prompting it yourself

    This skill prevents the common AI tendency to suggest a "fleet of clouds" for a simple desktop app. It enforces a strict "no server" policy where appropriate, ensuring your infrastructure remains as lean as your P0 requirements. It acts as a gatekeeper, blocking the workflow if hosting decisions or architectural prerequisites are missing rather than guessing.

    Use cases

    • Defining infrastructure for a local-first desktop application using SQLite.
    • Mapping out the minimal hosted topology for a P0 web service MVP.
    • Establishing backup and secret management protocols for a single-operator tool.
    • Generating infrastructure handoffs for automated developer workflows.

    Known limitations

    This skill produces documentation only. It does not author Dockerfiles, Terraform scripts, or application code. It requires an existing architecture document to function.

    Does not author Dockerfiles or CI/CD code. Requires an existing architecture document. Will not select a cloud vendor if hosting is undecided.

    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 2 months ago

    Permissions

    Read Files
    Write Files
    Browser
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    The System Architect creates a standardized `docs/infrastructure.md` file that defines hosting topology, storage paths, and security protocols without unnecessary cloud overhead. It prevents 'infrastructure bloat' by ensuring your deployment plan remains as lean as your software's core requirements.

    This skill requires an existing architecture document or project summary to function correctly. It acts as a gatekeeper, meaning it will request missing architectural prerequisites rather than guessing or suggesting generic, expensive cloud solutions.

    No, this skill is focused on architectural strategy and documentation only. It defines the 'contract' for your infrastructure, but it does not generate Terraform scripts, Dockerfiles, or other implementation code.

    This skill is designed for versatility and is compatible with most major AI agent frameworks and LLM-based platforms that support markdown-based workflows. It integrates seamlessly into existing developer environments as a specialized documentation agent.

    Unlike generic prompts that often default to complex cloud architectures, this skill enforces a strict 'lean-first' policy. It is specifically tuned to prioritize local-first solutions, single-operator tools, and minimal MVP topologies over expensive SaaS dependencies.

    Your purchase includes the System Architect skill logic, a guide for integration into your agent workflow, and lifetime access to any future updates or refinements to the architecture logic.

    New in Agents & Orchestration