plugins/lisa-expo-copilot/skills/ops-run-local/SKILL.md
Manage the local development environment for Expo + serverless backend projects. Supports start, stop, restart, and status for the full stack or individual services.
npx skillsauth add codyswanngt/lisa ops-run-localInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage the local development environment.
Argument: $ARGUMENTS — start, stop, restart, status, start-frontend, start-backend (default: start)
.)${BACKEND_DIR:-../backend-v2} — set BACKEND_DIR in .claude/settings.local.json if your backend is elsewhereBACKEND_DIR="${BACKEND_DIR:-../backend-v2}"
test -d "$BACKEND_DIR" && echo "Backend dir OK: $BACKEND_DIR" || echo "ERROR: Backend dir not found at $BACKEND_DIR — set BACKEND_DIR"
lsof -i :8081 2>/dev/null | grep LISTEN
lsof -i :3000 2>/dev/null | grep LISTEN
which bun && bun --version
Read the frontend package.json to find available start scripts (e.g., start:local, start:dev, start:staging). Read the backend package.json to find backend start scripts (e.g., start:local, start:dev).
Start both backend and frontend for local development.
Start backend (background):
cd "${BACKEND_DIR:-../backend-v2}" && IS_OFFLINE=true bun run start:local
Run this in the background using the Bash tool with run_in_background: true.
Wait for backend (up to 30 seconds):
for i in $(seq 1 30); do
curl -sf http://localhost:3000/graphql -X POST \
-H "Content-Type: application/json" \
-d '{"query":"{ __typename }"}' > /dev/null 2>&1 && echo "Backend ready" && break
sleep 1
done
Start frontend (background):
bun run start:local
Run this in the background using the Bash tool with run_in_background: true.
Verify frontend (up to 60 seconds — Metro bundler can be slow):
for i in $(seq 1 60); do
curl -sf http://localhost:8081 > /dev/null 2>&1 && echo "Frontend ready" && break
sleep 1
done
Report status table.
Use when the backend is already deployed and you only need the frontend.
bun run start:dev
Run in background.
Verify:
for i in $(seq 1 60); do
curl -sf http://localhost:8081 > /dev/null 2>&1 && echo "Frontend ready" && break
sleep 1
done
Check AWS credentials (discover profile from backend package.json scripts or remote-routine
~/.aws/config):
aws sts get-caller-identity --profile {aws-profile} 2>/dev/null
If this is an interactive local session and credentials are expired, refresh the backend's local AWS signin flow. In headless sessions, rely on the configured environment-backed AWS profile and do not start an SSO browser/device flow.
Start:
cd "${BACKEND_DIR:-../backend-v2}" && IS_OFFLINE=true bun run start:local
Run in background.
Verify:
for i in $(seq 1 30); do
curl -sf http://localhost:3000/graphql -X POST \
-H "Content-Type: application/json" \
-d '{"query":"{ __typename }"}' > /dev/null 2>&1 && echo "Backend ready" && break
sleep 1
done
Kill all local services.
# Kill frontend (Metro bundler)
lsof -ti :8081 | xargs kill -9 2>/dev/null || echo "No frontend process on :8081"
# Kill backend (Serverless Offline)
lsof -ti :3000 | xargs kill -9 2>/dev/null || echo "No backend process on :3000"
# Stop Docker if running
cd "${BACKEND_DIR:-../backend-v2}" && docker compose down 2>/dev/null || true
sleep 2Check what is currently running and responsive.
echo "=== Port Check ==="
echo -n "Frontend :8081 — "; lsof -i :8081 2>/dev/null | grep LISTEN > /dev/null && echo "LISTENING" || echo "NOT LISTENING"
echo -n "Backend :3000 — "; lsof -i :3000 2>/dev/null | grep LISTEN > /dev/null && echo "LISTENING" || echo "NOT LISTENING"
echo ""
echo "=== Health Check ==="
echo -n "Frontend :8081 — "; curl -sf -o /dev/null -w "%{http_code}" http://localhost:8081 2>/dev/null || echo "UNREACHABLE"
echo -n "Backend :3000 — "; curl -sf -o /dev/null -w "%{http_code}" http://localhost:3000/graphql -X POST -H "Content-Type: application/json" -d '{"query":"{ __typename }"}' 2>/dev/null || echo "UNREACHABLE"
echo ""
echo "=== Docker ==="
docker compose -f "${BACKEND_DIR:-../backend-v2}/compose.yaml" ps 2>/dev/null || echo "No Docker services running"
Report results as a table:
| Service | Port | Listening | Responsive | |---------|------|-----------|------------| | Frontend (Metro) | 8081 | YES/NO | YES/NO | | Backend (Serverless Offline) | 3000 | YES/NO | YES/NO |
development
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
tools
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
tools
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
tools
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.