Joel Moss joelmoss

Nunebot

A recurring pass over my important projects. Each run tends the PRs from earlier runs, then ends with at most one new small, proven, ready-to-merge pull request per repo, plus an updated record in my brain repo.

How to think about the work

Software is not a factory. A factory builds identical widgets to a fixed spec and is done. Software changes every day: customers, scale, and requirements shift, so a perfect up-front spec never exists. Treat each repo like a painting you come back to: make one deliberate improvement per pass, and leave it better than you found it.

Spec what's objective. Hard limits, API contracts, data integrity, and tests are rules. Follow them.
Use judgment for the rest. Scale, taste, clarity, and what customers need right now. Read the code and the product like a critic, and decide.

name	speed-run
description	Coordinate ongoing project fixes with parallel workers, instrumented diagnosis, independent review, and delivery after each pushed merge. Use for /speed-run or an explicitly requested speed run. Editing this skill does not start one.

Speed run

Own every report through delivery while the user tries the project. New messages add or clarify work; they do not replace unfinished reports. Follow global and repository policies for synchronization, worktrees, verification, devices, cleanup, and protected changes.

Start

Audit this entire codebase for materially useful simplifications in its data structures, state representation, control flow, algorithms, and ownership.

This is an audit-only exercise. Do not edit files, run tests, implement recommendations, commit, or push. Read-only inspection commands are allowed.

You are the coordinator. Continue until the complete codebase has been reviewed and the final audit is validated.

Establish the coverage contract

Inspect the repository and inventory every identifiable subsystem.

AgentOS — Product Spec & Implementation Blueprint

Reconstructed from Danny Postma's talk How I Built My Own AgentOS on Claude's Agent SDK (So You Can Too) (2026). This document is both a product spec for a human and an implementation prompt for an AI coding agent. Build exactly this system. Do not invent features that are not specified here.

Role contracts and prompts in this file are reconstructed from the talk, not his verbatim files. Mark every reconstructed prompt in code comments and docs as such.

1. Goal and non-goals

name	demo-video
description	Generate a narrated demo video from browser screenshots and TTS audio. Captures scenes via agent-browser, generates voice narration via Inworld TTS API, and stitches into an MP4 with ffmpeg.

Demo Video Generation

Generate a narrated demo video from browser screenshots and TTS audio. The output is an MP4 with still-image scenes synced to voice narration.

	---
	name: plan-exit-review
	version: 2.0.0
	description: \|
	Review a plan thoroughly before implementation. Challenges scope, reviews
	architecture/code quality/tests/performance, and walks through issues
	interactively with opinionated recommendations.
	allowed-tools:
	- Read
	- Grep

	# frozen_string_literal: true
	require "fileutils"

	# Helper for Git worktree-aware behavior
	class GitWorktree
	PROJECT_ROOT = File.expand_path("..", __dir__)

	def self.instance = new

	def self.name = instance.name

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Signals</title>
	</head>
	<body>
	<button id="decrement">
	-

	'$schema' = 'https://jj-vcs.github.io/jj/latest/config-schema.json'

	[user]
	name = 'Pavan Kumar Sunkara'
	email = 'pavan.sss1991@gmail.com'
	username = 'pksunkara'

	[ui]
	default-command = 'default'
	editor = 'nvim'

	require "digest"
	require "rack"

	# This class encapsulates a unit of work done for a particular tenant, connected to that tenant's database.
	# ActiveRecord makes it _very_ hard to do in a simple manner and clever stuff is required, but it is knowable.
	#
	# What this class provides is a "misuse" of the database "roles" of ActiveRecord to have a role per tenant.
	# If all the tenants are predefined, it can be done roughly so:
	#
	# ActiveRecord::Base.legacy_connection_handling = false if ActiveRecord::Base.respond_to?(:legacy_connection_handling)