Make it yours
npx shadcn@latest add https://elabs-ai.com/r/project-hub-page.jsonPaste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.
Add the brand-ui template "Project Hub" (project-hub-page) to this project — a whole screen copied into the app, built from registry blocks and the @elabs-ai/components-* packages. A product team runs projects, an issue board, team load and members as one product. Every view reads the same issues, so a move on the board changes the load, the overview and the navigation counts. 1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`. 2. Make sure the base is in place: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui`), then the packages the template imports: @elabs-ai/components-charts, @elabs-ai/components-tokens, @elabs-ai/components-ui. If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`. 3. Copy the template in with `npx shadcn@latest add https://elabs-ai.com/r/project-hub-page.json` — it brings its blocks with it (kanban-board-01, project-cards-01, settings-members-01, workspace-shell); if that url does not answer, copy the folders from https://github.com/mreimitz/elabs-components/tree/main/registry/blocks instead. 4. Mount the page at a route, keep its `WorkspaceShell` frame, and replace the seeded data with ours: [the route, the real data source, and what should change from the template] 5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop. 6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.
What each view shows
The screens the navigation names, one line each.
- Overview
- Projects and their state at a glance.
- Projects
- Project cards with progress and owners.
- Issues
- The board — drag an issue between columns.
- Team load
- Who holds how much, from the same issues.
- Members
- The team and their roles.
Try it on the screen above: Move an issue on the board and watch the team load, the overview and the navigation counts follow; the dock explains the project or issue last opened.
What it is made of
The blocks and packages the template composes — each has its own page. Copy the template and you copy the blocks with it.
4 blocks
Drag cards between columns or use each card's Move menu (keyboard, screen reader and touch), with a live-region announcement, per-column points and WIP-limit warnings in words.
Projects as cards with progress against time on one Meter (marker = today), a derived health word, team avatars, due date and a counted state filter.
Members with in-place role changes, a protected owner, an invite dialog that checks address, duplicates and seats, pending invites in the same list and a confirming remove.
Examples
Issues
Opened on the issue board.
Team Load
Opened on the team's load.
Overview
Opened on the overview.