Timmyy3000

Timmyy3000/skills

Skill Claude CodeCodex

Guides users through kickoff setup, /kickoff, and picking the skill, playbook, or principle for a task. Use for /kickoff-help, or when the user asks how to install, set up, or use kickoff, or which kickoff skill fits. Not for requests to do work, even ones that name kickoff.

Timmyy3000/skills

Skill Claude Code

Configure which models kickoff uses per role and at what reasoning budget. Detects the current harness and its available models, migrates a version 1 kickoff.yaml, and writes kickoff.yaml version 2. Use for /kickoff-setup, "configure kickoff models", "kickoff budget", or changing kickoff's model choices.

Timmyy3000/skills

Skill Claude Code

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

Timmyy3000/skills

Skill Claude Code

Use when building a custom UI (page, dashboard, buttons) that should wake the agent over a webhook, when the user must provide a webhook secret, or when exposing that UI on Tailscale.

Timmyy3000/skills

Skill Claude Code

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

Timmyy3000/skills

Skill Claude Code

Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.

Timmyy3000/skills

Skill Claude Code

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

Timmyy3000/skills

Skill Claude Code

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

Timmyy3000/skills

Skill Claude Code

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

Timmyy3000/skills

Skill Claude Code

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

Timmyy3000/skills

Skill Claude Code

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

Timmyy3000/skills

Skill Claude Code

Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

Timmyy3000/skills

Skill Claude Code

Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

Timmyy3000/skills

Skill Claude Code

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

Timmyy3000/skills

Skill Claude Code

Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to delegated tasks; keep summaries in the main thread, not raw payloads.

Timmyy3000/skills

Skill Claude Code

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

Timmyy3000/skills

Skill Claude Code

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

Timmyy3000/skills

Skill Claude Code

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

Timmyy3000/skills

Skill Claude Code

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

Timmyy3000/skills

Skill Claude Code

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.

Timmyy3000/skills

Skill Claude Code

Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

Timmyy3000/skills

Skill Claude Code

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

Timmyy3000/skills

Skill Claude Code

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'.

Timmyy3000/skills

Skill Claude Code

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.