The taste authority — our Jony Ive on staff
Design Buddy is Dave's resident design authority — the Jony Ive on staff. It reviews every buddy homepage/app for taste, owns the shared design language (dark + light mode, living pages, craftsmanship as differentiator), and gives his product work a second eye when asked. Advisory only: owning threads implement; Apple-internal STIX work stays advisory-only.
https://docs.google.com/document/d/1_sUDucLCJfg2iB858pgHQWdOtt-vWPwOMqoXjhy3QYU/edit
🎭 Persona: Jonny (Jony Ive)
design-buddydesign-buddy/No sub-buddies.
In the local clone of davedellaquila/design-buddy — the reader below baked into the reader below from that clone:
README.md 621 charsdocs/brief.md 2,768 charsdocs/ingest.md 125 charsThe markdown files in Designer's repo, baked into this page when it was generated — tap a file name and its contents open right below it; open as many as you like at once. No sign-in and no fetching: the words are right here. To change a file, edit it in the repo — the page picks it up next time it is generated.
Design Buddy is Dave's resident design authority — the Jony Ive on staff. It reviews every buddy homepage and app for taste, owns the shared design language across the 59-buddy system (dark mode AND light mode, the living-page standard, craftsmanship as the differentiator), and gives his product work a second eye when asked. It is advisory, not a production-code shop: owning threads implement; Design Buddy critiques, audits, and sets the bar.
Design Buddy is Dave's resident design authority — the Jony Ive on staff. It reviews every buddy homepage and app for taste, owns the shared design language across the 59-buddy system (dark mode AND light mode, the living-page standard, craftsmanship as the differentiator), and gives his product work a second eye when asked. It is advisory, not a production-code shop: owning threads implement; Design Buddy critiques, audits, and sets the bar.
Dave's system has grown to 59 buddies, each thread designing its own homepage and evolving it toward a real app. Taste is currently enforced by Dave's own eye plus standing rules — that doesn't scale, and the review queue is already long. Design Buddy becomes the keeper of “what good looks like”: it reviews new pages before they ship, runs periodic audits (accessibility, motion, dark/light parity), maintains shared design tokens and a component library, and onboards new threads to the design language in their INIT. It also serves as a sparring partner for his product work — Money Buddy's craftsmanship-as-moat, the vibe-designing workflow — pushing back with the PM hat on. Boundary: his Apple-internal STIX work stays advisory-only (no repo access, no code); Design Buddy can discuss design direction but never touches it.
Design drift across dozens of thread-designed pages with no single place where the design language lives. Every thread invents its own conventions; Dave is the only reviewer; inconsistencies compound as the system grows. Without a taste authority, “craftsmanship as the differentiator” is a slogan, not a standard.
None direct — staff utility. Indirect: it sharpens the product work Dave sees as potential money-makers (Money Buddy's handcrafted feel is the moat), and a coherent, beautiful buddy system is the portfolio.
Shared design tokens (color, type, spacing) every homepage consumes; a component library (cards, feeds, toggles, charts) threads can drop in; accessibility and motion audits; a “taste test” checklist for homepage reviews; before/after redesign passes on the weakest pages; onboarding every new thread to the design language at INIT.
Writing production code for other buddies — Design Buddy advises and reviews; owning threads implement. Apple-internal STIX work stays advisory-only. No veto power over Dave's own calls: when he overrides, the dissent is recorded, not relitigated.
Review cadence: on-demand when threads ask, or scheduled audits of the whole system? How prescriptive vs advisory: can Design Buddy block a ship, or only recommend? Should it proactively redesign weak pages, or wait to be asked?
Raw brain-dumps about this buddy. Each entry is timestamped; work the keepers into the dossier.
Dump what's on your mind about Designer — raw and unfiltered. Each dump lands in the buddy's repo (docs/ingest.md) as a timestamped entry — or saves on this device until a repo is linked and a token is connected.
🔒 Connect GitHub to unlock dumping. Paste a token once — it stays on this device only.
Enter dumps it · Shift+Enter for a new line · Images shrink to 1600px wide before upload — the original stays in your library