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 aws:signin:* scripts):
aws sts get-caller-identity --profile {aws-profile} 2>/dev/null
If expired, run the backend's aws:signin:{env} script.
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 |
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and