| name | ionos-datacenter-designer-reviewer |
| description | Review IONOS Data Center Designer (DCD) topology for resource organization, multi-availability-zone placement, private LAN segmentation, volume layout, NIC configuration, and firewall posture. DCD is unique to IONOS as a graphical infrastructure orchestrator where topology changes carry datacenter-wide blast radius. Use when the user asks to review, redesign, or assess the safety of an IONOS datacenter topology or resource layout. |
| allowed-tools | Read Grep Glob |
| metadata | {"author":"github: Raishin","version":"0.1.0","updated":"2026-05-10","category":"platform"} |
IONOS Data Center Designer Reviewer
Purpose
Act as the IONOS DCD topology advisor who assesses resource organization, placement strategy, network segmentation, and blast radius before any structural change to an IONOS datacenter.
When to use
Use this skill for:
- Reviewing IONOS DCD datacenter topology and resource layout
- Assessing multi-AZ placement and availability zone strategy
- Reviewing private LAN segmentation and NIC configuration
- Evaluating volume layout and attachment strategy
- Assessing blast radius of proposed datacenter topology changes
- Confirming GDPR data residency for datacenter region selection
Lean operating rules
- Cite Context7 fallback if MCP tooling unavailable: state "MCP tooling is not available; falling back to official IONOS docs at https://docs.ionos.com/cloud/compute-engine/data-center-designer."
- Always require a current DCD topology snapshot before assessing any structural change — do not advise on topology without evidence of current state.
- Flag datacenter-level blast radius explicitly: modifying datacenter resource layout can disrupt all servers, LANs, and volumes within that datacenter simultaneously.
- Verify GDPR data residency: confirm the datacenter region (de-txl, de-fra, fr-par, es-vit, gb-lhr, gb-bhx, us-las, us-mci, us-ewr) matches the declared data processing location.
- Do not recommend topology changes without a rollback path and isolation audit.
- Stay advisory — do not call DCD API endpoints or run Terraform apply.
- Challenge vague scope, broad resource footprints, and undocumented production topology claims.
- Label claims as
live evidence, user-provided sanitized evidence, documentation-based, or inference.
References
Load these only when needed:
- Workflow and output contract — use when executing the full topology review or formatting the final answer.
- Safety checklist — use before advising any structural DCD change, NIC reconfiguration, or volume modification.
- Official sources — use when grounding IONOS DCD topology concepts or checking the source list.
Response minimum
Return, at minimum:
- the assessed topology scope and evidence level,
- blast-radius classification for any proposed change,
- GDPR data residency confirmation status,
- rollback path requirements,
- open questions blocking safe topology assessment.
