From 449b428cead4b50a63d5682f7d9b3b7458467b95 Mon Sep 17 00:00:00 2001 From: Tyler Gillispie Date: Mon, 24 Aug 2026 22:11:32 -0700 Subject: [PATCH] docs(tasks): add 4 phased task specifications for mobile-first UI revamp --- ...ell.design-tokens-and-adaptive-nav-2215.md | 78 ++++++++++++++++++ ...i-auth.hero-passkey-and-onboarding-2216.md | 81 +++++++++++++++++++ ...aptive-launchpad-sessions-passkeys-2217.md | 77 ++++++++++++++++++ ...min.mobile-admin-cards-and-filters-2218.md | 75 +++++++++++++++++ 4 files changed, 311 insertions(+) create mode 100644 tasks/new/2026-0824.04.gem.feat.ui-shell.design-tokens-and-adaptive-nav-2215.md create mode 100644 tasks/new/2026-0824.05.gem.feat.ui-auth.hero-passkey-and-onboarding-2216.md create mode 100644 tasks/new/2026-0824.06.gem.feat.ui-user-hub.adaptive-launchpad-sessions-passkeys-2217.md create mode 100644 tasks/new/2026-0824.07.gem.feat.ui-admin.mobile-admin-cards-and-filters-2218.md diff --git a/tasks/new/2026-0824.04.gem.feat.ui-shell.design-tokens-and-adaptive-nav-2215.md b/tasks/new/2026-0824.04.gem.feat.ui-shell.design-tokens-and-adaptive-nav-2215.md new file mode 100644 index 0000000..78419a7 --- /dev/null +++ b/tasks/new/2026-0824.04.gem.feat.ui-shell.design-tokens-and-adaptive-nav-2215.md @@ -0,0 +1,78 @@ +# TASK METADATA + +- **Target Files:** `ui/components/Layout.tsx`, + `ui/components/AuthenticatedLayout.tsx`, `ui/components/AdminLayout.tsx` +- **Core Objective:** Implement a unified CSS custom property design token + layer, dark/light theme adaptation, and dual-mode responsive layout shell + (fixed mobile bottom navigation + desktop sticky header). +- **Dependencies:** + `docs/superpowers/specs/2026-08-24-mobile-first-ui-revamp-design.md` +- **Additional Important Notes:** Must remain 100% pure Hono SSR JSX (zero React + runtime dependencies) and support mobile safe-area insets + (`env(safe-area-inset-bottom)`). + +--- + +## 1. TASK METADATA + +The header block specifies the target layout templates, core objective, +dependencies, and constraints. + +## 2. Architectural Considerations & Risks + +### Risks + +- **Content Clipping Behind Fixed Bottom Navigation:** If the bottom navigation + bar is fixed to the bottom of the viewport on mobile without sufficient + padding on the `
` container, page content (such as action buttons or + footer links) could be obscured. + - _Mitigation:_ Explicitly set + `padding-bottom: calc(4.5rem + env(safe-area-inset-bottom))` on the main + layout container. +- **Flash of Unstyled Content / Layout Shift:** Inlining the design system + tokens into SSR JSX `