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

ClassCommandWorking directoryEnvironmentRequired proofStatus
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

TierMeaningTypical commands
Required localMust pass before claiming starter or app work is donetest, lint, typecheck, build
CIMust pass before merge or releaseCI workflow, local CI equivalent
Device/browserRequired when runtime behavior depends on a real targetemulator, device install, browser smoke
Package/signRequired before distributable claimspackage, sign, verify artifact
Release/storeRequired before publish claimsstore upload, deploy, release dry-run
Paid/LLMUseful but not always mandatoryE2E evals, LLM judges, external services
ManualHuman-only verificationvisual review, policy review, credentials, store forms