Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    System Architect

    1

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

    $19

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity 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

    FieldValue
    product_nameTaskSync
    slice_goalEstablish local-first persistence and process topology
    has_uiyes
    hostinglocal-first
    statusready

    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.

    What you get

    Determine if a project requires a server or can run as a local-only process.Define data durability and backup steps for local SQLite or flat-file storage.Map process listeners and ports to ensure zero unnecessary network exposure.Standardize infrastructure handoffs for downstream devops and planning roles.

    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.

    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

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 day ago

    • Passed all security checks, Safe to install

    Listed1 day ago

    Frequently Asked Questions