Developer tooling
Forge
A local game-development workspace for agent sessions, content editors, validation, and exports across projects.
- Focus
- Developer experience · Content pipelines
- Current state
- Local development tool
- Built with
- Next.jsTypeScriptZodVitest
The problem
Game development brings together code, content, tools, and multiple agent sessions. Moving between those surfaces makes it harder to keep the project and its generated data consistent.
What I built
- Built a project-aware web workspace with terminal sessions, changes, commands, and notes.
- Added content editors for items, skills, maps, and other game data, with validation before export.
- Separated game-specific profiles from the shared workspace so more than one engine can use the tool.
- Extracted Forge from Edgewalker into its own repository as the tooling grew beyond one game.
The engineering behind it
Content flows one way into a game through validated exports. Profiles define what each project can edit and export, while the shared workspace stays reusable.
Where it is today
A locally run suite under active development, supporting Edgewalker and TheAscension content pipelines. It is a development tool, not a public SaaS offering.
Keep exploringEdgewalker