flower
/
All briefs
planned draft note home-tracker
epic · Project review & updates epic - Let's get this proj...

home-tracker C: design rework — teal / playful / gamer-girl vibe

Dispatch

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

kind

No dispatch requests yet — dispatch above to generate a copy-paste packet.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. status change 1d ago
    agent · home-tracker-refine
  2. refinement 1d ago

    # C — Design rework (the big swing) Child of epic #211. Approach decided by operator (Q3, 2026-07-04): **design-loop first — produce a design doc + sequenced PR plan, then build.** ## Goal Make Mike's wife *want* to use the app. Persona: "girly asian gamer girl," Tarkov Twitch streamer, favorite color **teal**, strongly dislikes non-intuitive UIs. Feel: fun / clean / hip / intuitive — not a boring backend CRUD app. ## Approach (locked) 1. Run the **design-loop** (writer↔reviewer skill) to produce a polished design doc + sequenced PR plan for the teal-forward, playful-but-intuitive redesign. No code in phase 1. 2. Operator reviews the design doc; then build in the sequenced PRs. ## Scope / surfaces Prioritize the surfaces she'll actually touch: home/dashboard, cat-feeding, gaming status. Build on Flux (respect `resources/css/app.css` customizations; use `external-docs/fluxui`). Teal-forward palette. ## Open (non-blocking) Reference aesthetics: any apps/games/streamer overlays/sites whose look she loves would sharpen the design-loop — welcome but not required to start. The design-loop can surface specific reference questions as it runs. ## Ordering Soft-benefits from A (DB connectivity) so the design works against real data — not a hard dependency. ## Status Planned — ready to dispatch the design-loop.

    agent · home-tracker-refine
  3. spec snapshot 1d ago

    # C — Design rework (the big swing) Child of epic #211. STILL REFINING — blocked on the design-scope question (Q3 / question #49 on epic #211). ## Goal Make Mike's wife *want* to use the app. Persona: "girly asian gamer girl," Tarkov Twitch streamer, favorite color **teal**, strongly dislikes non-intuitive UIs. Feel: fun / clean / hip / intuitive — not a boring backend CRUD app. ## Direction (draft, pending Q3) - Teal-forward palette on Flux (respect existing customizations in `resources/css/app.css`; use `external-docs/fluxui`). - Playful personality + streamer/gamer touches, but clean and highly intuitive. - Target the surfaces she'll actually touch first: home/dashboard, cat-feeding, gaming status. ## Open (Q3) Scope + approach: full redesign vs targeted polish vs design-loop doc first vs teal-theme pass. Plus any reference apps/games/streamer overlays she loves. Recommend a design-loop doc first (design doc + sequenced PR plan, then build). ## Note Benefits from A (DB connectivity) done first so the designer works against real data — soft ordering, not a hard dependency.

    system · home-tracker-refine
  4. status change 1d ago
    agent · home-tracker-refine
  5. plan proposed 1d ago

    # C — Design rework (the big swing) Child of epic #211. STILL REFINING — blocked on the design-scope question (Q3 / question #49 on epic #211). ## Goal Make Mike's wife *want* to use the app. Persona: "girly asian gamer girl," Tarkov Twitch streamer, favorite color **teal**, strongly dislikes non-intuitive UIs. Feel: fun / clean / hip / intuitive — not a boring backend CRUD app. ## Direction (draft, pending Q3) - Teal-forward palette on Flux (respect existing customizations in `resources/css/app.css`; use `external-docs/fluxui`). - Playful personality + streamer/gamer touches, but clean and highly intuitive. - Target the surfaces she'll actually touch first: home/dashboard, cat-feeding, gaming status. ## Open (Q3) Scope + approach: full redesign vs targeted polish vs design-loop doc first vs teal-theme pass. Plus any reference apps/games/streamer overlays she loves. Recommend a design-loop doc first (design doc + sequenced PR plan, then build). ## Note Benefits from A (DB connectivity) done first so the designer works against real data — soft ordering, not a hard dependency.

    agent · home-tracker-refine
  6. parent set 1d ago

    Grouped under epic #211.

    agent · home-tracker-refine
  7. note added 1d ago

    # C — Design rework (the big swing) Child of epic #211. STILL REFINING — blocked on the design-scope question (Q3 on the epic). ## Goal Make Mike's wife *want* to use the app. Persona: "girly asian gamer girl," Tarkov Twitch streamer, favorite color **teal**, strongly dislikes non-intuitive UIs. Feel: fun / clean / hip / intuitive — not a boring backend CRUD app. ## Direction (draft, pending Q3) - Teal-forward palette built on Flux (respect existing customizations in `resources/css/app.css`; use `external-docs/fluxui`). - Playful personality + streamer/gamer touches, but clean and highly intuitive. - Target the surfaces she'll actually touch first: home/dashboard, cat-feeding, gaming status. ## Open (Q3) Scope + approach: full redesign vs targeted polish vs design-loop doc first vs teal-theme pass. Plus any reference apps/games/streamer overlays she loves. Recommend a design-loop doc first (produce design doc + sequenced PR plan, then build). ## Note Benefits from A (DB connectivity) being done first so the designer works against real data — soft ordering, not a hard dependency.

    agent · home-tracker-refine
  8. participant joined 1d ago
    system · home-tracker-refine

epic · dependencies

Relationships

depends on

No dependencies — dispatchable once planned.

agents · waves

Participants

  • home-tracker-refine participant · active

trace · graph

Links

No links yet — they accrue as agents work the brief.

scope

Projects

  • home-tracker · primary

dogfood · read-only

Agent’s-eye view

The literal recall_brief payload an agent gets — same service path as the MCP tool.