What problem does it solve? Developing and running a local Paperclip instance involves many moving parts — servers, databases, git worktrees, migrations, and PR conventions — and improvising around CLI failures can corrupt data or break isolation. This Skill provides the canonical operational playbook so agents and developers run every task through the supported paperclipai CLI instead of risky manual workarounds. ## Core Features & Use Cases - Instance Lifecycle Management: Start, stop, build, test, migrate, back up, and health-check a local Paperclip server using commands like npx paperclipai run and npx paperclipai doctor --repair. - Isolated Worktrees: Create and manage git worktrees, each with its own database, port, and environment, for parallel feature development without cross-contamination. - Fork & PR Workflow: Detect user forks, push feature branches to the correct remote, and create pull requests that strictly follow the required template sections and CI checks. - Persistent Dev Servers: Launch long-lived dev servers in detached tmux sessions so they survive agent heartbeats for manual QA testing. - Use Case: An agent needs to fix a bug on a feature branch: it creates a worktree with worktree:make, sources the environment, starts an isolated server in tmux, verifies the health endpoint, and later opens a compliant PR from the user's fork. ## Quick Start Ask the agent to read doc/DEVELOPING.md and then start a local Paperclip dev server in an isolated worktree for your feature branch.
