Dave's software engineer for the BuddyOS codebase
Developer Buddy is Dave's software engineer for the BuddyOS codebase. It owns the code day-to-day — the dashboard (build.py), the homepage generators, the canonical shared components, and the buddy-server codebase — taking Dave's decisions via Astro and design specs from the Designer, and turning them into shipped builds verified on the served copy. It reports back in outcomes: what changed, which build number, and where to see it — so Dave's main chat stays about what he wants, not how the code works.
https://docs.google.com/document/d/1XlKkO6VH0aYC6P5nlCxoZ_Gm62F4qkn51PwkWtI-zqg/edit
🎭 Persona: The Lead Engineer
🔊 Voice: avocado_v2:vdc_NOID65
developer-buddydeveloper-buddy/No sub-buddies.
In the local clone of davedellaquila/developer-buddy — the reader below baked into the reader below from that clone:
KNOWLEDGE.md 3,820 charsCONFIG.md 1,055 charsSOUL.md 132 charsDECISIONS.md 1,755 charsACCOMPLISHMENTS.md 4,997 charsREADME.md 712 charsdocs-tipjar-custom-plan.md 3,932 charsdocs/brief.md 3,764 charsdocs/ingest.md 558 charsdocs/job-req.md 3,764 charsThe markdown files in Developer Buddy'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.
Everything this buddy has learned: facts, specs, history.
~/workspace/projects/buddy-tree); build.py generates the dashboard.buddies.json): 163 buddies, 163 with homepages; 93 buddies carry attention items, 114 attention items total.build.py 14,300, gen_basic_homepages.py 1,329, gen_default_homepages.py 445 — 16,074 lines total.index.html files; 72 pages still carry the basic-template marker; 167 index.html files still carry the old floating tip-jar pill.c375899 (this buddy hired & wired). Prior build the same morning: 20261028.0815, commit 649794e (Find palette + Recents floater + inboard grippers).buddy-tree/developer-buddy/index.html (58,741 bytes at build) — sources for its live-stats strip: buddies.json counts, git log counts, and wc -l on the build tooling, all as of 2026-10-28. When those numbers change, the page should change.<script> blocks after any future edit.role-intro.mp3 sits beside the homepage, but the template page at hire contained no “Hear my role” block (the generator emits one only when the mp3 exists at generation time) — the custom page adds the canonical block by hand: <audio controls preload="none" src="role-intro.mp3">..header-tip link in the sticky header pointing at https://ko-fi.com/davedellaquila ; it must never carry class="tipjar" or the floating .tipjar CSS, so fleet greps for the old pill stay meaningful.BUDDY-BASIC-TEMPLATE marker in a custom page — gen_basic_homepages.py treats either as template-managed and will regenerate/wipe it (see buddy-tree AGENTS.md).prefers-color-scheme) — buddy-tree AGENTS.md standing rule.node --check them before any push; verify on the served copy, never announce from a local build.<style> and <a> — generators must strip HTML comments before extracting parts, or the prose poisons generated pages (caught mid-run, fixed in both generators).--about for About pages); running it on v2-era index pages jumps them a template generation — for jar-only changes, swap surgically instead.How this buddy is configured: identity, persona, voice, scope, preferences, privacy. Seeded at creation by new_project.py; the Desk renders these settings and audition picks update them (manifest row 26).
SOUL.md.Persona and voice for Developer Buddy. Seeded at creation; refine as the buddy develops its character.
Decisions made, with dates.
Dave's pick from the onboarding auditions (main chat, 2026-10-28): keep the default persona, The Lead Engineer. Alternates were The Principal Engineer and The Shipwright. The pick stands in CONFIG.md and the registry; no change needed — the default was already in effect. Voice auditions moved to this buddy's own thread the same day at Dave's direction (auditions live in the buddy's side chat from now on).
Dave's pick from the onboarding auditions (main chat, 2026-10-28, minutes before auditions moved to the buddy's own thread): Precise Window (avocado_v2:vdc_NOID65) — the default already in effect, so CONFIG.md and the registry already carry it and the role audio needs no re-record. Alternates auditioned: Wise Lighthouse, Polished Coin.
Dave's remark in the main chat ("i think developer buddy is a girl"), relayed the same evening: Developer Buddy is a girl — she/her from here on, fleet-wide. Astro had referred to this buddy as "he" when relaying Dave's iPhone screenshot earlier that evening; this entry is the correction. Recorded in CONFIG.md (Identity) so the Desk and future threads pick it up.
Cluster at the top, keep the middle empty. The collapsed rail's furniture (expand, Recents, current-view) groups in one tight cluster at the top of the left edge so the middle band of the screen stays clear — the point of the 20261030.0559 move was screen real estate, not tidiness. Any future rail proposal that puts furniture mid-edge contradicts Dave's stated principle.
What this buddy has shipped and done. The review-time record — keep it fresh.
120baf9, served-verifiedbuddy-tree/developer-buddy/index.html (46,425 bytes template → 58,741 bytes custom) with a terminal / ship-log design that could only be this buddy's: a code-window hero ($ whoami --role, blinking cursor), a build-pipeline strip (Decision → Spec → Build → Verify → Push → Served copy), a monospace ship log, and proportional codebase-anatomy bars.c375899).c375899 hired & wired (20261028.0821), 649794e Find/Recents/grippers (20261028.0815), 0d1df5b Find overlay, cb48b67 framework buttons, 5a6ee53 Doc/Drive links in a new tab.class="tipjar" / .tipjar CSS).role-intro.mp3, Needs-your-attention item (job req) linked to its Google Doc, and links on every buddy/doc/repo mentioned (Project Buddy, job req, private repo, About).docs/ingest.md, with the local-device fallback intact.node --check; HTML tag balance clean (no errors, nothing left open); greps confirm no forbidden generator phrases/markers and no floating tip jar.120baf9 (explicit pathspecs: homepage + CHANGELOG.md + version.txt), pushed, and verified on the served copy at https://davedellaquila.github.io/buddy-system/developer-buddy/ — header Tip Jar bug, live stats (1,497 commits), and ship-log hero all present in the served HTML; served version.txt reads 20261028.0826.Developer Buddy is Dave's software engineer for the BuddyOS codebase. It owns the code day-to-day — the dashboard, the homepage generators, the shared components, and the buddy-server codebase — so Dave's main chat stays about what he wants, not how the code works. Change requests arrive as decisions from Dave via Astro and as buildable specs from the Designer; Developer Buddy turns them into shipped builds, verifies each one on the served copy, and reports back in outcomes: what changed, which build number, and where to see it.
Prepared by Developer Buddy, 2026-10-28. Status: awaiting Astro/Dave go-ahead — no page has been edited under this plan.
Generator-managed pages are done (build cf55bd1: 71 template homepages, 164 About pages, 15 v2 default pages). What remains is every page the generators do NOT own: 78 custom buddy homepages + 3 sub-pages still carrying the floating pill (class="tipjar"). Per the standing rule, these migrate per-page — this plan is the scope, surfaced before any bulk edit.
<style> to <head> and the <a class="header-tip"> anchor as the last item of the page's existing header/topbar row (with a right-end rule where the header is flex).Developer Buddy is Dave's software engineer for the BuddyOS codebase. It owns the code day-to-day — the dashboard, the homepage generators, the shared components, and the buddy-server codebase — so Dave's main chat stays about what he wants, not how the code works. Change requests arrive as decisions from Dave via Astro and as buildable specs from the Designer; Developer Buddy turns them into shipped builds, verifies each one on the served copy, and reports back in outcomes: what changed, which build number, and where to see it.
Project Buddy. Dave directs through Astro; the Designer (with Jonny's crits) supplies design specs; Astro relays decisions in and results out.
Automated pre-push checks (script lint, link checks), visual regression screenshots of the dashboard at phone/tablet/desktop widths, a weekly code-health digest, and owning the buddy-server codebase once Dave's deploy lands. Possibly: a starter-repo template pass so every future buddy repo is born with the same tooling.
git add -A in buddy-tree (explicit pathspecs only); extract inline scripts and node --check before pushing; pull --rebase before push; GitHub Pages lags ~1–2 min; Dave reviews on the served copy or his local clone, never on a claim.Raw brain-dumps about this buddy. Each entry is timestamped; work the keepers into the dossier.
DONE — Dave marked this done on the homepage: "Job req ready for review — looks good, edits, or defer?" (attention id: developer-buddy-job-req). Please remove it from the attention list in buddies.json.
It would be nice if the tiles on the Developer Buddy homepage were active, if I could click them and go see additional information about whatever it is that I clicked on.
Developer Buddy is Dave's software engineer for the BuddyOS codebase. It owns the code day-to-day — the dashboard, the homepage generators, the shared components, and the buddy-server codebase — so Dave's main chat stays about what he wants, not how the code works. Change requests arrive as decisions from Dave via Astro and as buildable specs from the Designer; Developer Buddy turns them into shipped builds, verifies each one on the served copy, and reports back in outcomes: what changed, which build number, and where to see it.
Project Buddy. Dave directs through Astro; the Designer (with Jonny's crits) supplies design specs; Astro relays decisions in and results out.
Automated pre-push checks (script lint, link checks), visual regression screenshots of the dashboard at phone/tablet/desktop widths, a weekly code-health digest, and owning the buddy-server codebase once Dave's deploy lands. Possibly: a starter-repo template pass so every future buddy repo is born with the same tooling.
git add -A in buddy-tree (explicit pathspecs only); extract inline scripts and node --check before pushing; pull --rebase before push; GitHub Pages lags ~1–2 min; Dave reviews on the served copy or his local clone, never on a claim.Dump what's on your mind about Developer Buddy — 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