Agent skill
dev-server
Start, stop, restart, check status of, or tail logs for the Fenrir Ledger local dev environment.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/dev-server
SKILL.md
Dev Server — Local Development Environment Manager
Manages all local development services for Fenrir Ledger.
Usage
/dev-server # Show status of all services
/dev-server start # Start all services
/dev-server stop # Stop all services
/dev-server restart # Restart all services
/dev-server <service> start # Start a specific service
/dev-server <service> stop # Stop a specific service
/dev-server <service> logs # Tail a specific service's logs
/dev-server odins-throne start # Start odins-throne-api + odins-throne-ui
/dev-server odins-throne restart # Restart odins-throne-api + odins-throne-ui
Services
| Service | Alias | Port | Description |
|---|---|---|---|
app |
— | 9653 (WOLF) | Next.js dev server via vercel dev |
stripe |
— | — | Stripe CLI webhook forwarding to app |
odins-throne-api |
odins-throne |
3001 | Hono API/WebSocket server (K8s jobs, log streaming) |
odins-throne-ui |
odins-throne |
3002 | Vite React UI (Odin's Throne — Hlidskjalf) |
proxy |
— | 8001 | kubectl proxy for GKE cluster access |
odins-throne is a convenience alias that controls both odins-throne-api and odins-throne-ui together.
Scripts
Each service has its own management script in scripts/:
SCRIPT_DIR="$(git rev-parse --show-toplevel)/.claude/skills/dev-server/scripts"
bash "$SCRIPT_DIR/<service>.sh" <action>
Actions: start, stop, status, logs
Instructions
Parse the command
| Input | Action |
|---|---|
(no args) or status |
Run status on ALL services |
start |
Run start on ALL services |
stop |
Run stop on ALL services |
restart |
Run stop then start on ALL |
odins-throne <action> |
Run <action> on odins-throne-api + odins-throne-ui |
monitor <action> |
Same as odins-throne |
<service> <action> |
Run <action> on that service only |
logs |
Run logs on app (default) |
<service> logs |
Tail that service's log |
Execute
REPO_ROOT=$(git rev-parse --show-toplevel)
SCRIPT_DIR="$REPO_ROOT/.claude/skills/dev-server/scripts"
# Single service
bash "$SCRIPT_DIR/<service>.sh" <action>
# odins-throne (both odins-throne services)
bash "$SCRIPT_DIR/odins-throne-api.sh" <action>
bash "$SCRIPT_DIR/odins-throne-ui.sh" <action>
# All services (start order)
for svc in stripe app odins-throne-api odins-throne-ui proxy; do
bash "$SCRIPT_DIR/$svc.sh" <action>
done
Report
Show a status table after any action:
Service Port Status
─────── ──── ──────
app 9653 running (pid 12345)
stripe — running (pid 12346)
odins-throne 3001 running (pid 12347) ← odins-throne-api
3002 running (pid 12348) ← odins-throne-ui
proxy 8001 not running
Notes
odins-throne-apirequirestsx(runsdevelopment/odins-throne/viatsx watch)odins-throne-uirequiresvite(runsdevelopment/odins-throne-ui/Vite dev server with HMR)proxyrequireskubectlconfigured for the GKE clusterstriperequires Stripe CLI (brew install stripe/stripe-cli/stripe)- Open http://localhost:3002/ for the UI (Vite proxies API/WS to odins-throne-api on 3001)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?