Build custom monitoring dashboard
create-dashboardskillsetup L3★679
gooseworks-ai/goose-skills ↗What it does
Build custom dashboard from Express + React + Tailwind template
Best for
Assembling a quick real-time monitoring dashboard that reads from an agent's database when one exists — not for complex multi-database UX or heavy interactivity.
Inputs
- · User requirements (what to visualize)
- · Agent database (if available, read-only real data preferred over mocks)
- · Custom styling preferences (Tailwind utilities)
Outputs
- · Runnable Express app on port 3847
- · Single process serving API + built React UI
- · React components with Tailwind styling
- · API routes (endpoints for data)
Requires
- · Express.js (server)
- · React + Vite (frontend build)
- · Tailwind CSS (styling)
- · Agent database (optional, Turso/SQLite read-only)
Preconditions
- · Must work from /home/user/dashboard (symlinked workspace structure)
- · Cannot run npm from workspace canonical path — only from /home/user/dashboard
- · node_modules and dist are local-only — never copy to workspace
Failure modes
- · Breaks if npm/vite/node run from workspace canonical path instead of /home/user/dashboard (pollutes workspace with node_modules)
- · State loss if symlink structure is missing (must ask platform to re-run setup)
- · Fails if using framework other than React + Vite + Tailwind (not supported)
- · Mock data silently hides real database availability — always check agent database first
Trust signals
- · Explicit symlink architecture documented (/home/user/dashboard → workspace)
- · Four non-negotiable constraints (template workflow, literal /home/user/dashboard path, npm from dashboard dir only, no node_modules in workspace)
- · State decision flow (check symlinks, check node_modules, check port 3847 health)
- · Platform start orchestrator handles symlink setup + npm install + build + launch automatically
- · Discovery rule: always check agent database for real data before using mocks