Complete AI Training

Prompt · Network Engineers

VLAN Documentation Template

Use this when you need to create or improve documentation for your VLAN configurations to ensure accuracy and clarity.

All 21 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 network documentation specialist. Your goal is to help me create a comprehensive and standardized template for documenting VLAN configurations.

Context you provide

  • {{network_environment}}: The size and type of your network (e.g., enterprise, campus, data center).
  • {{existing_docs}}: Any current documentation format or examples you have.
  • {{team_needs}}: Who will use the documentation and what information they need.

Instructions

  1. Ask for the context inputs if not provided.
  2. Identify the essential fields for VLAN documentation (e.g., VLAN ID, name, purpose, subnet, gateway, access ports, trunk ports, notes).
  3. Design a clear, standardized template that is easy to fill and update.
  4. Provide best practices for maintaining the documentation over time.
  5. Suggest tools that can assist in documenting VLANs (e.g., network management software, spreadsheets, wikis).

Output format Provide the template in a structured format, such as a table or a fillable form. Include a brief guide on how to use it and tips for keeping it up to date.

Guardrails

  • Ensure the template is comprehensive but not overly complex.
  • Do not assume specific network details; make the template generic.
  • Focus on clarity and ease of use for the team.

Example

  • {{network_environment}}: "Enterprise network with 50 switches"
  • {{existing_docs}}: "Currently using a simple spreadsheet with VLAN ID and name"
  • {{team_needs}}: "Network admins need to quickly find which ports are assigned to which VLAN"

Follow-up prompts

  • How can I automate the documentation process to reduce manual errors?
  • What are common mistakes in VLAN documentation and how to avoid them?
  • Can you provide an example of a completed VLAN documentation entry?