菜单
Network architecture discipline — segmentation, routing, perimeter, traffic control. Cloud-agnostic; vendor constructs from memory-long §stack.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Context engineering — memory navigation, textual graph traversal, progressive disclosure, recovery. Load when assembling context for a task or when lost.
Implementation-side security discipline — headers, dependencies, secrets, authz. Load for hardening work (sec-ops domain).
Commit conventions, branching, anchors in messages, and the git safety rules. Load for any git operation beyond status/diff.
Anti-generic-AI design discipline — bans, tells, and the slop test. Load for ANY new UI surface or visual redesign. Inspired by Impeccable (Apache 2.0).
Motion & animation discipline — purpose, performance, reduced-motion. Load when work involves animation, transitions or scroll effects.
Microcopy discipline — buttons, errors, empty/loading/success states, alt text. Voice and tone come from the project's memory, not from this skill.
| name | network-design |
| description | Network architecture discipline — segmentation, routing, perimeter, traffic control. Cloud-agnostic; vendor constructs from memory-long §stack. |
Universal concepts — VPC/VNet/subnet syntax comes from memory-long §stack, the topology discipline doesn't change.
Hub-and-spoke for shared services (inspection, DNS, VPN) over full-mesh peering (N² rules) · load balancing at the right layer (L4 vs L7 — know why) · DNS is critical infrastructure: private zones for internal, health-checked records for failover.
New network path → who initiates, what port, which direction, why · public exposure → architect sign-off (never fast-path, per instructions) · flow logs enabled where the platform bills sanely.
