gannonh
- 112 skills
- 0 followers
- 19 hours ago last updated
- ▌ Ps Principle Laziness Protocol · gannonh bundleApply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
- ▌ Brainstorming With Explorer Challenger Teams · gannonhRun structured brainstorming sessions using paired explorer/challenger agent teams. Explorers generate ideas, challengers play devil's advocate, and 2-3 rounds of debate produce pressure-tested proposals. Use when brainstorming product ideas, exploring feature directions, evaluating strategic options, generating milestone candidates, or when the user says "brainstorm", "explore ideas", "what should we build next", "generate options", or "run an ideation session".
- ▌ Ps Principle Boundary Discipline · gannonh bundleApply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
- ▌ Ps Principle Minimize Reader Load · gannonh bundleApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
- ▌ Ps Principle Foundational Thinking · gannonh bundleApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- ▌ Ps Principle Type System Discipline · gannonh bundleApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
- ▌ Ps Principle Subtract Before You Add · gannonh bundleApply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
- ▌ Ps Principle Exhaust The Design Space · gannonh bundleApply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
- ▌ Ps Principle Guard The Context Window · gannonh bundleApply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
- ▌ E2e Test Author · gannonhAuthor or modify local Playwright + real-Electron E2E tests for Kata Agents. Use when adding @smoke/@settings/@browser/@agent specs, harness modules, or product flows under e2e/, or when wiring stable id selectors into renderer code for E2E.
- ▌ Verify Kata Agents · gannonh bundleVerify the Kata Agents macOS Electron desktop app with its isolated Playwright harness; use when proving launch, onboarding, settings, browser-panel, agent, channels, memory, handoffs, Katacode dispatch, or Git behavior.
- ▌ Release Kata Agents · gannonhRunbook for releasing Kata Agents desktop builds to GitHub Releases. Use this skill whenever the user asks to release, ship, publish, cut a release, run a release workflow, do a nightly, do a nightly dry run, do a stable release, or anything about releasing or publishing Kata Agents. Covers the full sequence: Nightly Dry Run → Nightly Release → Stable Dry Run → Stable Release. Dispatches the release.yml workflow, polls for status, verifies results at each stage, and knows exactly what a passing run looks like vs. a real failure.