← backCoding & DashboardsFounding · Free forever

Build a lightweight internal dashboard

Start with static HTML for internal tools — Next.js is overkill for a 1-user dashboard.

by @whitney · recommended tool Claude Code · 0 unlocks

You'll need

CLAUDE SKILLS

init

CONNECTORS

GitHub

EXAMPLES · WHAT THIS PROMPT PRODUCES

Sample output

**Build complete — Support Ticket Health Dashboard**

Stack: static HTML + vanilla JS + Chart.js (CDN). No build step. Data source: `tickets.csv` (Zendesk export). Auth: Basic (single shared password via prompt — fine for an internal 1-team tool).

**Views shipped:**
1. **Overview** — open vs. resolved (last 30 days), median first-response time, CSAT gauge, backlog count.
2. **By Agent** — tickets handled, avg resolution time, reopen rate (sortable table).
3. **By Category** — bar chart of volume by tag, with week-over-week delta arrows.
4. **SLA Breaches** — red-flagged list of tickets past their response window.

**Run it:**
```
python3 -m http.server 8080
```
Then open `http://localhost:8080`. Drop a fresh `tickets.csv` next to `index.html` and refresh — no rebuild needed.

**README includes:** expected CSV column schema (ticket_id, agent, category, created_at, resolved_at, csat), how to change the SLA threshold (one constant at top of `app.js`), and how to swap the password.

Note: I kept it static intentionally — for one team checking it on a laptop, Next.js would've added a build pipeline you'd have to maintain for zero benefit.

PRICE HISTORY0 cr · current

PROMPT TEMPLATE · v1.0.0

Build an internal dashboard for <PURPOSE>.
Data source: <DB/API/CSV>. Tech: <REACT+SHADCN / NEXT.JS / STATIC_HTML>.
Views: <LIST>. Auth: <NONE/BASIC/SSO>.
Make it runnable locally in one command. Include a README.