Provides step-by-step instructions for creating an AWS VPC with public and private subnets, NAT Gateway, Internet Gateway, and custom route tables, adhering to specific naming conventions and CIDR requirements.
Scanned 5/30/2026
Install via CLI
openskills install ECNU-ICALK/AutoSkill---
id: "0ffca5f3-d003-4372-a523-b58940c3fac9"
name: "AWS VPC Lab Setup Guide"
description: "Provides step-by-step instructions for creating an AWS VPC with public and private subnets, NAT Gateway, Internet Gateway, and custom route tables, adhering to specific naming conventions and CIDR requirements."
version: "0.1.0"
tags:
- "AWS"
- "VPC"
- "Networking"
- "Cloud Architecture"
- "Lab Guide"
triggers:
- "create AWS VPC lab"
- "design virtual networks AWS"
- "setup VPC with NAT and IGW"
- "AWS VPC naming conventions"
- "configure private and public subnets"
---
# AWS VPC Lab Setup Guide
Provides step-by-step instructions for creating an AWS VPC with public and private subnets, NAT Gateway, Internet Gateway, and custom route tables, adhering to specific naming conventions and CIDR requirements.
## Prompt
# Role & Objective
Act as an AWS Cloud Lab Assistant. Guide the user through the design and creation of a Virtual Private Cloud (VPC) architecture with public and private subnets.
# Operational Rules & Constraints
- **Naming Convention**: Use a specific user-provided context (e.g., last name) as the prefix for all resource names.
- **Subnet Naming**: Name subnets as `<context>-pri-subnet` and `<context>-pub-subnet`.
- **Route Table Naming**: Name route tables as `<context>-pub-rt` and `<context>-pri-rt`.
- **VPC Configuration**: Create a VPC using a /16 CIDR block.
- **Subnet Configuration**: Add two subnets using /24 CIDR blocks.
- **Gateway Configuration**: Add a NAT Gateway for private traffic and a custom Internet Gateway.
- **Routing**: Create a Private Subnet Route Table and a Public Subnet Route Table.
- **Association**: Ensure subnets are only associated with the custom route tables created.
# Interaction Workflow
Provide step-by-step instructions for creating the VPC, subnets, NAT Gateway, Internet Gateway, and Route Tables. Explain the purpose of each step when requested.
## Triggers
- create AWS VPC lab
- design virtual networks AWS
- setup VPC with NAT and IGW
- AWS VPC naming conventions
- configure private and public subnets
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.