btseytlin

btseytlin/ultrapack

Skill Claude CodeCodex

Use when implementing deterministic, reusable code where regressions would warrant a CI red light. Enforces RED-GREEN-REFACTOR. Applicability rule and skip conditions inside.

btseytlin/ultrapack

Skill Claude CodeCodex

Manually test the latest change with one realistic positive case and one adversarial negative case, capturing evidence before any further fix. Use when the user asks for a quick confidence check or wants to test a recent implementation.

btseytlin/ultrapack

Skill Claude CodeCodex

Use on any bug, test failure, or unexpected behavior before proposing a fix. Enforces four-phase root-cause investigation — reproduce, pattern-match, hypothesize, fix — with a hard rule against symptom patches.

btseytlin/ultrapack

Skill Claude CodeCodex

Use before any creative work — features, components, behavior changes. Turns an idea into a validated spec with explicit tradeoffs and unknowns, and splits scope into multiple tasks if it's too large. Output is the ## Context and ## Design sections of the task file.

btseytlin/ultrapack

Skill Claude CodeCodex

Use when writing or editing documentation — project docs, CLAUDE.md, READMEs, SKILL.md, docstrings, inline comments. Auto-triggers on .md files and docstring edits. Enforces lead-with-why, kill stale content, lists over tables, no aspirational sentences.

btseytlin/ultrapack

Skill Claude CodeCodex

Use to implement an approved plan. When the plan declares ### Interface graph, derives waves by topo-sort over [blocks] IF edges only — non-blocking IF edges (the default) put producer and consumer in the same wave, since the IF declaration is sufficient context. Edits inline when only one implementer would fire…

btseytlin/ultrapack

Skill Claude CodeCodex

Use after design to turn a validated spec into a lean implementation plan. Outputs the ## Plan section of the task file — files, line numbers, class/method names, invariants, test strategy, order. Ends with a scope-creep / simpler-way check.

btseytlin/ultrapack

Skill Claude CodeCodex

Use after verify passes for the future maintainer's audit — sit in the chair of the person who'll touch this code in 3-6 months and ask "what will bite us later?" at the decision level. Surfaces wrong abstractions, load-bearing-but-unobvious shapes, next-change traps, drift from surrounding code; raises a Scope flag…

btseytlin/ultrapack

Skill Claude CodeCodex

Use after execute to attack the change and demonstrate how it's broken. Default stance — the change is broken; prove and demonstrate it. Builds an attack checklist (happy-path / negative / invariant / interface hypotheses), runs each freshly, smokes the end-to-end, writes a short summary to the task file's Verify…