프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. Google로 로그인하면 리뷰를 쓸 수 있어요.프로토타입 · 30분마다 업데이트
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

drawthe.net Skill

저장소 ↗

제작자: cidrblock★ 1,184skill 1개

설치

What it does

drawthe.net draws network diagrams dynamically from a text file describing the placement, layout and icons. Given a yaml file describing the hierarchy of the network and it's connections, a resulting diagram will be created.

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category 기타
제작자용: README에 배지 달기

제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/cidrblock-drawthe-net.svg)](https://mcp.popnx.com/en/skills/cidrblock-drawthe-net)

비슷한 Skill

같은 종류의 작업, Skill 목록과 같은 순서

비슷한 항목과 비교
이 항목
drawthe.net
llmfitclaude-videoVideoCaptionerclaude-cookbooks
제작자cidrblockAlexsJonesbradautomatesWEIFENG2333anthropics
Skill 수11114
GitHub 별1,18439,03621,08516,55754,799
마지막 코드 변경2026년 11월 13일2026년 11월 16일2026년 9월 25일2026년 9월 12일2026년 11월 5일
라이선스MITMITMITGPL-3.0MIT

cidrblock의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요

Skill과 MCP의 차이

MCP = 손

AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.

Skill = 안내서

작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.

겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.

쓸 수 있는 앱

Codex

제작자 README와 repo 폴더 기준

설치

Is it safe?

  • Who made it

    GitHub account cidrblock (person), 10 years old

  • Use and upkeep

    ★ 1,184 stars · code last changed 2026년 11월 13일

  • Any scripts?

    75 scripts that can run on a computer: .eslintrc.cjs, bin/container-entrypoint.sh, bin/drawthe-net.js, mcp/dsl-reference.ts and 71 more

  • Uses the internet?

    Scripts that go online: src/renderer/icon-loader.ts

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 8aeeacc (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

먼저: 어떤 AI를 쓰시나요

쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (389). Use "Let the AI install it" instead

Option 1Claude Code에게 설치 맡기기

이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요

Where to install
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) for all my projects, at ~/.claude/skills/drawthe-net. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) into the project this chat is open in (at .claude/skills/drawthe-net). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Claude Code를 다시 열고 /drawthe.net를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요

Checked against official docs 2026년 11월 12일 · Source: code.claude.com

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.claude/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.claude/skills/drawthe.net
  3. Claude Code를 다시 열고 /drawthe.net를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요

직접 설치한 Skill은 ChatGPT 데스크톱 앱, Codex CLI, IDE의 Codex 확장 프로그램에서 쓸 수 있습니다 · 웹과 모바일의 ChatGPT에서는 직접 설치한 Skill을 쓸 수 없고 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다

ChatGPT 데스크톱 앱

ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다

Option 1ChatGPT에게 설치 맡기기

ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요

Where to install
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) for all my projects, at ~/.agents/skills/drawthe-net. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) into the project this chat is open in (at .agents/skills/drawthe-net). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2폴더를 직접 넣기

drawthe-net 폴더를 ~/.agents/skills/drawthe-net에 넣으세요

~는 홈 폴더($HOME)입니다

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.agents/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.agents/skills/drawthe.net

설치한 뒤

  • ChatGPT 데스크톱 앱: 사이드바에서 Skills를 열어 Skill이 보이는지 확인하세요
  • 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
  • Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요

Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com

웹과 모바일의 ChatGPT

직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다

이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요

Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com

Option 1Codex에게 설치 맡기기

이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다

Where to install
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) for all my projects, at ~/.agents/skills/drawthe-net. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) into the project this chat is open in (at .agents/skills/drawthe-net). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요

Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.agents/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.agents/skills/drawthe.net
  3. Codex를 다시 열고 관련 작업을 요청하면 Codex가 skill을 목록에 보여 줘요

Option 1Cursor에게 설치 맡기기

이 문장을 복사해 Cursor 채팅에 붙여 넣으세요

Where to install
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) for all my projects, at ~/.cursor/skills/drawthe-net. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) into the project this chat is open in (at .cursor/skills/drawthe-net). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Cursor Agent 채팅에서 /를 입력하고 drawthe.net 선택

Checked against official docs 2026년 11월 12일 · Source: cursor.com

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.cursor/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.cursor/skills/drawthe.net
  3. Cursor Agent 채팅에서 /를 입력하고 drawthe.net 선택

Option 1Let the AI install it

Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat

Where to install
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) for all my projects, at ~/.claude/skills/drawthe-net (in Codex use ~/.agents/skills/drawthe-net, in Cursor ~/.cursor/skills/drawthe-net). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill drawthe-net from https://github.com/cidrblock/drawthe.net (commit 8aeeacc) into the project this chat is open in (at .claude/skills/drawthe-net; in Codex use .agents/skills/drawthe-net, in Cursor .cursor/skills/drawthe-net). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.

GitHub에서 보기 ↗

2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인

✓ 명령 확인 2026년 11월 18일

원본 SKILL.md 보기

아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요

처음 8,000자 표시 · GitHub에서 전체 파일 열기

---
name: drawthe.net
description: Draw network/architecture diagrams (AWS, Azure, Cisco) from a natural-language description or from a proposed system architecture, using the drawthe.net MCP server's YAML DSL and icon tools. Use this skill whenever the user asks to "draw a diagram", "create an architecture diagram", "visualize this infrastructure", "sketch the network", or asks you to propose/illustrate a system design.
---

# drawthe.net diagram authoring skill

This skill teaches an agent how to turn a description (or a proposed
architecture) into a drawthe.net YAML diagram and render it via the
drawthe.net MCP server's tools. The result should be a build blueprint:
someone reading it should understand what to provision, how traffic and
data move, what is required versus optional, and what to configure next.

### ARCHITECTURE DIAGRAM DESIGN SYSTEM & AESTHETIC DIRECTIVES

When authoring system architecture diagrams in YAML, adhere strictly to these architectural visual design principles:

#### 1. Architectural Layout & Directional Flow
* **Determine the Primary Axis:**
  * **Top-to-Bottom (Layered Systems):** Use for Tiered/Client-Server architectures (Presentation → Processing/Logic → Storage → External Infrastructure).
  * **Left-to-Right (Data & Workflow Pipelines):** Use for event-driven systems, ETL pipelines, integration flows, or user journey sequences.
* **Dedicated Cross-Cutting Rows/Columns:** Place auxiliary or cross-cutting services (e.g., Logging, Authentication, Telemetry, Storage) on a dedicated side column or bottom row rather than interspersing them within the core flow.
* **Spatial Breathability:** Always leave 1–2 empty grid steps between connected components to provide space for connection lines without crossing icons or text.

#### 2. Restrained Color System & Contrast
* **Canvas:** Use the established white canvas (`white`) unless the user requests another treatment.
* **Default Elements:** Use dark readable text and lines (`black` for labels and `#334155` for connections/borders). Do not use the historical orange renderer defaults for blueprint styling.
* **Containers:** Use light-gray or very lightly tinted fills with a consistent border, such as `#F1F5F9` with `#94A3B8`. Container color should establish hierarchy without competing with the topology.
* **Icons:** Preserve native vendor icon artwork. Do not impose a diagram-wide accent palette or override icon fills/strokes unless the selected icon has been previewed and the override is intentional.

#### 3. Domain Grouping & Boundaries
* **Container Enclosure:** Wrap related components in named groups (e.g., Services, Data Domain, External System, Core Boundary).
* **Line Style Rules:**
  * **Solid Lines:** Direct synchronous calls, primary system processes, or hard structural boundaries.
  * **Dashed Lines (`strokeDashArray: [4, 4]`):** Asynchronous events, metadata/telemetry flows, or logical/trust boundaries.
* **Group Headers:** Choose one placement for all group names, commonly `bottomMiddle` for north-to-south flows, and keep it consistent unless a collision is unavoidable.

#### 4. Typography & Label Symmetry
* **Unified Alignment:** Standardize `textLocation` across the entire diagram. Use the selected group/icon placement consistently; the established blueprint default is `bottomMiddle`. Never mix alignments within the same diagram unless a documented collision makes it unavoidable.
* **Readable Display Names:** Always use explicit, concise display text with the `text:` attribute (e.g., `text: "Auth Service"`) instead of raw technical identifiers (e.g., `auth_svc_node_01`).

#### 5. Connection Line Discipline
* Align connected components along straight grid lines to eliminate diagonal line clutter.
* Group multi-destination fan-outs neatly through shared alignment rather than overlapping multiple connection lines across the canvas.

## Prerequisites

The drawthe.net MCP server must be connected and expose these tools:

- `get_dsl_reference` — returns the full YAML DSL syntax reference.
- `list_icon_families` — lists available icon families and icon counts.
- `list_icons` — lists/searches icon names within a family.
- `get_icon` / `get_icon_svg` — preview a specific icon (PNG/SVG) to confirm it looks right before using it.
- `render_diagram` — renders a YAML diagram to PNG or SVG.

## Procedure

1. **Read the DSL reference first.** Call `get_dsl_reference` before
   writing any YAML if you have not already seen it in this conversation.
   Do not guess at the syntax — the `diagram`, `title`, `icons`, `notes`,
   `groups`, and `connections` sections each have specific required and
   optional fields.

2. **Identify the components in the description.** Break the request down
   into concrete entities (servers, load balancers, databases, gateways,
   VPCs/VNets, users, external services, etc.) and the connections between
   them. If the user proposes an architecture rather than describing an
   existing one, design a sensible one first (reasonable tiers, redundancy,
   networking boundaries), then diagram it.

    State the architecture assumption in the title or a note when the
    request is ambiguous. For example, RHDH on ROSA is materially different
    from RHDH on EKS or RHDH on EC2.

    Design the blueprint before choosing icons. Organize it into these layers
    where they apply:
    - prerequisites and network foundation: account, region, VPC, AZs,
       public/private subnets, routing, security groups, IAM, and certificates;
    - request path: users, DNS, edge/load balancer, ingress, and application;
    - platform: cluster, namespaces, operators, ingress controller, and
       workload replicas;
    - dependencies: identity, database, secrets, object storage, registries,
       source control, and observability;
    - build notes: required configuration, optional choices, and an ordered
       implementation sequence.

    Do not draw every plausible service. Include a component only when it
    answers a deployment question, and mark it as required, optional, or
    external in its label or notes.

3. **Choose the right icon family based on vendor keywords in the
   request** — there is no fixed default family. Inspect the request for
   vendor/platform signals:
   - AWS services/terms → `aws2026` (preferred, current) or `aws` (legacy).
   - Azure services/terms → `azure2026` (preferred), or `azureCloud` /
     `azureEnterprise` (legacy).
   - Cisco/network hardware terms → `cisco2026` (preferred) or `cisco` (legacy).
   - Generic/vendor-neutral request → pick whichever family has the closest
     conceptually matching icon; prefer the modern `*2026` families.
   Call `list_icon_families` if you're unsure what's available.

4. **Never invent an icon name.** For every component, call `list_icons`
   with the family and a keyword query (e.g. `query: "load_balanc"`) to find
   the real icon name before writing an `icon:` reference in YAML. Use
   `get_icon` or `get_icon_svg` to visually confirm an ambiguous match
   before committing to it.

5. **Always prefer a meaningful, accurate icon over a generic
   placeholder.** If an exact icon for a component doesn't exist in the
   chosen family, search for the closest conceptually similar icon (e.g. a
   generic "server" or "compute" icon for an unlisted service type) rather
   than defaulting to a plain box or an unrelated icon. Only fall back to a
   generic shape (e.g. via `notes`) if truly no reasonable icon exists in
   any relevant family.

6. **Write the YAML diagram** using the DSL: define `diagram` (grid size,
   background), optionally `title`, then `icons` (with `x`/`y` grid
   coordinates, using relative positions like `x: "+1"` where convenient),
   `groups` to box related components together, and `connections` between
   icon keys. Use YAML anchors for repeated styling if helpful.

    Start from the light, readable style below unless the user explicitly
    requests a different visual treatment:

토론

질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.

아직 글이 없어요. 처음으로 질문하거나 공유해 보세요.

이곳의 글은 사용자가 쓴 것으로, PopNx 팀의 글이 아니에요.

로그인하고 글쓰기

GitHub 정보

GitHub 스타
1,184
제작자
cidrblock
라이선스
MIT
최근 코드 수정
2026년 11월 13일
repo 안 SKILL.md(번역본과 템플릿 포함)
2
토픽
diagram, icons, network