Gridshift UI

Purpose

Create distinctive, production-minded interfaces where visual character supports the product's real purpose. For technical dashboards, this may mean a precise monochrome system with restrained terminal-inspired details; for other products, adapt the visual language to the audience and existing brand.

The goal is clear, credible, usable, responsive, and memorable—not a generic SaaS template, fictional hacking interface, or collection of decorative cards.

Read only the reference documents relevant to the current task.

Start Here

1. Inspect repository instructions, app structure, framework, design system, dependencies, routes, and data models before changing code.
2. Read references/README.md for the reference index.
3. Read references/design-principles.md and references/product-and-information-architecture.md for dashboard work.
4. Read references/visual-system.md for visual styling and references/motion-and-interaction.md for interactive or animated work.
5. Read references/engineering-and-accessibility.md before implementation and references/quality-checklist.md before declaring work complete.
6. Treat screenshots, URLs, and product references supplied by the user as evidence. Do not claim an uninspected reference has a specific layout or behavior.