From monday-code
Starts Vite frontend dev server on port 3000, Express backend on 8080 with watch mode, and local MongoDB via Docker for monday code apps. Installs deps, checks .env.
How this skill is triggered — by the user, by Claude, or both
Slash command
/monday-code:monday-code-devThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Start development servers and set up the local environment for monday code apps.
Start development servers and set up the local environment for monday code apps.
Check which directories exist:
ls -d frontend/ backend/ 2>/dev/null
frontend/ exists → Frontend appbackend/ exists → Backend appCheck dependencies are installed:
# Frontend
[ -d "frontend/node_modules" ] || (cd frontend && npm install)
# Backend
[ -d "backend/node_modules" ] || (cd backend && npm install)
Check environment files:
For backend, verify .env exists. If not, check for .env.example:
[ -f "backend/.env" ] || echo "WARNING: No .env file found in backend/"
Required backend env vars:
MONDAY_CLIENT_SECRET - For JWT verification (set in Developer Center > OAuth)MNDY_MONGODB_CONNECTION_STRING - For Document DB (local: mongodb://localhost:27017/appname)Check if the backend uses MongoDB:
grep -r "MNDY_MONGODB_CONNECTION_STRING\|mongodb\|MongoClient" backend/src/ 2>/dev/null
If it does, ensure a local MongoDB is running:
# Check if MongoDB is already running
docker ps --filter name=monday-app-mongo --format "{{.Names}}" 2>/dev/null
# If not running, start one:
docker run -d --name monday-app-mongo -p 27017:27017 mongo:7
Set in backend/.env:
MNDY_MONGODB_CONNECTION_STRING=mongodb://localhost:27017/monday-app
Frontend only:
cd frontend && npm run dev
Starts Vite on port 3000 with HMR. Access at http://localhost:3000.
Backend only:
cd backend && npm run dev
Starts Express with tsx watch mode on port 8080 (or PORT env var). Auto-reloads on file changes.
Fullstack (both servers):
Run each in a separate background process:
# Start backend first (frontend may depend on it)
cd backend && npm run dev &
# Then frontend
cd frontend && npm run dev
Or suggest the user to open two terminal tabs.
The frontend MondayContext should auto-detect local development. It works by checking:
const isLocalDev =
!window.location.ancestorOrigins?.length && // Not inside monday.com iframe
import.meta.env.DEV; // Vite dev mode
When in local dev mode:
VITE_DEV_TOKEN for authenticationTo test the app inside monday.com, you will need to create the app and the desired app feature in the monday.com Developer Center. You can use the local dev server for the frontend and a tunnel for the backend.
If building a backend for automations/integrations on monday.com production with real monday.com webhooks/integrations, the user needs a tunnel:
# Using ngrok (or similar)
mapps tunnel:create -p 8080
Then set the tunnel URL in monday.com Developer Center go to: Your app > Features > your app feature > Deployment > External hosting
And put in the fielsd the tunnel URL (e.g. https://548f50475f79.apps-tunnel.monday.app)
For frontend testing inside monday.com:
| Problem | Solution |
|---|---|
| Port 3000/8080 already in use | Kill the existing process: lsof -ti:3000 | xargs kill or change the port |
node_modules missing | Run npm install in the relevant directory |
| Docker not running (MongoDB) | Start Docker Desktop, then re-run the docker run command |
.env file missing | Copy from .env.example if available, or create manually with required vars |
MONDAY_CLIENT_SECRET not set | Get it from Developer Center > Your App > OAuth and add to backend/.env |
| Frontend shows blank page | Check browser console; ensure Vite dev server is running on port 3000 |
User says: "Start the dev server for my fullstack app"
Actions:
frontend/ and backend/ directories exist (fullstack)npm install in both if node_modules missingcd backend && npm run devcd frontend && npm run devResult: Backend running on http://localhost:8080, frontend on http://localhost:3000 with HMR
npx claudepluginhub mondaycom/agentic-monday --plugin monday-codeConfigures Replit dev workflow: .replit run commands, hot reload for Node/Python/Vite, Webview ports, dev/prod DBs, Replit Agent.
Orchestrates end-to-end development workflows bundling skills for web, mobile, full-stack, and backend applications from project scaffolding to deployment.
Guides deploying Deno apps to Deno Deploy using `deno deploy` CLI, covering workflows, environment variables, KV database, custom domains, and --tunnel flag.