| name | spock-lang |
| description | Create, inspect, validate, run, debug, and modify Spock v0 backend and framework projects using the published npm distribution. Use when turning product requirements into a Spock program; scaffolding or adopting a framework project; changing tables, records, functions, seed data, actor-aware operations, storage, or refusals; generating contracts, TypeScript, or GraphQL; or verifying Spock-backed Uhura behavior. |
Spock Language
Treat the user's request as an executable engineering task. Produce or modify
the program, run the relevant Spock commands, fix failures within scope, and
finish with concrete verification evidence.
Use only the published spock npm package. Do not assume the Spock source
checkout, a Rust toolchain, or source-built web assets are available.
Establish the environment
- Locate the target directory,
spock.toml, and existing .spock files.
- Require Node.js 18 or newer. Run
spock --version; if the command is
unavailable, install it once with npm install --global spock@latest, then
record the installed version. Use plain spock commands afterward.
- Classify the target as a framework project or a standalone
.spock
program. Framework commands operate on a project; build, run, and gen
operate on an explicit standalone file.
- Preserve unrelated user changes and never replace an existing model before
understanding its tables, functions, constraints, seeds, and consumers.
Select the source of truth
- Treat the globally installed npm CLI as the executable contract.
- Use the bundled references for concise guidance. Consult the
Spock v0.5.2 toolchain specification
when exact syntax or semantics matter; its RFD 0024 additions are explicitly
marked experimental and non-normative.
