菜单
Routing & connectivity discipline — BGP, OSPF, hybrid links, the tunnel classics. Protocol-level (IETF), vendor syntax 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-routing |
| description | Routing & connectivity discipline — BGP, OSPF, hybrid links, the tunnel classics. Protocol-level (IETF), vendor syntax from memory-long §stack. |
Protocols are standards; only the CLI is vendor. Complements network-design (topology) — this is how traffic actually finds its way, on-prem, cloud and hybrid.
Area 0 is the backbone, everything attaches to it · use stub/NSSA areas to shrink LSA flooding at the edges · cost follows bandwidth policy, set explicitly — default auto-cost on mixed link speeds produces surprise paths · adjacency checklist when it won't form: MTU mismatch, area type mismatch, timers, authentication (in that order).
Dedicated link (Direct Connect/ExpressRoute-class) for steady bandwidth + predictable latency; VPN as backup on a different failure domain — both running BGP so failover is routing, not runbooks · test the failover path on schedule (an untested backup link is decoration — same law as backups) · asymmetric routing kills stateful firewalls: keep both directions on the same path or design for it.
MTU/fragmentation — tunnels eat bytes; clamp MSS, test with DF-bit pings · DNS split-horizon: internal names resolve internally on both sides · overlapping CIDRs between sites = NAT hell — prevent via the network-design CIDR plan, not mitigation.
Routing changes are architectural tier (never fast-path): peer review + maintenance window + rollback plan · before/after route table diff in the report · monitoring on session state and prefix counts (see observability principles).
