← ClaudeAtlas

create-dashboardlisted

Create a custom web dashboard (React + Vite + Express) inside your sandbox to visualize the agent's Turso database. The dashboard is served on port 3847 and the user sees it live in the "App" tab in Gooseworks. Use when the user asks for a dashboard, visualization, chart, metric view, or any custom UI powered by their agent's data.
gooseworks-ai/goose-skills · ★ 727 · Web & Frontend · score 82
Install: claude install-skill gooseworks-ai/goose-skills
You are helping the user build a custom dashboard from the Gooseworks dashboard template. The app must run on port 3847 from a single Express process that serves both the API routes and the built React UI so it appears in the Gooseworks App tab. ## Where the source lives (read this first) The **runnable project folder is `/home/user/dashboard`**. That is the ONLY directory you should `cd` into for any npm / build / server command. Most files inside it are symlinks pointing back into the canonical source under the agent's workspace folder (the file you'd see at the canonical path is the same file you'd see through the symlink — it's one file, two paths). The runnable project folder also holds two real local directories that must NOT be on the workspace mount: `node_modules` (dependencies) and `dist` (built bundle). ``` /home/user/dashboard/ ← cd here for everything package.json, package-lock.json, server.js, src/, vite.config.ts, … (symlinks → workspace canonical source) node_modules/, dist/, .vite/, .cache/ (real local dirs — never on workspace) ``` What this means for you: - **Always `cd /home/user/dashboard` before running npm / vite / node / any shell command.** Tools resolve modules from the `node_modules` next to the cwd. Running them from the canonical source path under the workspace folder will install `node_modules` directly into the workspace mount — that puts tens of thousands of files on s3fs, hits its filesystem-semantic