Jamon Holmgren jamonholmgren

name	jamon-apply-engineering-principles
description	Apply engineering principles to software design, implementation, and review

Apply Engineering Principles

Build the smallest complete solution that satisfies the actual requirement. Minimize unnecessary concepts, competing owners, remembered facts, and maintenance obligations—not line count. A justified new domain or real history remains legitimate. Judge the whole affected behavior: callers, owners, lifecycles, and interactions.

Each rule is a strong default. Depart only for a concrete, present reason the simpler design cannot satisfy (a supported caller, an invariant, an external contract, or a measurement) and keep the exception narrow. A tell shows where to look; it is neither proof of a violation nor permission to ignore the rule. Idioms change how a rule is expressed, not whether it applies.

name	apply-engineering-principles
description	Apply engineering principles to software design, implementation, and review. Prevent overengineering, duplicate state, misplaced ownership, speculative infrastructure, and false test confidence across languages and frameworks.

Apply Engineering Principles

Prefer the smallest complete solution that satisfies the actual requirement and fits the existing system.

Smallest means the fewest unnecessary concepts, competing owners, synchronization obligations, and lifecycle rules—not merely the fewest lines changed.

We couldn’t find that file to show.

Worksheet: Combat-Frame Perf — NPC AI / GunController / ScanBase

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.

	#!/usr/bin/env bash

	# verbose
	#set -x

	set -o pipefail
	shopt -s failglob
	set -u

	log () {

	---
	name: gso-babysit-external-agents
	description: Hand Gunship Origins implementation, research, or planning to a cheap in-process babysitter (Sonnet in Claude Code, Terra in Codex) that drives external Jam Session agents (Muse, Cursor Grok, Grok, Devin, and others) from a written plan, so the interactive session keeps its context for Jamon. Use when Jamon asks for a babysitter, cheap agent babysitter, or external agents to do work while he keeps talking with the lead. Do not use for a short task the lead can finish directly, the night-shift queue, or a single summoned agent.
	---

	# Babysit External Agents

	The interactive session is the supervisor in `$jamsession-orchestrate-agent-work`; the babysitter is its manager; Jam Session agents are workers. This skill adds the Gunship shape. Use concise plain English at every level and require it of every agent.

	## Lead: before launch

	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.
	#

	# Docs Authoring Guide

	Canonical authoring rules for all repo documentation. The docs system is optimized for coding agents, not humans: prioritize retrieval quality, unambiguous ownership, and token efficiency. It's the single source of truth for doc structure, naming, status taxonomy, cross-references, and anti-duplication. Owner: `AGENTS.md` routes here; this doc owns the rules.

	Key Files: N/A

	Status: IMPLEMENTED

	## Audience and intent