forge
Clone forge-starter
Your projectone repo, one app at ./app
forge beside ita container, not an install
Skills bundled.claude/skills/ · Claude drives

The starter, explained

your project foldercompose.yaml· the control plane.env· FORGE_SECRETS_KEY./forge· the CLI wrapper./new-app· the one command.claude/skills/· for your agentapp/your app · Next.js · forge.app.json.forge/state · resources · events · secretsforge control planecontainer · api · :371724 capabilitiesFORGE_WORKSPACE = your folderFORGE_STATE_DIR = .forgeyour app's containersweb :3000postgres :5432started by capabilities, via DockerDockerthe only requirementhost daemon./forgeexecs the CLImounted atthe same pathdocker.sockruns web + postgresstate
The starter has no platform source of its own: it points a control-plane container at your folder, mounted at the same path on both sides so nested Docker resolves your files. ./forge is a one-line wrapper that execs the CLI inside that container.

Ask your agent provision-app

you
What is in this folder?
claude
Your app in app/, forge running beside it as a container, and three skills that tell me how to drive it — the picture above.

From the terminal

$ make up # start forge      $ make logs
$ make down # stop it          $ make pull # newer control plane
provision-appScaffold, provision, build, test, lint and explain a new forge application end-to-end.
add-a-featureSpecify, design, implement and verify a new feature in your forge application.
frontend-designDesign and implement UI components that feel original, not template-like.

3 skills exist today (forge-starter v0.2.0 · pins forge 1.56.0). The full set covering every capability is the step-4 plan — each increment adds skills and resolves the INVENTED tags.