Menu
Set up a reproducible remote dev environment using sprites with credential-free git sync. Use when user asks to "set up a sprite", "create a remote dev environment", "use sprites", or mentions wanting a reproducible remote environment for a project.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | setup-sprite |
| description | Set up a reproducible remote dev environment using sprites with credential-free git sync. Use when user asks to "set up a sprite", "create a remote dev environment", "use sprites", or mentions wanting a reproducible remote environment for a project. |
Set up and manage a remote dev environment using sprites. All git auth stays local — no credentials on the sprite.
Run these steps in order:
Create the sprite
sprite create <project-name>
Create a bare repo on the sprite
sprite exec -s <name> git init --bare /home/sprite/repos/<name>.git
Start git daemon on the sprite
sprite exec -s <name> git daemon --reuseaddr --base-path=/home/sprite/repos --export-all --enable=receive-pack --port=9418 /home/sprite/repos
Start the proxy (run in background locally)
sprite proxy -s <name> 9418
Push code from local
git push git://localhost:9418/<name>.git <branch>
Clone working copy on the sprite
sprite exec -s <name> git clone /home/sprite/repos/<name>.git /home/sprite/<name>
Install dependencies
sprite exec -s <name> -dir /home/sprite/<name> npm install
Create initial checkpoint
sprite checkpoint create -s <name> --comment "initial setup"
git push git://localhost:9418/<name>.git <branch>git pull git://localhost:9418/<name>.git <branch>sprite exec -s <name> -dir /home/sprite/<name> <command>sprite console -s <name>sprite checkpoint create -s <name> --comment "<description>"sprite restore <checkpoint-id> -s <name>sprite exec treats the entire argument as one command — no semicolons or pipes. Run separate exec calls instead.sprite proxy fails with "address already in use", kill old proxy processes locally: pkill -f "sprite proxy"Lint prose against Simplified Technical English (ASD-STE100) rules. Use when the user asks to check, lint, or simplify technical writing (specs, manuals, procedures, docs) for STE compliance, or mentions ASD-STE100 or Simplified Technical English.
Any time committing, pushing, or creating new revisions is mentioned, use this commit flow.
Step-by-step procedure for building a Claude Code channel integration. Use when creating a new channel plugin that connects Claude Code to external systems via MCP, named pipes, webhooks, or chat platforms.
This skill should be used when the user asks to "set up a dev environment", "create a workspace", "open a browser pane", "split terminal", "spin up frontend and backend", "use cmux", "manage cmux panes", "run commands in cmux", or mentions cmux workspaces, panes, surfaces, or browser automation. Provides workflow guidance for orchestrating multi-pane development environments with terminal and browser surfaces.
Use when merging a stack of stacked PRs with jj. Triggered by phrases like "merge the PR stack", "merge the stacked PRs", "land these PRs", or "merge the stack into main".
Use when addressing PR review comments on stacked jj branches. Triggered by phrases like "address review comments", "fix PR feedback", "respond to review on stacked branch", or "update the PR with reviewer suggestions".