PACketMan - Networking Maze
Move a packet through six networking lessons, choosing routes and making decisions at checkpoints. Learn how routing, ACLs, transport, subnets, QoS, and congestion affect packet delivery.

The builder
- Name
- A.J. Ragusa
- From
- Bloomington, Indiana, United States
- First spec project?
- Yes
- Began at
- NAF AC6
How it was built
- Model
- unknown
- Harness
- Copilot SDK in VS Code
- Spec method
- GitHub Spec Kit
- Spec artifacts
- spec, plan, tasks, research, data-model, quickstart, checklists
- Tasks
- 39 in 6 loops
Build environment
- MCP servers
- GitHub MCP Server
- Sources & RAG
- Workshop StarterKit feature brief
- RFC 791
- RFC 792
- RFC 4301
- RFC 9293
- RFC 768
- RFC 1122
- RFC 4632
- RFC 2474
- RFC 4594
- RFC 5681
- RFC 7567
- RFC Editor status and update information
- Skills
- speckit-implement
- speckit-git-commit
- Other tools
- Node.js built-in test runner (Node v26.7.0)
- Python standard-library HTTP server
- Git
- integrated browser
Runtime: how to play
- Type
- static-web · HTML5, CSS, JavaScript ES modules, Python 3 standard library for local serving
- Start
- cd WORKSHOP/LAB/Examples/PACketMan && python3 -m http.server 8000 --bind 127.0.0.1
- Then open
- http://127.0.0.1:8000/
- Install needed
- No
- Internet needed
- No
- API key needed
- No
- AI at runtime
- No
- Tested on
- Integrated browser (version unknown), Chromium 153.0.8010.12
- Saves
- In-memory only; reloading starts a fresh session.
- Accessibility
- Keyboard movement supports arrow keys, WASD, and direction buttons; reduced-motion behavior and 320px layout were checked in browser automation. Manual keyboard-only play and screen-reader testing were not run.
Verification
- Tests
- 48 passing · cd WORKSHOP/LAB/Examples/PACketMan && npm test
- Facts from
- RFC 791, RFC 792, RFC 4301, RFC 9293, RFC 768, RFC 1122, RFC 4632, RFC 2474, RFC 4594, RFC 5681, RFC 7567
- Known limits
- The five-person first-time learner study has not been run, so the 5-10 minute completion and learning-outcome targets are unverified.
- Manual keyboard-only and screen-reader testing remain outstanding.
- Networking behavior is a deterministic teaching model, not a live network or vendor implementation.
- The ACL lesson uses a small ordered first-match policy, not a universal firewall configuration.
- QoS uses a declared local strict-priority queue model, not a service guarantee.
- Congestion and loss use authored integer risk points and finite deterministic traces, not probabilities or TCP feedback.
- License
- Apache-2.0
Who it is for.
PACketMan is a browser game for learning practical networking decisions. Move a packet through a branching maze, clear three checkpoints in each of six lessons, and collect optional network bits. The lessons cover routing, ordered ACL rules, TCP and UDP, subnet boundaries and gateways, QoS, and congestion and loss. Roaming ghosts can catch the packet and ask an extra question about the current lesson.
THE BUILD STORYHow it was made.
The work followed a Spec Kit feature specification, then research and design artifacts, an ordered task list, and phased implementation. The first playable campaign covered six networking lessons, but the owner wanted a stronger PAC-MAN-style feel; the maze was reshaped around a grid, gates, branching paths, and collectible bits. Further feedback asked for more decisions and paths, so each lesson gained three sequential checkpoints. The owner then requested roaming ghosts that trigger an extra question when they catch the packet. We kept those questions separate from required checkpoint grading so a catch or wrong answer would not erase lesson progress. Ghosts pause during questions and while the game is paused; the chase updates sprites in place so routine movement does not disturb focus or scroll. The dependency-free Node suite now passes 48 cases, and a browser playthrough verified all 18 checkpoints and ghost encounters. The five-person learner study and manual screen-reader and keyboard-only checks are still outstanding. A future builder should preserve that separation between arcade pressure and network correctness.
ADVICEFor the next builder.
- Keep the learning checkpoints independent from collectibles, ghost questions, and other optional arcade events.
- Test ghost movement, pause, capture, retry, and recovery as state transitions, not only as animation.
- Treat the learner study and manual assistive-technology checks as release work; automated tests do not replace them.
Built a game of your own?
Fill in the ARCADE template with your build agent and send me your GitHub URL.
Add your game →