Import your own game

sandscape init <folder> maps a folder tree verbatim into a new Sandscape project, so exclude everything that isn't game content first. init honors .gitignore and .sandscapeignore at the folder root, and always skips node_modules/ and .git/. It creates a new project on your account.

Before you run it

1. If there's no .gitignore, create one. Exclude build output and dev cruft: node_modules/, dist/, build/, .next/, out/, coverage/, *.log, .DS_Store, and any tmp/scratch dirs.
2. Keep the real game and its source material — concept art, references, raw models, audio, the design doc (gdd.md / ARCHITECTURE.md). Sandscape wants those; they aren't cruft.
3. Want git to keep a file but Sandscape to skip it? Put it in .sandscapeignore (same syntax) instead of .gitignore.

init prints how many paths it excluded — check that summary before continuing so you know the cut was right (e.g. node_modules/ gone, assets/ and reference/ kept).

Backfill — optional, costs coins

By default, init imports your files and auto-registers recognized asset files (images/3D/audio) for free; code and config files are kept but not registered as assets. The design metadata starts sparse.

--backfill runs an optional, coin-metered pass where the AI reads your imported game and fills in Sandscape's design — the concept, art style, asset descriptions, and the plan — so you can keep building on Sandscape with the AI instead of just storing a copy of your files.

sandscape init <folder> --backfill

It prints the exact coin cost and your current balance before doing anything, and spends nothing if your balance is too low. Not sure? Run plain sandscape init <folder> — the import is free, and you can enrich the design later in the Sandscape app.