VectorRen is a small, stubborn, joyful revival of vector‑based arcade games — built in pure SVG, running directly in the browser, and crafted with the kind of engineering discipline that comes from a few decades of seeing how the web actually evolves.
This isn’t a framework.
This isn’t an engine.
This is a collection of tiny, self‑contained games that prove you can still build something elegant without dragging a dependency forest behind you.
VectorRen is vibe‑coded for fun, but it’s also a living demonstration of how to build clean, intentional software in a world where Coding Assistants sit in the passenger seat. It’s what happens when you mix old‑school craft with modern tools and just enough mischief to keep things interesting.
- A renaissance of vector graphics
- A playground for SVG as a first‑class rendering engine
- A set of small, inspectable, hackable browser games
- A showcase of best practices in a Coding Assistant era
- A reminder that simplicity still works
Each game stands alone.
No shared engine.
No shared runtime.
Just shared philosophy.
Because vectors age better than most of us.
They’re crisp, scalable, expressive, and honest.
They show every line you meant to draw — and every line you didn’t.
And after two decades of browser evolution, SVG is finally as powerful as it always should have been.
If you want to understand why this matters, check out docs/origin-story.md.
Spoiler: I’ve been doing this long enough to say things like “I’m not old, I’m deprecated” and mean it.
VectorRen/
├── docs/
│ ├── philosophy.md
│ ├── principles.md
│ ├── origin-story.md
│ ├── architecture.md
│ ├── svg-guidelines.md
│ ├── game-template.md
│ ├── naming-conventions.md
│ ├── behavior-specs.md
│ ├── patterns.md
│ ├── testing.md
│ ├── glossary.md
│ └── roadmap.md
├── games/
│ └── vectoroids/ (first game)
├── site/ (production site)
├── test-harness/ (shared test runner)
├── CONTRIBUTING.md
└── README.md
The docs/ folder is the soul of the project.
The games/ folder is where the fun lives.
games/vectoroids/— the first game- More games coming soon, each with its own identity and its own engine
No two games will share code, but they’ll all share the same ethos.
If you want to understand how VectorRen thinks, start here:
docs/philosophy.md— the whydocs/principles.md— the rulesdocs/svg-guidelines.md— the craftdocs/game-template.md— the blueprint
The full documentation lives in the docs/ folder.
Pull requests are welcome — but keep them small, clean, and intentional.
VectorRen is about clarity, not cleverness.
Before contributing, please read:
docs/philosophy.mddocs/principles.mddocs/svg-guidelines.mddocs/game-template.mdCONTRIBUTING.md
Issue templates and PR templates are provided to keep everything sharp and behavior‑first.
MIT.
Because open source should be an invitation, not a negotiation.
VectorRen is a return to form — a reminder that the things we build for fun often end up being the things that matter most. If you want to explore, learn, fork, remix, or just enjoy the glow of vector lines on a dark background, you’re in the right place.
Let’s see where this goes.