<h1 align="center">
<a href="https://prompts.chat">
Parse the argument provided:
Loading actions...
<a href="https://prompts.chat">
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend linting, type safety, or ESLint configuration.
risks
Generate a complete Eve-ng lab guide for a CCNP ENCOR topic, and optionally deploy it automatically if Eve-ng MCP is connected.
Parse the argument provided:
16), find the matching folder: 16-VLANs/OSPF or RSTP), fuzzy-match against folder namesRead the topic's README.md to understand what key concepts the lab should demonstrate.
Create a complete lab document with these sections:
1–3 sentences: what the lab proves, what the user will configure, what they'll verify.
ASCII art showing the devices, their hostnames, interface labels, and connections. Include an IP addressing table: | Device | Interface | IP Address | Description |
| Hostname | Type | Eve-ng Image | Notes | Use standard Eve-ng images:
vios-adventerprisek9-m-15.9viosl2-adventerprisek9-m-15.2vios-adventerprisek9 (lightweight)Per device, in the order a real engineer would configure them. Every command in a code block. Brief comment before each block explaining what it does and why.
Exact show commands with expected output snippets. Format as:
R1# show ip ospf neighbor
Neighbor ID Pri State Dead Time Interface
10.0.0.2 1 FULL/DR 00:00:37 GigabitEthernet0/0
3–5 common mistakes for this topic and how to diagnose/fix them.
Save the lab guide to: ##-Topic-Name/lab/lab-guide.md
Create the lab/ directory if it doesn't exist. Use the Write tool to create the file.
Tell the user the file has been saved and where.
Check if the eveng MCP server is available (tools should be listed in the session).
If MCP is connected: Ask the user: "Your Eve-ng server is connected. Want me to deploy this topology now? I'll create the lab, add nodes, connect interfaces, and start the devices."
If they say yes:
create_lab to create a new lab with a descriptive name (e.g., "RSTP-Lab-26")add_node for each device in the topologyconnect_node_to_node or connect_node_to_network to wire the interfacesstart_all to boot all nodesIf MCP is not connected:
Say: "Eve-ng MCP is not connected, so I can't deploy automatically. Run /install-eveng-mcp to set it up, then re-run /lab [topic] to deploy."