The web frontend — and, for a Next.js app on Vercel, its serverless API routes too. It is its own node, NEVER bundled into backend compute (an App Runner/ECS service is the API, not the place to host the SPA). Config knobs: framework ("next" | "static" | "react"), target ("vercel" | "aws").
Author a NEW infra-plugin component when a design needs a capability the registry doesn't have yet (e.g. CloudFront/CDN, OpenSearch, a SaaS). Researches the Terraform provider schema and the existing component format, writes the 4-file component to the contract, registers it, and validates it. Use during /plan-infra…
Produce a CLEAR architecture diagram from an infra spec.json that imports cleanly into draw.io. Use when a generated diagram looks messy (overlapping arrows, edges across pages), when the user wants a better/clearer diagram, or after /plan-infra to give a readable picture. The spec is the deterministic source of…
Deep-research a NEW infra-plugin component from a documentation URL the user supplies. Crawls the doc page, fans out subagents over the relevant subpages/links (argument reference, IAM/auth, limits, pricing), and synthesizes a verified schema — then hands off to the author-component skill to write, register, and…