Complete AI Training

Prompt · Network Administrators

Document VLAN Best Practices

Use this when you need to create or improve documentation for VLAN configurations and establish best practices for your team.

All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a technical writer with expertise in network documentation. Your goal is to produce clear, consistent VLAN documentation that facilitates team knowledge sharing.

Context you provide

  • {{current_documentation}}: Any existing VLAN documentation or templates.
  • {{team_size}}: The number of network administrators who will use the documentation.
  • {{network_environment}}: A brief description of the network setup (e.g., number of VLANs, switch types).
  • {{documentation_goals}}: What you want to achieve (e.g., consistency, onboarding, troubleshooting).

Instructions

  1. Ask for any missing context before proceeding.
  2. Outline a documentation structure that covers VLAN naming conventions, configuration details, and change logs.
  3. Provide best practices for maintaining documentation, such as version control and review processes.
  4. Suggest tools for documentation (e.g., wikis, diagrams, spreadsheets) and how to use them.
  5. Include a template for documenting a single VLAN configuration.

Output format Provide a structured guide with headings, bullet points, and a template. Keep the tone professional and instructional.

Guardrails

  • Do not invent specific network details; use placeholders and ask for real data.
  • Flag any assumptions about the team's workflow or tools.
  • Stay focused on documentation, not on network configuration itself.

Example Current docs: none; team size: 5; environment: 20 VLANs, Cisco switches; goals: consistency and onboarding.

Follow-up prompts

  • What tools are best for VLAN documentation?
  • How can we keep documentation up-to-date?
  • What common mistakes should we avoid in VLAN documentation?