req-nf-inf-network

Generate and update AWS network design documents covering VPC, routing, and security.

Updated May 18, 2026
One-click install
npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill req-nf-inf-network
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: req-nf-inf-network
Source: https://github.com/ABLER-Digital-Services/ai-guild/tree/main/skills/req-nf-inf-network
Command: npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill req-nf-inf-network

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Network design documentation gets created inconsistently, missing key decisions about connectivity, security controls, and observability, which leads to rework and review delays.

Core Features & Use Cases

  • MECE-ready network document structure: Helps produce a complete network design (VPC/subnet, routing, access control, edge, external connectivity, bandwidth/transfer, monitoring/logging) in a consistent order.
  • Design guidance for core AWS network building blocks: Provides section-by-section instructions for SG/NACL/WAF, ALB/CloudFront/DNS, VPC peering/VPN/Direct Connect/PrivateLink considerations, and traffic/logging expectations.
  • Review checklist baked into the process: Supports updates and reviews of existing design documents with explicit validation points.

Quick Start

Ask your AI to generate the "基盤概要設計_ネットワーク編" document for your system by following the required MECE chapter structure and filling in VPC, subnet, routing, security (SG/NACL/WAF), edge (ALB/CloudFront/DNS), external connection, capacity, and monitoring sections.

Frequently Asked Questions about req-nf-inf-network

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a network design document for AWS that covers VPC, routing, and security groups?

Define enterprise network design documents by structuring VPC, subnet, routing, security groups, edge, external connectivity, capacity, and monitoring sections to fulfill MECE decomposition and review completeness requirements.

What should be included in an AWS network infrastructure design template?

Include sections for VPC/subnetting, routing, access control via SG/NACL/WAF, edge components like ALB/CloudFront/DNS, external connectivity through VPC peering/VPN/Direct Connect/PrivateLink, capacity planning, and traffic monitoring and logging.

How do I review and update an existing enterprise network design?

Update existing network design documents by applying the baked-in review checklist with explicit validation points to iteratively verify VPC connectivity, security controls, and observability configurations for MECE compliance and review readiness.

Does this network design skill support documenting Direct Connect and PrivateLink considerations?

Yes, the skill provides section-by-section design guidance for external connectivity, covering VPC peering, VPN, Direct Connect, and PrivateLink considerations to explicitly define network connectivity and traffic expectations.

Why does my network design documentation keep failing architectural reviews?

Network design documentation fails reviews when created inconsistently, missing key decisions about connectivity, security controls, and observability, leading to rework and delays that a standardized MECE document structure prevents.