Claude Sync
pocketd [module] [command] [arguments] [flags]
Explain complex operations as step-by-step procedures, and always include expected output format or success indicators when available.
For configuration-based commands, explain the required format of config files and provide simplified examples of valid configurations.
Base your answers on the detailed code in the Pocket Network codebase, particularly the CLI command implementations in the module directories and the root command structure.
Resources
Claude Sync: https://dev.poktroll.com/develop/developer_guide/claudesync#claude-sync-
Table of Contents: https://dev.poktroll.com/develop/developer_guide/claudesync#table-of-contents-
Benefits: https://dev.poktroll.com/develop/developer_guide/claudesync#benefits
Getting Started: https://dev.poktroll.com/develop/developer_guide/claudesync#getting-started
Installation: https://dev.poktroll.com/develop/developer_guide/claudesync#installation
Authentication: https://dev.poktroll.com/develop/developer_guide/claudesync#authentication
ClaudeSync Projects and Actions: https://dev.poktroll.com/develop/developer_guide/claudesync#claudesync-projects-and-actions
Available Commands: https://dev.poktroll.com/develop/developer_guide/claudesync#available-commands
Ignoring Files: https://dev.poktroll.com/develop/developer_guide/claudesync#ignoring-files
Support
.claudeignorefiles: https://dev.poktroll.com/develop/developer_guide/claudesync#support-claudeignore-files
System Prompt: https://dev.poktroll.com/develop/developer_guide/claudesync#system-prompt
Pocket Documentation System Prompt: https://dev.poktroll.com/develop/developer_guide/claudesync#pocket-documentation-system-prompt
Pocket CLI System Prompt: https://dev.poktroll.com/develop/developer_guide/claudesync#pocket-cli-system-prompt
Usage guidance
Keep the CLI top-level usage in mind: pocketd [module] [command] [arguments] [flags]
When explaining any complex operation derived from Pocket Network CLI code:
Provide a step-by-step procedure.
Include expected output format or concrete success indicators if present in the implementation (for example, a success message, an exit code, or a JSON structure).
For commands that rely on configuration files, show the required format and include a minimal valid example.
Getting started (high-level steps)
Installation
Follow the installation instructions in the Getting Started → Installation section: https://dev.poktroll.com/develop/developer_guide/claudesync#installation
Step-by-step: see the linked Installation docs for concrete commands and platform-specific steps.
Expected outcome: your environment has the claudesync tooling/install artifacts available on PATH or otherwise ready to run (the specific messages or files produced are described in the Installation doc).
Authentication
Follow the Authentication instructions: https://dev.poktroll.com/develop/developer_guide/claudesync#authentication
Step-by-step: complete any authentication flow described in the linked doc (API key, OAuth, or other credential steps).
Expected outcome: the tool reports successful authentication or creates a credentials/config file as described in the linked documentation.
ClaudeSync Projects and Actions
Read "ClaudeSync Projects and Actions" to learn how to create and run projects: https://dev.poktroll.com/develop/developer_guide/claudesync#claudesync-projects-and-actions
Step-by-step: create a project, configure actions, and run them as described.
Expected outcome: actions execute and produce outputs described in the linked documentation (logs, generated artifacts, or CLI success messages).
Available commands
See the full list and details: https://dev.poktroll.com/develop/developer_guide/claudesync#available-commands
Ignoring files
High-level: .claudeignore support and behavior:
Main docs: https://dev.poktroll.com/develop/developer_guide/claudesync#ignoring-files
Support for
.claudeignorefiles: https://dev.poktroll.com/develop/developer_guide/claudesync#support-claudeignore-files
System prompt and presets
Main doc: https://dev.poktroll.com/develop/developer_guide/claudesync#system-prompt
How to document pocketd commands (guidelines)
For each command implementation (inspect the code under the module directories and root command):
Describe the command signature (module, command, arguments, flags).
Provide a step-by-step procedure for complex/compound operations (use a stepper for multi-step flows).
Show expected outputs or success indicators verbatim when available (copy exact messages or sample JSON output from the implementation).
For configuration-based commands:
Show the exact required format (keys, types, any required fields).
Provide a minimal, valid example configuration file block.
Preserve any links or URLs exactly (do not alter query parameters).
If the original doc contains FAQs, convert them into expandable blocks (details).
Example structure for a pocketd command doc page
Title: pocketd
Short description
Syntax: pocketd [module] [command] [args] [flags]
Stepper: step-by-step usage
Config example (if applicable): code block with minimal valid content
Expected output: code block showing success JSON or CLI confirmation
Errors and troubleshooting: list of common errors (copy exact error strings from code where possible)
Links and references: keep exact URLs to relevant source files or docs
Notes
Do not add information not present in the original code or docs.
Keep all original links and URLs intact.
Convert numbered multi-step lists into stepper blocks (remove numeric prefixes).
Convert any package-manager-specific install blocks (npm, yarn, pnpm) into tabs (one tab per package manager) if present in the source.
Convert FAQ sections into expandables.
If you want, provide a specific pocketd command (module + command) and I will generate the GitBook-optimized markdown for that command based on the code and docs you point me to.
Was this helpful?