What problem does it solve? Adding a new department dashboard to the Shogun OS web portal requires coordinated changes across the FastAPI backend, TypeScript types, API client, and React components, and doing it inconsistently breaks the established CRM dashboard pattern. ## Core Features & Use Cases - Six-step workflow: Guides agents through backend aggregation endpoints, TypeScript types, API methods, React sub-tab components, and DashboardViewer registration. - Design conventions: Enforces shared chart wrappers, design tokens, color palette utilities, table patterns, and empty states so every department dashboard looks consistent. - Verification checklist: Includes TypeScript compilation, Vite build, Python syntax validation, and commit message conventions. - Use Case: A user asks to add a marketing dashboard; the agent follows the workflow to produce a /department/marketing?tab=dashboard page with Overview, Leads, and Analytics sub-tabs backed by gbrain data. ## Quick Start Ask the agent to add a marketing dashboard to the Shogun OS web portal following the CRM dashboard pattern.