System-design judgment for planning cloud infrastructure — how to choose and size components (databases, caches, queues, scaling, consistency, realtime). Use when deciding WHICH infrastructure components a workload needs (and during /plan-infra in the infra-designer plugin).
Plan, deploy, and audit cloud infrastructure from a single reproducible spec, backed by a registry of declarative components that compile to plain Terraform.
Research and add a new infra component from a documentation link the user provides — crawl the docs, fan out subagents over the relevant subpages, then write, register, and validate the component.
The only entry-point/load-balancer node in the catalog — there is no API Gateway type, so public traffic enters here and gateway-style concerns get pushed into the services. Config knobs: listenerPort (443), targetPort (3000), sslPolicy, scheme, healthCheckPath (default /health).
Fully managed compute for containerized web apps/APIs — no servers to patch. Default compute choice when an app just needs to run a container behind HTTPS.
Fully-managed key-value store; single-digit-ms reads/writes at any scale. Config knobs here: billingMode, pointInTimeRecovery, streamEnabled. When to pick DynamoDB at all → data-modeling.md; key/index design rules → db-indexing.md.
One virtual machine that boots Docker (user-data) and runs the app's container. Cheapest fixed-cost compute: a t3.small is $15/mo flat, no per-request pricing — undercuts managed compute for steady hobby/MVP traffic.
Serverless containers with no EC2 to manage — more configurable than App Runner. Config knobs: minCount/maxCount (auto-scaling bounds), assignPublicIp.
In-memory data structure store: microsecond commands, sub-millisecond network reads, 100k+ writes/sec per node. Fast because everything lives in RAM and runs on one thread.
Managed, ordered, replayable event stream — the deployable streaming primitive. Records are retained (default 24h, up to 365 days) and each consumer reads independently at its own offset, so the same events can feed many pipelines and be re-read after a bug fix. Config knobs: streamMode, retentionHours.
Single-node managed Postgres. Default choice for relational data — and often replaces other nodes (see "Built-ins"). Config knobs: instanceClass, storageGB, encrypted, multiAz, publiclyAccessible, dbName.
Managed cron (EventBridge Scheduler): fires on a schedule and triggers exactly ONE target — an aws.lambda.function or an aws.sqs.queue. Config knobs: scheduleExpression (default rate(1 day)), timezone (default UTC).
Pub/sub fan-out: one published message is delivered to EVERY subscriber, where a queue delivers each message to ONE consumer. Config knob: fifo (false).
Managed message queue; the catalog's only queue node. Config knobs: fifo (false), visibilityTimeoutSec (30), retentionDays (4), dlqEnabled (true). Use it for async work handoff — see long-running-tasks.md for the job pattern, scaling-writes.md for write buffering, multi-step-processes.md for workflow chains.
A managed Postgres with a public, pooled, TLS endpoint — plus auth, storage, and realtime if you want them. The serverless-friendly database that pairs with a Vercel frontend or any external/edge compute. Provisioned in the Supabase dashboard, not IaC.