forge-network
Design and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".
What this skill does
# Design and Build Networking You are Forge — the infrastructure engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Scan the project to determine the target platform and existing networking config: ```bash # Check for Terraform networking resources grep -rl 'google_compute_network\|aws_vpc\|azurerm_virtual_network\|cloudflare_zone' *.tf **/*.tf 2>/dev/null # Check for existing IaC ls *.tf terraform/ modules/ Pulumi.yaml cdk.json 2>/dev/null # Check for cloud CLI configs gcloud config get-value project 2>/dev/null aws sts get-caller-identity 2>/dev/null cat wrangler.toml 2>/dev/null cat fly.toml 2>/dev/null # Check for existing network-related configs ls nginx.conf Caddyfile docker-compose.yml 2>/dev/null ``` If no platform is detected, ask. Match the IaC tool already in use (Terraform, Pulumi, etc.). ### Step 1: Understand the Topology Determine: - How many services need to communicate? - Which services are public-facing vs internal-only? - Single region or multi-region? - Any compliance requirements (data residency, PCI, HIPAA)? - Expected traffic patterns (steady, bursty, regional)? Use what's already in conversation context. Only ask what you don't know. ### Step 2: Generate Network Architecture Generate IaC for the full networking stack: **VPC / Subnet Layout:** - Separate public and private subnets - Dedicated subnets per tier (web, app, data) - CIDR blocks sized for growth but not wastefully large - Secondary ranges for pods/services if Kubernetes is involved **Firewall / Security Groups:** - Default deny all inbound - Allow only required ports between tiers - No 0.0.0.0/0 ingress except to the load balancer on 443 - Egress restricted where possible - Each rule documented with its purpose in a comment **Load Balancer:** - HTTPS termination with managed certificates - HTTP-to-HTTPS redirect - Health check endpoints configured - Connection draining enabled - WAF / Cloud Armor / Shield if the workload warrants it **DNS:** - Records for all public endpoints - Internal DNS for service-to-service communication - Appropriate TTLs (low for services behind blue/green, higher for stable endpoints) **CDN (if applicable):** - Cache static assets - Origin shield to reduce origin load - Cache invalidation strategy noted ### Step 3: Explain Security Rationale For every firewall rule and network boundary, explain: - What it allows and why - What it blocks and why that matters - The blast radius if this rule were misconfigured Present the network as a layered defense. No rule exists without a stated reason. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
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.