Now let me check what UI components are available and start building the system.

Now I have everything I need. Let me start building this comprehensive system. I'll begin with the globals.css theme update, localStorage data layer, layout, and all the core modules.

Now let me build the localStorage data layer and all core components:

Now let me build all the components and pages:

Now let me create the layout and all the pages:

Now create all the page files:

Now update the tailwind config for our custom fonts:

The complete ResQ Emergency Response Coordination System is now built with all six core modules. Here's what was created:

1. Dashboard (/) - Overview with stat cards for total ambulances, pending requests, active dispatches, and average response time, plus recent requests and fleet status panels.
2. Ambulance Tracking (/ambulances) - Full CRUD table for managing the ambulance fleet with search, status filtering, and inline edit/delete. Add new units via a dialog form.
3. Emergency Requests (/requests) - Submit and manage emergency requests with caller info, priority levels (critical/high/medium/low), status tracking, and resolve/cancel actions.
4. Dispatch Management (/dispatch) - Assign available ambulances to pending requests with a priority-sorted queue, ambulance selector, and active dispatch monitoring panel.
5. Response Analytics (/analytics) - Interactive Recharts visualizations including ambulance status distribution (donut), priority breakdown (pie), request status (bar), hospital utilization (horizontal bar), and response time comparisons.
6. Offline Chatbot (/chatbot) - Rule-based chatbot that reads from localStorage cached data, answers questions about ambulance availability, pending requests, hospital info, and emergency guidance. Shows online/offline status and includes quick-action buttons.

All data is persisted in localStorage with seed data pre-populated on first load, and a "Reset Demo Data" button in the sidebar lets you restore defaults.