dashboard-hub-onboarding
Made by JeffOne-time setup of a single internal dashboard site (Next.js App Router on Vercel, shadcn/ui, Supabase as a read-only presentation cache) that hosts every dashboard a team builds, gated by an access code from the first deploy, with optional read-only Snowflake panels through fsnow. Use when standing up a dashboards site or hub, onboarding a team to Vercel and Supabase for dashboards, or when someone says "make me a dashboard site".
From Jeffrey's Skills.md: professionally crafted skills for any AI agent, installed and kept in sync by the jsm CLI. Subscription only, $20/month.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
1Updates, enhancements, and release notes for this skill.
New skill: dashboard-hub-onboarding, one gated internal site for every dashboard a team builds
An agent sets up one internal dashboard site with someone who is not a web developer: Next.js on Vercel, shadcn/ui, and Supabase as a read-only cache, with optional live Snowflake panels through fsnow. The access-code gate is in place before the first deploy, a sample dashboard shows the whole pattern working, and every later dashboard is a new route on the same site, built with make-me-a-dashboard.
- The agent interviews first: who owns the accounts (the organization, never a personal account), the hub's name, whether one access code is fine until SSO, and whether Snowflake panels are needed.
- The access-code gate ships with the first deploy. src/proxy.ts checks an httpOnly session cookie in constant time and sends every other request to /enter with a 307.
- After login, next is parsed as a URL and kept only if it stays on the hub, so //evil.example, https://evil.example/ and the same path with a tab after the first slash all land on the hub's index.
- Supabase is a read-only presentation cache. Pages read it as dash_reader, only publish scripts write it as dash_publisher, and each publish replaces its tables in one transaction.
- Every dash_ table revokes anon and authenticated, whatever the project's default grants, so the project's public key can't read the cache through the Data API.
- Optional live Snowflake panels go through the fsnow CLI on a read-only role and a capped warehouse, read curated views only, and are cached for 15 minutes.
- Phase 4 publishes a sample table twice and builds /d/sample with three stat cards, a chart and a table, so the pattern works before any real dashboard exists.
- The hand-off checklist ends with a scan of the built client bundle for the access code, the session token and the database URL.
- Built and run end to end on create-next-app 16.4.5, shadcn CLI 4.23 and postgres.js 4.1, with Postgres 18 standing in for Supabase and an fsnow stand-in for the warehouse.
The skill starts with an interview: who owns the Vercel and Supabase accounts (the organization, never a personal account), the hub's name and domain, whether one long random access code is acceptable until SSO, and whether Snowflake panels are needed. Then come five phases: accounts and CLIs, scaffold and gate, data backends, a sample dashboard, and hand-off.