spw.quest

Keep Spw on your phone, or in a repository.

On a phone, spw.quest opens from your home screen. In a repository, Spw Workbench adds the language's tools beside your own files.

On your phone

Add spw.quest to your home screen. It opens on the guide, in its own window, without the browser around it.

Pages you have opened with a connection open again without one; a page never opened shows a short offline note instead. On iPhone and iPad the home-screen app keeps its own storage, so a note kept in Safari does not follow it there: copy or download the note first.

In a repository

Choose who runs the setup. Copy one block. Run it from the repository root. It stops before any commit.

Spw Workbench adds the Spw language, parser, CLI, and editor tooling. It mounts at .spw/_workbench; your repository keeps its own .spw/. It needs Git and Node 20.19+ or 22.12+.

Shell
test -d .git || git init
git submodule add https://github.com/spwashi/spw-workbench .spw/_workbench
git -C .spw/_workbench checkout 850077ab48e02c58c2b55787075a7b97c9e4bf4f
npm --prefix .spw/_workbench ci --ignore-scripts
npm --prefix .spw/_workbench run spw:init -- ../.. --preset quest
npm --prefix .spw/_workbench run spw:doctor -- ../..
git diff --check

This copy now ends with the five git commands. They do not commit.

Claude
claude -p 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.'

This copy now ends with the five git commands. They do not commit.

Codex
codex exec 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.'

This copy now ends with the five git commands. They do not commit.

Grok
grok 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.'

This copy now ends with the five git commands. They do not commit.

Another agent
Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.

Git, in this order

Use this when the block you copied does not already run git. Run only the command that matches the folder you have.

  1. No .git yet → git init. Creates the repository.
  2. No .spw/_workbench in .gitmodules → git submodule add. Records where the workbench comes from.
  3. Link just added → checkout. Pins the reviewed revision.
  4. Link recorded, folder empty → submodule update --init. Downloads that revision.
  5. git diff --check only looks. It does not edit or commit.
git.txt · git.md
test -d .git || git init
git submodule add https://github.com/spwashi/spw-workbench .spw/_workbench
git -C .spw/_workbench checkout 850077ab48e02c58c2b55787075a7b97c9e4bf4f
git submodule update --init -- .spw/_workbench
git diff --check

When it worked

Same result for every choice above.

Then, if you want

After doctor, give the same agent one question about this repository. Skip this if you only wanted the mount.

Use the mounted workbench
Read .spw/README.md, .spw/index.spw, .spw/workspace.spw, and .spw/mount.spw.
Treat .spw/_workbench as mounted infrastructure. The consumer owns the surrounding .spw tree.
Choose one bounded question about this repository. Navigate before reviewing:
npm --prefix .spw/_workbench run spw -- roots
npm --prefix .spw/_workbench run spw -- tree @spw --depth 3
Use the mounted-consumer review skill only as an instrument, following this repo's rules.
Record evidence under consumer-owned .spw/audits/ with consumer and workbench revisions.
Keep this repository's own CSS nouns, copy, and framework.

What Spw is · Full recipe · Prompts · quest.json · Upstream quick start · What was hard to follow