원클릭으로
run-slateflow
Build and run SlateFlow — self-hosted project management platform with Kanban, sprints, roadmap, and reporting
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Build and run SlateFlow — self-hosted project management platform with Kanban, sprints, roadmap, and reporting
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Run deep browser UI tests against the admin panels (global and project-level) using MCP Playwright.
Run deep browser UI tests against the SlateFlow Kanban board using MCP Playwright — covers board load, card CRUD, DnD lane transitions, card modal tabs, task checklists, filters, and lane management.
Run interactive browser UI tests against the running SlateFlow dev server using MCP Playwright.
Create a GitHub issue from a bug or problem description found during testing.
Audit recent changes and verify that README.md, ROADMAP.md, and CLAUDE.md were all updated.
Reset and re-seed slateflow.db with realistic test data for local dev and demos.
SOC 직업 분류 기준
| name | run-slateflow |
| description | Build and run SlateFlow — self-hosted project management platform with Kanban, sprints, roadmap, and reporting |
SlateFlow is a self-hosted, single-container project management platform. The dev setup runs a concurrent React frontend (:5173 or :5174 on busy systems) and Hono backend API server (:3000). This skill builds, launches, and tests the app.
Prerequisites:
Build & Launch (Development):
cd c:/repo/slateFlow
npm install
npm run dev
This spawns:
http://localhost:3000http://localhost:5173 (or :5174 if 5173 is busy)server/slateflow.db (auto-created)The server logs appear in the terminal; frontend logs are in the browser console.
The driver (driver.mjs) runs quick smoke tests to verify the app is up and responsive:
node .claude/skills/run-slateflow/driver.mjs
This checks:
/api/config endpoint (config & feature flags)<div id="root">)POST /api/auth/login) with default admin credentialsGET /api/projects — auth required)All four must pass (exit 0).
Default Login:
admin@flow.localAdmin1234!This user is pre-seeded on first boot as a super_admin (can see all projects, manage users, toggle feature flags).
Once npm run dev is running, test the API:
# Check feature flags
curl http://localhost:3000/api/config | grep features
# Login
curl -X POST http://localhost:3000/api/auth/login \
-H "Content-Type: application/json" \
-d '{"email":"admin@flow.local","password":"Admin1234!"}'
# Fetch projects (requires auth cookie from login above)
curl http://localhost:3000/api/projects \
-b cookies.txt # httpOnly cookie from login response
Navigate to http://localhost:5173 (or :5174) in any browser. You will see:
Click around to verify:
No test suite is currently configured. The smoke test driver above covers the main API surface.
npm run build
docker-compose up -d # builds and runs single container on :3000
Production builds serve the static React bundle from the Hono server (no separate frontend port).
server/slateflow.db. Delete it to reset to defaults on next run.FEATURE_AI, FEATURE_CALENDAR, etc.). Defaults are in .env.example; copy to .env and toggle as needed.sf_token, 7-day TTL). Browser testing works seamlessly; API testing via curl requires passing cookies back.| Symptom | Fix |
|---|---|
Port 3000 already in use | lsof -i :3000 (Linux/macOS) or netstat -ano | findstr :3000 (Windows); kill the process or set PORT=3001 in .env |
Cannot find module '@slateflow/...' | npm install didn't run; try npm install --force |
| Frontend shows blank page | Check browser console (F12) for errors; server logs should show API requests. If 404s, frontend port is wrong — check dev log for actual port |
ERR_INVALID_DB_PATH | Database parent dir doesn't exist; mkdir -p server/ or set DATABASE_PATH in .env to a valid path |
| Login fails with "user not found" | Default user only exists on first boot (initial DB creation). Check server/slateflow.db exists; if not, delete and restart. |
EADDRINUSE on :5173 | Another process is using the port. Either kill it or Vite will auto-pick :5174. Check the dev log. |