Create and organize a PlayWeld project
Keep your game files, design notes, and project history together.
On this page
A PlayWeld project gives your game a home and keeps its notes and activity close by. Start with a new practice folder, then decide which files belong with the game and which records PlayWeld keeps for you.
Create a project deliberately
Project Home uses a six-stage wizard: name, description, engine family, genres, parent directory, and confirmation. Use a new location for experiments. Review the engine and destination before confirming; the chosen engine family is part of the project's identity.
The Control Room project setup using Lantern Workshop as an example.
Open the new project from the registered-project table. Confirm the workspace path if Theia presents a trust prompt. Some screens select a project independently, so check their selectors when moving between games.
Know which files belong where
| Location | Purpose |
|---|---|
game/ |
Native Unity, Unreal, or Godot project files |
docs/ |
Design documents and adopted decisions |
gamecrafter.project.json |
Project identity and engine metadata |
AGENTS.md |
Instructions for work on this particular game |
.agents/skills/ |
Project-specific skill instructions |
.gamecrafter/ |
Operational data managed by the service |
Some files still use the project's former GameCrafter name. PlayWeld still uses them, so leave them in place.
Check the outcome
A successful creation produces a registered project with the intended folder and engine. It does not install an engine or populate an empty native game directory. Add valid engine files before expecting file detection or headless operations.
For independent copies, use the supported clone or restore workflow. Copying another project's manifest can duplicate its identity. See backup and recovery before moving important work.
