Bento Grid

Build a complete ◉ Tasko page in this style, extending the original hero into content, concrete operations and return paths rather than isolated controls or a partial demo. Preserve brand, hero copy, assets, composition, tokens and all variants. Keep preview.brand aligned with shared REFERENCE_BRANDS; ReferenceStyleScene defines the hero structure, actual navigation and assets.

Preserve Tasko’s .tasko-body columns at 32% / 14.5% / 14.5% / 35%, rows at 13.6cqw / 11.8cqw and 1.15cqw gaps. The intro spans both rows; the calendar spans the middle columns; green stats and a mountain tile occupy the right, with separate task/note entries below. Keep the distinct pale blue/lilac/green fills and 1.65cqw radii, not equal-width columns, fixed 96px rows or uniformly purple cards. Use the existing height adjustment for six-week months; below 600px major tiles span the width while tasks and notes remain paired.

Full-page operations:
Get started opens the local workspace. Change calendar month and date, add/complete tasks and edit/save notes. Login explains demo identity without claiming real signup or cloud sync.

Share one renderer between static covers, the detail experience and /style-scenes/bento-grid/ (English /en/style-scenes/bento-grid/). Static covers contain no nested live buttons; the detail experience enables the same page’s semantic controls and brand continuation in an independent document. Original navigation and CTAs reach actual content or workflows, not placeholder links, color-only changes or one-line toasts.

Interaction state lives only in this page’s memory. Reload, toolbar reset and mode changes restore initial state; do not use localStorage or sessionStorage. In-page clear/reset undoes this visit’s operations without implying cross-page or persistent saves.

Provide return, cancel or clear/reset paths and disclose the page-memory state boundary; never fake real payments, email, login, AI or cloud sync. Reflow desktop, 390px and 320px layouts with readable text and usable targets rather than shrinking the desktop page. Give controls accessible names, keyboard access and visible focus; overlays close and return focus, validation/results are announced; respect prefers-reduced-motion.

Add no dependencies. Check both languages, original navigation/CTAs, concrete results, return/reset and narrow reflow; report checks actually run and pending items, never requirements as passed results.

Additional requirements:
- Dark mode support
- Respect prefers-reduced-motion
- No new dependencies
- Run existing checks and list modified files

Hand to your coding agent — stack a style and extra requirements on top