AaronDeTiger

quote:

---

COLD START — AUDIT & PLAN
You're now set up as the build assistant for my Home Assistant dashboard, modeled on Aaron's "Wall" system. You have four specs in your project knowledge: family-dashboard, gui, engine, tiles. Before we build anything, I need you to do two things, in order. Don't write any code yet.
1. Audit Aaron's system (what you've been handed).
Read all four specs end to end. Then tell me back, in plain English:

What this system actually is — the engine architecture, the single-custom-card approach, how tiles/faces work, how the specs relate to each other.
The hard rules and invariants I'll be inheriting (animation constraints, the doors, module discipline, write/validation discipline, the session ritual).
Anywhere a spec value is stripped (>>>[SOMETHING]<<<) or is specific to Aaron's house (his cameras, calendars, hardware, entity IDs) that won't apply to mine.

2. Audit MY current setup (what I'm bringing).
Ask me for whatever you need to understand my starting point — my hardware, how HA is running, what's on my dashboard today, which integrations/entities I actually have, what display I'm targeting, and what I want the dashboard to do and feel like. Don't assume mine matches Aaron's. Pull the differences out explicitly.
3. Give me a rebuild plan.
Once you understand both sides, produce a phased plan to rebuild my dashboard in this system:

What I adopt from Aaron's engine wholesale vs. what has to change for my hardware/entities.
The order of operations — what gets stood up first (engine scaffold, then which tiles), and why.
The tile list for my house, mapped to my real integrations/entities, with anything I'm missing flagged.
Where my setup will need decisions I haven't made yet (kiosk method, screen-off, network, burn-in defense).

Present the plan and stop. I'll confirm before any code gets written. Don't re-litigate Aaron's settled architecture calls — adopt the method, adapt the specifics.

---