local-dev-server
Start and manage local development servers
Address already in use errors and server crashes disrupt development workflow. This skill provides PM2 commands to start, stop, and restart local development servers with auto-recovery and centralized logging.
Télécharger le ZIP du skill
Importer dans Claude
Allez dans Paramètres → Capacités → Skills → Importer un skill
Activez et commencez à utiliser
Tester
Utilisation de "local-dev-server". Start the local development server
Résultat attendu:
- Starting Empathy Ledger server with PM2...
- ✓ Server started: empathy-ledger-solo (PID: 12345)
- ✓ Running on port 3030
- ✓ Auto-restart enabled
- View logs: pm2 logs empathy-ledger-solo
Utilisation de "local-dev-server". Port 3030 is busy. Kill the existing process and restart the server.
Résultat attendu:
- Finding process on port 3030...
- Killing process (PID: 67890)
- Starting server with PM2...
- ✓ Server started successfully on port 3030
- ✓ Auto-recovery enabled
Utilisation de "local-dev-server". Start all ACT ecosystem projects
Résultat attendu:
- Starting ACT Regenerative Studio on port 3002...
- Starting Empathy Ledger on port 3001...
- Starting JusticeHub on port 3003...
- Starting The Harvest Website on port 3004...
- Starting ACT Farm on port 3005...
- Starting ACT Placemat on port 3999...
- ✓ All 6 projects running
Audit de sécurité
SûrThis is a pure documentation skill containing only markdown documentation. No executable code exists. All 154 static findings are false positives: the scanner misidentified SHA-256 hashes as weak crypto/C2 keywords, markdown code blocks as Ruby backticks, and legitimate PM2/lsof/xargs commands as dangerous external commands. This skill only provides guidance for using standard development tools.
Facteurs de risque
🌐 Accès réseau (3)
📁 Accès au système de fichiers (7)
⚙️ Commandes externes (132)
Score de qualité
Ce que vous pouvez construire
Start multiple projects
Start all ACT ecosystem projects with a single command for comprehensive local development environment
Fix port conflicts
Resolve address already in use errors by killing processes and restarting servers cleanly
Monitor server health
View centralized logs and auto-restart crashed servers to maintain development continuity
Essayez ces prompts
Start the local development server for Empathy Ledger
Port 3030 is busy. Kill the existing process and restart the server.
I updated the schema. Restart the dev server to pick up the changes.
Start all ACT ecosystem projects so I can work on the full platform.
Bonnes pratiques
- Use ecosystem script to start all projects for consistent environment
- Check server status with pm2 list before running tests
- Save PM2 process list with pm2 save for session persistence
Éviter
- Using npm run dev directly for production-like testing
- Ignoring repeated server crashes without checking error logs
- Leaving servers running overnight without pm2 save
Foire aux questions
How do I stop the server?
What ports does this skill use?
Does this work on Linux?
Is my data safe with PM2?
Why does my server keep crashing?
How is this different from npm run dev?
Détails du développeur
Auteur
AcurioustractorLicence
MIT
Dépôt
https://github.com/Acurioustractor/empathy-ledger-v2/tree/main/.claude/skills/local/local-dev-serverRéf
main
Structure de fichiers
📄 SKILL.md