progressive-modularity-review
Use this skill when a change touches CLI startup, package dependencies,
published package surfaces, setup/configuration, module state, storage
initialization, built-in catalog visibility, host, native permissions, processes,
daemons, launchers, models, browsers, audio, integrations, sync/remote, network,
or sidecars.
Procedure
- Read
CONSTITUTION.md, ADR 0031, docs/decision-map.md, the host
boundary docs, and docs/data-storage-boundary.md.
- Classify the change as a cheap definition, cheap local state, optional
capability, domain area, heavy dependency, process, permission, network
action, or external/provider action.
- Ensure safe CLI paths stay quiet: help, inspect, setup preview, modules
status/list, command discovery, and basic task CRUD must not open apps, start
persistent processes, request native permissions, download assets/models, or
call external services.
- Keep technical capabilities separate from human areas. Do not activate niche
domains through
advanced.
- Use
enable for visibility/configuration and install for optional
packages, assets, models, browsers, or other heavy materials.
- Update docs, discovery, guardrails, tests, and package metadata with behavior
changes.
Constraints
- Do not add
preinstall, install, postinstall, or prepare hooks to the
base CLI package.
- Do not add direct heavy dependencies to
@clawjs/cli for optional
capabilities.
- Do not present all built-in domains as active by default.
- Do not make host, OS permissions, network, downloads, models, audio, or
background services implicit side effects of installation or safe commands.
1---2name: progressive-modularity-review3description: Review Claw/ClawJS changes for zero-surprise install, progressive activation, module modes, optional dependencies, and capability/area visibility.4---56# progressive-modularity-review78Use this skill when a change touches CLI startup, package dependencies,9published package surfaces, setup/configuration, module state, storage10initialization, built-in catalog visibility, host, native permissions, processes,11daemons, launchers, models, browsers, audio, integrations, sync/remote, network,12or sidecars.1314## Procedure15161. Read `CONSTITUTION.md`, ADR 0031, `docs/decision-map.md`, the host17 boundary docs, and `docs/data-storage-boundary.md`.182. Classify the change as a cheap definition, cheap local state, optional19 capability, domain area, heavy dependency, process, permission, network20 action, or external/provider action.213. Ensure safe CLI paths stay quiet: help, inspect, setup preview, modules22 status/list, command discovery, and basic task CRUD must not open apps, start23 persistent processes, request native permissions, download assets/models, or24 call external services.254. Keep technical capabilities separate from human areas. Do not activate niche26 domains through `advanced`.275. Use `enable` for visibility/configuration and `install` for optional28 packages, assets, models, browsers, or other heavy materials.296. Update docs, discovery, guardrails, tests, and package metadata with behavior30 changes.3132## Constraints3334- Do not add `preinstall`, `install`, `postinstall`, or `prepare` hooks to the35 base CLI package.36- Do not add direct heavy dependencies to `@clawjs/cli` for optional37 capabilities.38- Do not present all built-in domains as active by default.39- Do not make host, OS permissions, network, downloads, models, audio, or40 background services implicit side effects of installation or safe commands.
clawic