Project Dashboard

[OVERVIEW] Build a customizable, shareable multi-project or multi-account status dashboard Artifact — letting the user define their own accounts/projects, role-based section visibility, MCP connector data sources, and custom keywords/non-MCP inputs. [TRYABLE] 1. Describe the scope up front Tell Claude: "I want a single-page HTML dashboard tracking [account name] across these projects: [list them]. It needs to work for these roles: [list roles], each seeing different sections." 2. Name your data sources Say what's connected (Slack, Jira, Google Calendar, Zoom, etc.) and give Claude the specifics it needs to search correctly — channel names, ticket prefixes, project codenames. Without this, Claude can't tag anything to the right project. 3. Specify what "sections" you want List the actual tiles: task list, today's meetings, health scorecard, stakeholder pulse, hidden patterns, whatever matters to you. Otherwise Claude guesses generically. 4. Say explicitly you want it built as a shareable artifact/page, not just a text summary — so it asks Claude to publish an HTML file rather than paste a report in chat. 5. Ask for role-based filtering to be functional, not decorative — i.e., "when I click 'Exec view,' actually hide sections, don't just relabel them." 6. Tell it to mark unverified data as placeholders rather than inventing numbers — this keeps the scorecard/patterns honest instead of hallucinated. 7. Review and iterate — ask for adjustments to role visibility, color coding, or metrics once you see the first draft. [SETUP] Claude, Gmail, Gdrive, MCP, Zoom, Slack, Confluence, JIRA [IMPACT] What it does: One shareable dashboard pulling tasks, meetings, health scores, and patterns across your multiple projects, with role-based views (exec sees less, PM sees everything, Architect, etc.). Connects to different tools like Slack, Jira/Confluence, Calendar, Zoom, etc. Time saved: Cuts the manual work of compiling a weekly status update from five tabs into one query-based build. Quality gains: Consistent scorecard/fields across all projects, systematic search instead of "did I check that channel," and clear real-vs-placeholder data tagging. [LESSONS] Before building this dashboard, consider the following requirements: - Need real-time alerting. - Require two-way task management. - Data resides in tools without a connector or exportable format.