Manage the development server lifecycle. Use when starting, stopping, restarting the dev server, checking server status, viewing server logs, or before testing changes that require a running server.
This skill manages the development server for this Next.js/PayloadCMS project. It ensures a single server instance is shared across all Claude Code sessions.
# Default: Start server (if needed) + show 100 lines + tail logs
.claude/skills/dev-server/dev-server.sh
| Command | Description |
|---|---|
| (none) | Default: Start if needed, show last 100 lines, tail logs |
start | Start server if not running |
stop | Stop server gracefully |
restart | Stop and start server |
status |
| Show server status and health |
logs [N] | Show last N lines (default 100) and tail |
health | Quick health check |
# Default - most common usage
.claude/skills/dev-server/dev-server.sh
# Start without tailing logs
.claude/skills/dev-server/dev-server.sh start
# Check if server is running and healthy
.claude/skills/dev-server/dev-server.sh status
# View logs only
.claude/skills/dev-server/dev-server.sh logs
# Restart after config changes
.claude/skills/dev-server/dev-server.sh restart
# Stop when done
.claude/skills/dev-server/dev-server.sh stop
pnpm devsafe (cleans .next before starting)/api/managers/me endpoint.claude/skills/dev-server/state/server.logOnce running:
The skill uses PID-based state tracking to ensure a single server across all Claude instances:
logs command)restart command)restart command)