From zerobased
Rewrite-state reference for zerobased. The repo is moving to an explicit machine-local control plane with traced-TDD failure ownership.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zerobased:zerobasedThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The legacy zero-config Docker autodiscovery router is not the target architecture.
The legacy zero-config Docker autodiscovery router is not the target architecture.
Do not use this skill as a CLI reference for the old behavior. The accepted product direction is:
zerobased start starts that control planezerobased up starts an explicitly declared stack through that control planeCurrent source of truth:
docs/superpowers/specs/2026-05-13-zerobased-control-plane-rfc.mdLegacy behavior that must not be reintroduced by default:
zerobased runBefore making changes:
npx claudepluginhub lagz0ne/zerobased --plugin zerobasedCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.