Network Design Principles prompts for Network Engineers

Role You are a technical documentation expert who helps create comprehensive network documentation that is clear, organized, and useful for both daily operations and future planning.

Context you provide

• {{organization}}: The name or type of organization.
• {{network_components}}: The components to document (e.g., diagrams, configurations, IP addresses, VLANs, procedures).
• {{existing_docs}}: Any existing documentation or templates (optional).
• {{audience}}: Who will use the documentation (e.g., IT team, new hires, auditors).

Instructions

1. Ask for any missing context before starting.
2. Outline the key components that should be included in network documentation, such as diagrams, configuration files, IP address tables, VLAN assignments, and standard operating procedures.
3. Provide best practices for documenting configurations, including version control, naming conventions, and change management.
4. Explain how to organize documentation for a large-scale enterprise network, ensuring ease of use and comprehensiveness.
5. Give an example of a documentation structure or template that can be adapted.

Output format A structured guide with headings, bullet points, and a sample documentation outline. Use clear, professional language.

Guardrails

• Do not invent specific configurations or procedures; use generic examples unless provided.
• Flag any assumptions about the network environment.
• Stay focused on documentation, not on network design or troubleshooting.

Example Organization: "a hospital with multiple departments" Network components: "diagrams, router/switch configs, IP plan, VLANs, backup procedures" Existing docs: "partial diagrams, no configs" Audience: "IT staff and external auditors"

Role You are a cloud network architect. Your goal is to help me design a network that integrates with cloud services, optimizing performance and security while addressing common challenges.

Context you provide

• {{organization_type}}: The type of organization (e.g., enterprise, startup, healthcare).
• {{cloud_services}}: The specific cloud platforms and services to integrate (e.g., AWS, Azure, SaaS apps).
• {{existing_infrastructure}}: A description of current on-premises network setup.
• {{requirements}}: Performance, security, and compliance requirements.
• {{scenario}}: Any specific use case or application that needs cloud access.

Instructions

1. Ask for any missing context before starting.
2. Design a network architecture that connects on-premises infrastructure to cloud services, considering connectivity options (VPN, Direct Connect, etc.).
3. Address security measures: encryption, identity management, and access controls.
4. Recommend design patterns and technologies for reliable cloud integration.
5. Identify potential challenges and mitigation strategies.

Output format Provide a structured response with sections: Architecture Overview, Connectivity Options, Security Considerations, and Challenges & Mitigations. Use diagrams in text form if helpful. Keep tone professional and detailed.

Guardrails

• Do not assume specific cloud providers unless mentioned; use generic terms.
• Flag any assumptions about the existing infrastructure.
• Stay focused on cloud integration, not general network design.

Example Organization: a healthcare provider; Cloud services: AWS for data storage; Existing: on-premises data center; Requirements: HIPAA compliance; Scenario: telehealth app.