Claude Code setup
Install Pocketto as a Claude Code plugin from the marketplace, run its skills as /pocketto: commands, configure CLAUDE.md memory, and fix setup problems.
Pocketto distributes for Claude Code as a plugin through a marketplace manifest in the Pocketto repository.
Install
/plugin marketplace add rfxlamia/pocketto
/plugin install pocketto@pocketto
/reload-pluginsAfter /reload-plugins, every skill is available as a /pocketto:* command, for example /pocketto:pocket-grinding, /pocketto:bug-hunting, /pocketto:pocket-closing <plan_dir>.
First command
Run /pocketto:pocket-help, a compact router that explains the system and which skill to use without loading every skill into context.
The memory file: CLAUDE.md
Claude Code reads CLAUDE.md as project memory. Two Pocketto features write to it:
- pocket-init generates a project guide (stack, verified build/test/lint commands, layout, conventions) inside a managed section delimited by
<!-- pocket-init:start -->and<!-- pocket-init:end -->. Only that section is ever rewritten; your own content around it is untouched. - Pocket Education stores a learner profile in a
## Pocket Educationblock outside the managed section. Regenerating the project guide never resets calibration.
No extension setup is required on Claude Code: the review-gate, library-docs, and subagent capabilities that Pi loads as extensions come from the host itself.
Claude Code vs Pi
| Claude Code | Pi | |
|---|---|---|
| Install | /plugin marketplace add + /plugin install | pi install git:… or pi install npm:pocketto-pi |
| Invocation | /pocketto:<skill> commands | Trigger phrases and skill names |
| Extensions | Host capabilities | npx pocketto-pi setup-extensions |
| Memory file | CLAUDE.md | AGENTS.md |
| Enterprise role | claude/enterprise | pi/enterprise |
Troubleshooting
- Commands missing after install: run
/reload-plugins. The marketplace entry tracks the repository, so a re-run of/plugin install pocketto@pockettorefreshes it. - CLI errors mentioning a contract: the skills and the CLI handshake on a version (
--contract 3). If they disagree, update the plugin or pin the CLI as the error message instructs; see Compatibility. - Mid-plan updates: if a plan is in flight, finish or close it before updating; pipeline markers refuse older plans rather than corrupting state. See the FAQ.
Related documentation
- Installation: both hosts side by side
- Quickstart
- Core & Enterprise: adding GitHub synchronization later