Scaffold a Project

sn init + sn pull

The v0.6 workflow starts outside the chat → execute loop. sn init inlines four project templates (app / monorepo / feature / minimal) so the initial file layout and CLAUDE.md conventions are consistent. sn pull captures tables, roles, scopes, action types, trigger types, and choice values — the reference data that sn preflight --offline and sn execute --offline answer against instead of hitting the network.

sn init --dry-run prints the file plan without writing anything. Use it to inspect a template before committing to it.

Tasks

Scaffold a new project with the `app` template.

sn init --template app --name payroll-skills ./payroll-skills

✓ Scaffolded payroll-skills at ./payroll-skills (15 files)

Next steps:

cd ./payroll-skills

cp .env.example .env

sn preview manifests/example-business-rule/manifest.ts

List what was scaffolded so you know what's yours to edit.

cd payroll-skills && ls -la

Snapshot instance reference data for offline preflight.

sn pull manifests/example-business-rule/manifest.ts

Pulling reference data from dev12345…

✓ Pull cache written to manifests/example-business-rule/.sn-pulls/manifest.pull.json

1842 tables · 287 roles · 42 scopes · 418 action types · 18 trigger types · 124 choice values (2 fields)

Next Level

Preview & Preflight

Human review + instance-aware validation