Commands
Commands are the pack’s proof surface. A stack pack may recommend a stack only after exact commands exist or each missing command has an explicit Not applicable reason.
Command Rules
- Record the working directory for every command.
- Record required environment variables without secret values.
- Distinguish local, CI, device, package, signing, release, cleanup, and paid commands.
- Include expected proof, not just the command text.
- Do not hide commands behind wrapper scripts unless the wrapper is a durable project tool.
Required Command Matrix
| Class | Command | Working directory | Environment | Required proof | Status |
|---|---|---|---|---|---|
| Create | [command] | [path] | [env] | [new app layout] | `[verified |
| Dev | [command] | [path] | [env] | [local URL, emulator, process, or device proof] | `[verified |
| Test | [command] | [path] | [env] | [passing output] | `[verified |
| Lint | [command] | [path] | [env] | [passing output or reason absent] | `[verified |
| Format | [command] | [path] | [env] | [check or write behavior] | `[verified |
| Typecheck | [command] | [path] | [env] | [passing output or n/a reason] | `[verified |
| Build | [command] | [path] | [env] | [artifact path or output] | `[verified |
| Package | [command] | [path] | [env] | [installer, apk, image, bundle, archive] | `[verified |
| Sign | [command] | [path] | [env] | [signed artifact or manual prerequisite] | `[verified |
| Release | [command] | [path] | [env] | [deploy/store/upload result] | `[verified |
| Emulator/device | [command] | [path] | [env] | [device ID, screenshot, logs] | `[verified |
| CI | [command] | [path] | [env] | [workflow or local CI-equivalent result] | `[verified |
| Cleanup | [command] | [path] | [env] | [generated artifacts removed safely] | `[verified |
Command Entry Template
Use this format when a command needs details beyond the table:
### [Command Class]
Command:
```bash
[exact command]
```
Working directory: `[path]`
Requires: `[tools, env vars, device, auth, network]`
Expected proof: `[what success looks like]`
Failure handling: `[what to inspect first]`
Gate Tiers
| Tier | Meaning | Typical commands |
|---|---|---|
| Required local | Must pass before claiming starter or app work is done | test, lint, typecheck, build |
| CI | Must pass before merge or release | CI workflow, local CI equivalent |
| Device/browser | Required when runtime behavior depends on a real target | emulator, device install, browser smoke |
| Package/sign | Required before distributable claims | package, sign, verify artifact |
| Release/store | Required before publish claims | store upload, deploy, release dry-run |
| Paid/LLM | Useful but not always mandatory | E2E evals, LLM judges, external services |
| Manual | Human-only verification | visual review, policy review, credentials, store forms |