PacketJedi
Players select every router that receives each OSPF LSA in a fictional three-area topology. Five rounds teach area scope, ABR summaries, and Type 5 flooding around a stub area, with RFC-cited feedback after answers.

The builder
- Name
- Seif Allaoua
- First spec project?
- Yes
- Began at
- NAF AC6
How it was built
- Model
- unknown
- Harness
- Codex CLI 0.169.0
- Spec method
- GitHub Spec Kit 1.4.3.dev0
- Spec artifacts
- constitution, spec, clarify, plan, tasks, checklists, research, data-model, quickstart, game-ui-contract
- Tasks
- 28 in 6 loops
- Built
- November 17, 2026
- Human prompts
- 11
Build environment
- MCP servers
- Node REPL MCP
- CUA REPL MCP
- Sources & RAG
- StarterKit/LAB_README.md
- references/rfc2328.txt
- references/rfc3101.txt
- Skills
- speckit-constitution
- speckit-specify
- speckit-clarify
- speckit-plan
- speckit-tasks
- speckit-analyze
- speckit-implement
- unified-computer-use
- Other tools
- Python 3.15
- curl
- Git
- Node REPL
- specify CLI
- AI assets
- Five hand-authored SVG character illustrations; no image generator used
Runtime: how to play
- Type
- static-web · HTML, CSS, JavaScript ES modules, JSON, SVG
- Start
- 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
- Chromium 153.0.8010.12
- Saves
- Active run is in memory; the top-five leaderboard uses per-browser localStorage with a try/catch fallback.
- Accessibility
- Keyboard controls exercised through five rounds; automated accessibility checks pass on the game and detail page. Responsive widths 320–1440 and reduced motion checked. Manual screen-reader testing remains unverified.
Verification
- Tests
- 22 passing · Browser suite at /tests/ in the source repository; 22 checks passed during Arcade review
- Facts from
- references/rfc2328.txt, references/rfc3101.txt
- Known limits
- The topology is fictional and does not model packet-level flooding, acknowledgements, retransmission, or route calculation.
- NSSA and Type 7 behavior are excluded.
- The LSA originator is excluded from selectable receivers by game convention.
- Manual screen-reader and cross-browser testing were not performed.
- License
- Apache-2.0
Who it is for.
PacketJedi is a static browser game for people learning OSPF. In each round, the player sees an LSA type, its origin, and a fictional topology, then selects every router that receives it. The five rounds progress from area-local LSAs to ABR summaries and Type 5 flooding with a stub area. Wrong answers identify extra or missing routers and show the relevant RFC 2328 section.
THE BUILD STORYHow it was made.
The work followed the workshop sequence: constitution, specification, clarification, plan, tasks, analysis, and implementation. The project records its constitution and feature artifacts under `.specify/` and `specs/001-lsa-flooding-game/`; the clarification allows negative scores and assigns Youngling to every score below 100. Implementation keeps receiver evaluation separate from scoring, run state, and local leaderboard storage. During RFC review, section references needed correction: §12.1.3 identifies the LS type field, Advertising Router is §12.1.5, Type 4 is covered under §12.4.3, and Type 5 under §12.4.4. The content validator also initially rejected periods in RFC section IDs; its ID pattern was updated to accept them. The documented preview command returned HTTP 200, and 22 domain, state, scoring, and leaderboard checks passed in the Node REPL. Browser automation was unavailable, so the browser suite and manual accessibility checks remain unverified. The next builder should run `/tests/` in a browser and complete tasks T024, T026, and T027 before claiming the release is ready to demo.
ADVICEFor the next builder.
- Keep the first three independent fixtures ordered as correct, plausible wrong, and Type 5 stub boundary.
- Run the browser suite and manual keyboard, screen-reader, narrow-width, reduced-motion, and subpath checks; these have not been verified yet.
- Keep scoring out of the receiver evaluator, and retain tests for storage failures and equal-score ordering.
Built a game of your own?
Fill in the ARCADE template with your build agent and send me your GitHub URL.
Add your game →