iac-planning
Infrastructure as Code planning. Tool selection, module design, state management, environment separation, CI/CD integration, drift detection, policy-as-code, secrets handling.
What this skill does
# IaC Planning You plan Infrastructure as Code approach: tooling, structure, state, CI/CD, policy, secrets. ## Tool selection | Tool | Best for | |---|---| | **Terraform (HCL)** | Multi-cloud, mature ecosystem, large community | | **OpenTofu** | Terraform fork with open governance (post-BSL) | | **Pulumi** | Real programming languages (TS / Python / Go / .NET) | | **CloudFormation** | AWS-only, native, slower adoption | | **AWS CDK** | AWS-native with TypeScript/Python abstraction over CF | | **Bicep** | Azure ARM abstraction | | **Google Cloud Deployment Manager** | GCP; less popular vs Terraform | | **Crossplane** | K8s-native multi-cloud (CR-based) | Most teams: Terraform / OpenTofu unless AWS-exclusive (CDK OK) or prefer programming (Pulumi). ## Module design - **Layered modules**: base (networking / IAM) → platform (K8s / RDS templates) → application (per-service) - **Versioned** (semver; Git tags or Registry) - **Thin composition** top-level (mostly wiring modules) - **Inputs + outputs documented** - **Reusable across environments** Anti-pattern: monolithic root module with everything. ## State management - **Remote backend** (S3 + DynamoDB lock / GCS + locking / Terraform Cloud / Spacelift / Atlantis) - **State locking** always on - **Encryption at rest** for state - **Access control** on state bucket - **Per-environment state** (dev / staging / prod separate) - **No secrets in state** (use data sources / KMS references) ## Environment separation strategies | Strategy | Notes | |---|---| | **Workspaces** | Single codebase; switch workspace; simple but risky (wrong-env applies) | | **Directories** | One root dir per env (dev/ staging/ prod/); clearer separation | | **Separate accounts / subscriptions** | Strongest; Landing-zone pattern | | **Separate repos** | Maximum isolation; more overhead | Most robust: directories + separate accounts. ## CI/CD integration - **PR trigger**: `terraform plan` on PR for review - **Merge trigger**: `terraform apply` to target env - **Approval gate** for prod - **OIDC federation** to cloud (no long-lived keys) - **Plan review mandatory** — don't auto-apply without human review for prod - **Staged rollouts** — dev → staging → prod ## Policy as code Prevent misconfigurations pre-apply: | Tool | Notes | |---|---| | **OPA (Rego)** | General policy; used by Terraform Cloud | | **Sentinel** | Terraform Cloud native | | **Checkov** | Static analysis for Terraform / CloudFormation / K8s | | **tfsec / terrascan** | Terraform-specific scanners | | **AWS Config rules / Azure Policy / GCP Organization Policy** | Runtime enforcement | Typical policies: - Encryption required (S3, EBS, RDS) - Public access blocked by default - Required tags present - Region allow-list - Instance type allow-list (cost control) ## Drift detection - Periodic `terraform plan` compared to state - Alerts on unexpected diffs - Tools: Terraform Cloud drift detection, Spacelift, env0 ## Secrets handling - Never in state or code - Reference via KMS / Secrets Manager via data source - See `secrets-management-design` ## Common anti-patterns - State file committed to repo - Hardcoded account IDs / secrets - Single module doing everything - Auto-apply to prod without review - No policy enforcement - Untested modules going to prod ## Report ```markdown # IaC Plan: [Scope] ## Tool Selection [Chosen + rationale] ## Module Structure [Base / platform / application layers + registry] ## State Management [Backend + locking + encryption + access] ## Environment Separation [Strategy] ## CI/CD Integration [PR plan + approval + OIDC + staged rollout] ## Policy as Code [Tool + policies] ## Drift Detection [Approach + cadence] ## Secrets Handling [Reference pattern] ## Migration / Adoption [From current state] ``` ## Failure behavior - No CI/CD for IaC → require before prod - State in repo → block; remediate first - Auto-apply to prod → require review gate
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.