ywc-infra-design

Design cloud infrastructure topology and generate infra-design.md contracts before IaC authoring.

8|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-infra-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ywc-infra-design
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-infra-design
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-infra-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of fragmented or unverified infrastructure design by enforcing a structured, reviewable architecture process before any IaC is written.

Core Features & Use Cases

  • Requirements Gathering: Systematically captures workload, traffic, data, and compliance constraints.
  • Topology Design: Architect network, compute, storage, and IAM boundaries with a 3-lens reliability, cost, and security pre-check.
  • ADR Documentation: Automatically generates Architecture Decision Records to ensure all design trade-offs are documented and auditable.
  • Use Case: When starting a new service, use this skill to design the AWS topology and generate an infra-design.md contract that ensures your Terraform implementation is pre-validated and aligned with project constraints.

Quick Start

Invoke the ywc-infra-design skill to architect the cloud infrastructure for the payments-api service with an aws provider.

Frequently Asked Questions about ywc-infra-design

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

FAQPage Schema
How do I design cloud infrastructure architecture before writing Terraform code?

Cloud infrastructure architecture is designed by systematically gathering workload, traffic, and compliance constraints, then defining network, compute, storage, and IAM topology to validate reliability, cost, and security before IaC authoring.

What is an Architecture Decision Record and when do I need it for infrastructure refactoring?

An Architecture Decision Record (ADR) documents design trade-offs to ensure infrastructure decisions are auditable and reviewable. It is needed during infrastructure refactoring or new deployments to pre-validate topology against project constraints.

Can I use this to architect AWS topology for a new service deployment?

Yes, you can architect AWS topology for new service deployments by selecting cloud providers and defining infrastructure boundaries. The process outputs an infra-design.md contract ensuring alignment with reliability, cost, and security requirements.

What's the best way to document infrastructure design trade-offs for compliance validation?

The best way to document infrastructure design trade-offs is generating automated Architecture Decision Records (ADRs) during topology design. This captures reliability, cost, and security pre-checks, ensuring compliance validation before IaC implementation.

Do I need an infra-design.md contract format before authoring infrastructure as code?

Yes, you need an infra-design.md contract format to bridge architecture design and IaC authoring. It enforces a structured, reviewable process that pre-validates topology and integrates with downstream IaC authoring tools.