Make a prompt your own.

Build a complete, responsive dashboards website for [PROJECT NAME].

PROJECT BRIEF
Make complex metrics feel simple with a focused, data-rich dashboard.
Audience: [TARGET AUDIENCE — describe their needs and primary goal].
Technology: Use the existing project stack
Start by inspecting the existing project and reuse its routing, components, and conventions. State any assumptions. Ask only for missing decisions that block implementation.

PAGES & NAVIGATION
1. Overview
2. Reports
3. Customers
4. Settings
Give each page a real route, descriptive title, appropriate metadata, active navigation, and a useful not-found state.

VISUAL DIRECTION
Build a dark graphite workspace with violet accents, compact sidebar, restrained metric cards, and readable charts. Clearly label all metrics as demo data.
Treat the preview as visual direction, not a screenshot to reproduce. Create consistent spacing, typography, color tokens, and reusable components. Adapt the layout from 360px mobile to large desktop without horizontal overflow.

REQUIRED FUNCTIONALITY
- Date-range filtering that updates all metrics from the same seeded dataset
- Accessible charts with text summaries and CSV export
- Sortable paginated customer table and persistent display preferences
- Every visible control must work. Include loading, empty, validation, error, and success states where applicable.
- Use realistic seed content, clearly distinguish demo data, and avoid fabricated metrics or endorsements.

QUALITY & ACCESSIBILITY
- Use semantic landmarks, one clear page heading, associated form labels, visible focus, keyboard navigation, descriptive link text, and sufficient color contrast.
- Respect prefers-reduced-motion. Provide text alternatives for meaningful visuals.
- Validate inputs at trust boundaries. Keep secrets server-side. Never render untrusted HTML.
- Use an actual backend for shared data, authentication, or transactions when needed. If credentials are missing, document the setup and make the limitation visible instead of faking success.
- Optimize assets, reserve media dimensions, and keep dependencies and client bundles small.
- Handle unavailable browser storage and clipboard access gracefully.

ACCEPTANCE CHECKS
Run the production build and relevant lint/type checks. Verify all page routes, mobile and desktop layouts, keyboard flows, filtering, forms, and persistence. Test invalid inputs and empty/error states. Report what was verified and any remaining integration requirements.

DELIVERABLE
Implement working code, not just a proposal. Include a concise README with setup, environment variable names (no secrets), demo-data behavior, and deployment steps.

This builder assembles your brief locally. It doesn't call an AI service or send your draft to a server. Replace any remaining [placeholders] before building.