dev-servers
Start the backend (FastAPI/uvicorn) and frontend (Vite) development servers. Use when user mentions "start dev", "run servers", "launch app", "start the app", or needs to run the application locally.
When & Why to Use This Skill
The dev-servers skill automates the initialization and management of local full-stack development environments. It streamlines the workflow by handling dependency checks, installing missing packages for FastAPI (Python) and Vite (Node.js), and launching backend and frontend servers simultaneously, ensuring a seamless transition from coding to testing.
Use Cases
- Rapidly launch a full-stack application by automating the startup of both FastAPI backend and Vite frontend servers with a single prompt.
- Automate the setup of new development environments by detecting missing dependencies and executing 'pip install' or 'npm install' automatically.
- Ensure local environment readiness by verifying .env configurations and port availability before starting services to prevent common runtime errors.
- Streamline the local debugging process by running development servers in the background with hot-reloading enabled for immediate feedback.
| name | dev-servers |
|---|---|
| description | Start the backend (FastAPI/uvicorn) and frontend (Vite) development servers. Use when user mentions "start dev", "run servers", "launch app", "start the app", or needs to run the application locally. |
| allowed-tools | Bash |
Development Servers
Instructions
Check if dependencies are installed:
- Backend: Look for
backend/venv/or ask user about Python environment - Frontend: Check if
frontend/node_modules/exists
- Backend: Look for
Install dependencies if missing:
- Backend:
cd backend && pip install -r requirements.txt - Frontend:
cd frontend && npm install
- Backend:
Start servers (recommend running in separate terminals or background):
- Backend:
cd backend && uvicorn main:app --reload(runs on http://localhost:8000) - Frontend:
cd frontend && npm run dev(runs on http://localhost:5173)
- Backend:
Verify
.envfile exists inbackend/withOPENAI_API_KEYset
Examples
- "Start the dev servers"
- "Run the app locally"
- "Launch backend and frontend"
Guardrails
- Never expose or log the OPENAI_API_KEY
- Confirm with user before installing dependencies
- Warn if ports 8000 or 5173 are already in use