jtaroreh
- 21 skills
- 0 followers
- 3 hours ago last updated
- ▌ Arena · jtarorehSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
- ▌ Swarm · jtaroreh bundleFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
- ▌ Deslop · jtarorehClean AI slop and defensiveness out of code and diffs before commit. Strips narrating comments, redundant guards, speculative error handling, unused abstractions, and dead compatibility code.
- ▌ Recall · jtarorehReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
- ▌
- ▌ Reflect · jtaroreh bundleSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- ▌ Architect · jtaroreh bundleSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
- ▌ Automate Me · jtarorehUse for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via unslop, optionally pulling fresh evidence from recent transcripts.
- ▌ Interrogate · jtaroreh bundleUse for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
- ▌ No Comments · jtarorehSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- ▌ Poteto Mode · jtaroreh bundlepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
- ▌ Setup Agystack · jtaroreh bundleConfigure models and execution runtime for agystack. Configures Antigravity model tiers per role and Cloud Run runtime settings for up to 100+ parallel workers.
- ▌ Show Me Your Work · jtaroreh bundleKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
- ▌ Create Verification Skill · jtaroreh bundleGenerate a project-local verification skill that drives your app the way a user does across any language, framework, or platform. Use for /create-verification-skill, 'make a control skill for this repo', or when a project has no scripted way to prove UI/CLI/service behavior.
- ▌ Maintain Verification Skill · jtarorehPeriodic 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".
- ▌ Principle Attack The Premise · jtarorehApply when handed a problem, constraint, or design you are tempted to accept as given. Ask if the premise is false, the constraint is self-imposed, or a simpler framing eliminates the work entirely.
- ▌ Principle Guard The Context Window · jtarorehApply 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.
- ▌ Principle Test Behavior Not Implementation · jtarorehApply when writing or reviewing tests. Test what the system does from the outside (inputs, outputs, observable behavior, invariants), not how it is structured internally (private methods, call counts, internal state).
- ▌ How · jtaroreh bundleUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
- ▌ Why · jtaroreh bundleUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
- ▌ Loop · jtaroreh bundleRun iterative verification hillclimbs against a concrete test command using Antigravity reactive scheduling. Use for /loop, 'loop until green', or automated hypothesis testing with a verification predicate.