Made of little things.

# Napplet Space integration

This project includes the maintained napplet/boilerplate and unchanged upstream
napplet-* skills. Start with napplet-make. Protocol guidance stays upstream;
this note maps its local tooling commands to the installed Napplet Space CLI.

## Commands

- The project is already scaffolded. Do not run another creator CLI or re-scaffold it.
- Skills are already installed locally in .agents/skills and .claude/skills.
  The upstream npx skills command is an alternative for other environments.
- napplet-space setup prepares the pinned Node/pnpm toolchain and dependencies.
  Nothing is installed globally; ordinary pnpm commands also work if you have it.
- napplet-space run verify runs the upstream guidance/type/build checks.
- napplet-space run test:conformance runs the upstream reference-shell checks.
  Its pinned test browser is downloaded and cached on first use.
- napplet-space dev watches the Vite build inside the Napplet Space sandbox.
  Use its URL for preview. The upstream pnpm dev URL serves source without a host.
- napplet-space build makes dist/index.html. Edit index.html, src/main.ts and
  src/styles.css; keep the upstream Vite configuration and dependency lockfile.
- napplet-space check checks the existing built artifact in our host.
- napplet-space publish --dry-run inspects source and destinations;
  napplet-space publish publishes the existing build. Build after editing and
  before publishing. Publication and checks never execute project scripts.
- For older single-file projects whose napplet.json entry is index.html, edit
  that file directly and use dev/check/publish; no build toolchain is required.

## Metadata and host support

napplet.json owns this client's creator reference, name, identifier, topic labels,
relay/resource hints and publication destinations. It replaces the upstream
CLI's deployment configuration in this workflow; never put creator secrets in
the project. The default endpoints already point to napplet.soy.

Keep hard domain requirements in vite.config.ts; the publisher reads the build's
napplet-requires metadata and checks it against this host. Optional domains must
degrade gracefully, following upstream guidance. Use the injected namespace and
SDK; do not add a bootstrap or a private protocol extension to app code.

This host provides identity, storage, theme, resource, relay/outbox reads,
common reads, user-confirmed links and session files. Social writes, signer
operations, ContextVM and cross-napplet operations are not currently granted.
A domain's presence does not promise that every operation will be permitted.
Our host check complements upstream conformance; report each result separately.

## Upstream maintenance

Pinned boilerplate: https://github.com/napplet/boilerplate/tree/cbbebe9bd56271277b054535c0a8d720a588f61d
Pinned skills: https://github.com/napplet/napplet/tree/976ad0549c38f93d4ed418d3ea59a615a7e5fd7f

Upstream source, configuration, documentation and scripts are retained. Local
changes: package name, this integration note, agent entry pointers, private-state
gitignore entries, and excluding installed skill folders from the boilerplate's
repository-guidance scan. Skill bodies and licenses are unchanged. Run
napplet-space skills update to install the CLI's bundled skill revision; modified
files are reported as conflicts and preserved. Template/source changes are never
applied by that command.