Jamon Holmgren jamonholmgren
| class_name CloudLayer extends MeshInstance3D | |
| # Summary: 2D cloud plane driver: syncs CloudLayer.gdshader sun direction/color/energy to Sky3D's dominant light and coverage to mission fog. | |
| ### Public signals and properties ### | |
| @onready var _sky: Sky3D = owner # https://github.com/TokisanGames/Sky3D | |
| @onready var _mat: ShaderMaterial = get_active_material(0) | |
| ### Godot hooks ### |
| #!/usr/bin/env bash | |
| # discord-cli — Minimal Discord bot CLI for channel/forum management | |
| # Usage: discord-cli <command> [options] | |
| # | |
| # Commands: | |
| # read <channel_id> [--limit N] Read messages from a channel/thread | |
| # post <channel_id> <message> Post a message to a channel/thread | |
| # post-reply <channel_id> <message_id> <nonce> <message> | |
| # Idempotent reply without pinging its author | |
| # react <channel_id> <message_id> <emoji> Add a reaction to a message |
| #!/usr/bin/env bash | |
| # | |
| # agent_cli — one front door for cross-agent work: read-only review/research | |
| # OR write-capable edit/refactor. | |
| # | |
| # Generalizes agent_review (read-only only) by adding an optional trailing | |
| # `mode` arg. `review` (default) keeps every agent read-only — identical to | |
| # agent_review. `edit` flips each CLI into its write-capable mode so a worker | |
| # can apply targeted refactors/edits. Append `edit` to allow writes. | |
| # |
Status: DRAFT (2026-06-28) — investigation just started. No implementation yet.
Slug: combat-perf-npc-gun-scan
Task source: Interactive human request (Jamon, 2026-06-28). After the tree-LOS native win (~90× faster query), hunt for the next perf opportunities. Jamon profiled a live combat mission with the F4 Perf panel and shared screenshots; this worksheet captures the read and the investigation.
Summary: Orchestrator protocol for driving multi-agent task execution. One coordinating agent (the orchestrator, often Codex) slices a task into parallel-safe units and dispatches worker agents (often Claude) via the Tools/agent_review CLI wrapper. Covers work slicing, context hygiene, temp report files, parallelism, avoiding conflicting edits, polling/tailing results, and output validation. Use when the user asks an agent to act as orchestrator/coordinator/dispatcher rather than do the work directly.
Key Files: Tools/agent_review, AGENT_WORKFLOW.md, AGENT_REVIEW.md, CODING_CONVENTIONS.md
Status: IMPLEMENTED
I've reached a pretty solid workflow for getting the most from agents in my code base. This setup and workflow has significantly reduced how often I have to fix obvious issues caused by agents doing the wrong thing.
This entire guide was hand-written by me, Jamon, with no AI-generated text nor any AI-suggested text or review. Fully human-generated.
My philosophy is based on these concepts:
Lessons learned on how to use AI agents effectively. In no particular order. Edited from time to time.
With agents, there should be no such thing as “tech debt”. An agent should simply pay down every bit of tech debt before presenting you with the “finished work”. Unlike humans, agent time is not very valuable; it can continue to work on something until it’s done, and shouldn’t make concessions assuming human constraints.
If an agent tells you that it’s “leaving something for later”, tell it to go finish it first before saying it’s done.
Per: https://x.com/jamonholmgren/status/2043385696535331324
mkdir -p "$HOME/homebrew"
git clone https://github.com/Homebrew/brew "$HOME/homebrew/.linuxbrew/Homebrew"
mkdir -p "$HOME/homebrew/bin"
ln -s "$HOME/homebrew/.linuxbrew/Homebrew/bin/brew" "$HOME/homebrew/bin/brew"
# Homebrew (per-user)