SiTaggart
- 99 skills
- 0 followers
- 1 week ago last updated
- ▌ Ce Thermo Nuclear Code Quality Review · sitaggartRun an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
- ▌ Reproduce And Fix Issues · sitaggart bundleReproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
- ▌ Principle Test Behavior Not Implementation · sitaggart bundleApply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value. If the test would still pass when every imported function returns undefined, rewrite the assertion or delete the test.
- ▌ Principle Migrate Callers Then Delete Legacy Apis · sitaggart bundleApply 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.
- ▌ Principle Separate Before Serializing Shared State · sitaggart bundleApply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
- ▌ Maintain Verification Skill · sitaggart bundlePeriodic 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 Laziness Protocol · sitaggart 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.
- ▌ Repoprompt Multi Review · sitaggart bundleUse when a code change needs a higher-confidence review in RepoPrompt, especially before merge or after substantial, subtle, or high-risk changes. Produces one evidence-checked CE report from independent model reviews.
- ▌ Principle Attack The Premise · sitaggart bundleApply 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.
- ▌ Setup Benny · sitaggart bundleConfigure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.
- ▌ Principle Boundary Discipline · sitaggart 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.
- ▌ Typescript Advanced Types · sitaggartMaster TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
- ▌ Principle Minimize Reader Load · sitaggart 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.
- ▌ Principle Type System Discipline · sitaggart 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.
- ▌ Principle Subtract Before You Add · sitaggart bundleApply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
- ▌ Principle Exhaust The Design Space · sitaggart 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.
- ▌ Principle Guard The Context Window · sitaggart 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.
- ▌ Principle Never Block On The Human · sitaggart bundleApply 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.
- ▌ Principle Sequence Verifiable Units · sitaggart bundleApply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
- ▌ Principle Make Operations Idempotent · sitaggart bundleApply 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.
- ▌ Principle Outcome Oriented Execution · sitaggart bundleApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
- ▌ Principle Encode Lessons In Structure · sitaggart bundleApply 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.
- ▌ Triage Issue Reports · sitaggart bundleTriage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.
- ▌ Principle Redesign From First Principles · sitaggart bundleApply 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.
- ▌ Docs Researcher · sitaggartResearch official documentation and version-specific constraints for a framework, library, or API when current external behavior materially shapes a plan or implementation. Returns official-docs findings, version caveats, and community patterns.
- ▌ Document Review · sitaggartReview requirements, PRDs, kickoff docs, and implementation plans with taste. Use after ce-plan for markdown plans, before ce-plan for requirements docs that need a quality pass, or whenever a written project artifact needs sharper scope, coherence, and reader utility.
- ▌ Git Clean Gone Branches · sitaggart bundleClean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
- ▌ Ce Improve Skills · sitaggartImprove agent guidance from evidence. Use for continual-improvement loops that patch skills, AGENTS.md, or CLAUDE.md from recurring corrections and verified session friction across local coding agents.
- ▌ Ce Slack Research · sitaggart bundleUse only when the user explicitly asks to search Slack or wants Slack discussions, decisions, or organizational context about a named topic.
- ▌ Ce Simplify Code · sitaggartUse when the user asks to simplify, refactor, clean up, reduce duplication, or remove unnecessary complexity from recently changed code. Also use after a substantial refactor or rewrite to check behavior preservation, reuse, and resulting complexity before completion.
- ▌ Qmd Knowledge Base · sitaggart bundlePreflight non-trivial tasks against this machine's indexed knowledge base (~12k markdown docs of wikis, specs, decisions, prior plans, and session retros) when prior decisions, product intent, ownership, conventions, expected behavior, or known failures could change the correct solution—even when the prompt does not request history. Skip only mechanical work fully defined by live source. Routes searches to relevant collections and classifies evidence authority; use the installed QMD surface for query mechanics.
- ▌ Orca Multi Review · sitaggart bundleRun a repository's existing cross-provider multi-model review through visible Orca-managed Claude, Codex, and OpenCode terminals. Use when the user asks for orca-multi-review, an Orca-based multi-model review, or wants to watch the repository review agents and progress instead of launching hidden coding CLIs.
- ▌ Ce Compound Refresh · sitaggart bundleRefresh stale .ai/solutions learnings against current code. Use for "refresh my learnings", audit stale learnings, or consolidate overlapping docs.
- ▌ Spade Python Taste · sitaggart bundleApply Spade-specific Python service design taste when writing, reviewing, refactoring, or fixing Python under spade, especially FastAPI or Termpower services, Pydantic boundaries, router packages, runtime dependencies, expensive endpoints, and service code-shape decisions.
- ▌ Resolve Pr Merge Conflicts · sitaggartResolve a PR that conflicts with its base branch by rebasing onto the base and force-pushing with lease — never a merge commit. Use when a PR is out of date or has conflicts with main, when GitHub shows "This branch has conflicts that must be resolved", or when the user asks to rebase a branch, update a branch against main, or resolve PR conflicts.
- ▌ Learnings Researcher · sitaggartSearch .ai/solutions/ for applicable past learnings via frontmatter metadata — bugs, architecture, design patterns, conventions, workflow lessons. Use before implementing features, making decisions, or starting work in a documented area so institutional knowledge carries forward.
- ▌ Principle Prove It Works · sitaggart bundleApply 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.'
- ▌ Create Verification Skill · sitaggart bundleGenerate a project-local verification skill that drives your app the way a user does — 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.
- ▌ Principle Build The Lever · sitaggart bundleApply 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.
- ▌ Principle Fix Root Causes · sitaggart bundleApply 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.
- ▌ Repo Research Analyst · sitaggartPerform scoped repository reconnaissance — technology, architecture, patterns, conventions, issues, templates — and return a compact evidence-backed markdown summary inline. Use when onboarding to a codebase, grounding a plan, or when a loop skill dispatches scoped repo research.
- ▌ Principle Experience First · sitaggart bundleApply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
- ▌ Principle Model The Domain · sitaggart bundleApply 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.
- ▌ Chronicle · sitaggartAllows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.
- ▌ Blast Radius · sitaggart bundleFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
- ▌ Setup Pstack · sitaggartConfigure which models pstack uses per role. Detects your available models and writes host-specific model overrides for the bundled defaults. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.
- ▌ Ce Debug · sitaggart bundleFind root causes and fix bugs. Use for errors, failing tests, issue repros, stack traces, "debug this", or "why is this failing".
- ▌ Ce Grill · sitaggartClarify and stress-test a requirements doc, plan, design, or rough approach through a focused interview. Use when the user wants to be grilled, or before ce-plan when the requirements are too branchy, ambiguous, or strategically important to plan cleanly.
- ▌ Pr Review Canvas · sitaggart bundleGenerate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says "review this PR".
- ▌ Ce Handoff · sitaggartCompact the current conversation into a durable handoff document for another agent or future session. Use when the user asks to hand off, pause with context, summarize work for the next session, or prepare a continuation brief.
- ▌ Figure It Out · sitaggart bundleDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
- ▌ Ce Ideate · sitaggart bundleGenerate and evaluate grounded ideas. Use for 'what should I improve', 'give me ideas', 'ideate', 'surprise me', or 'what would you change'.
- ▌ Ce Polish · sitaggart bundleStart the dev server, open the feature in a browser, and iterate on improvements together. Manual invocation only — type /ce-polish to run it.
- ▌ Ce Review · sitaggart bundleUse when the user asks for a code review, PR review, pre-commit audit, or review of a branch or local diff after implementation exists. Review-only; use document-review for plans and requirements.
- ▌ Ce Compound · sitaggart bundleDocument a recently solved problem into .ai/solutions/ and, when domain terms surface, CONCEPTS.md — the project's shared domain vocabulary.
- ▌ Ce Sessions · sitaggart bundleSearch coding agent session history across Claude Code, Codex, Cursor, OpenCode, and Hermes. Use for past work, previous attempts, or prior investigations.
- ▌ Ce Council · sitaggart bundleRun any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Use when the user asks for ce-council, council this, run the council, war room this, pressure-test this, stress-test this, debate this, validate this, get multiple perspectives, or when they are torn between meaningful options. Do not trigger on simple factual questions, trivial yes/no questions, implementation tasks, or casual should-I questions without a real tradeoff.
- ▌ Code Taste · sitaggart bundleApply TypeScript and React code-shape taste for implementation, review, refactor, and quality-gate tasks. Use when TypeScript or React changes involve typed contracts, helper boundaries, domain cores, IO or UI adapters, schemas, reducers, selectors, premature abstractions, speculative guards, maintainability smells, courier objects, JSX business logic, casts, useEffect, effect soup, or over-engineering.
- ▌ Onboarding · sitaggart bundleGenerate or refresh ONBOARDING.md for a codebase. Use for onboarding docs, new contributor docs, 'vonboard', or 'vonboarding'.
- ▌ Repoprompt · sitaggartUse RepoPromptCE / rpce-cli for token-efficient codebase exploration, planning, review, refactor context, and prompt exports.
- ▌ Git Commit Push Pr · sitaggart bundleCommit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.
- ▌ Ce Optimize · sitaggart bundleRun metric-driven optimization loops with experiments and hard gates. Use for search, clustering, build, prompt, or measurable quality tuning.
- ▌ Resolve Pr Feedback · sitaggart bundleResolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.
- ▌ Ce Decompose · sitaggartSplit or rebuild oversized diffs into reviewable pieces. Use for 'too big to review', 'break this down', 'decompose this', or 'split this up'.
- ▌ Prompt Check · sitaggartNormalize a consequential or ambiguous request when missing context, boundaries, or proof could materially change the work. Explicit invocation previews the improved prompt.
- ▌ Obsidian Vault · sitaggart bundleManage a local Obsidian vault from the command line using the Obsidian CLI. Use when the user wants to create, read, search, or organize notes, manage tasks, work with daily notes, handle properties/tags, or automate vault operations. Triggers on mentions of Obsidian, vault, notes, daily notes, or PKM workflows.
- ▌ Show Me Your Work · sitaggart 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.
- ▌ Technical Writing · sitaggart bundleLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
- ▌ Ce Brainstorm · sitaggart bundleExplore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.
- ▌ Ce Triage Pr Feedback · sitaggart bundleTriage PR review comments before implementation. Use when the user asks whether feedback is valid, what to fix or reject, or how to respond.
- ▌ Ce Conventions · sitaggart bundleShared conventions and references for the ce-* skill family. Shared by Engineering skills as a sibling directory; not invoked directly.
- ▌ Web Researcher · sitaggartPerform iterative web research and return structured external grounding. Use when planning or ideating needs prior art, competitor patterns, cross-domain analogies, or market signals from outside the repo. Prefer over ad hoc manual web searches for structured external context.
- ▌ Ce Quality Gate · sitaggartRun the changed-code quality gate after implementation: touched-file lint, format, type-check, tests, and code-shape checks. Use after ce-work writes code, before review or shipping, and when the user asks to make changed files clean.
- ▌ Architect · sitaggart 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.
- ▌ Codiff · sitaggart bundleOpen Codiff for a narrative code walkthrough, a blocking plan handoff, or a shared walkthrough URL. Use when the user writes "$codiff", "/codiff", "$codiff plan", "$codiff share", "show me codiff", "open Codiff", or asks to review a change or edit a plan in Codiff.
- ▌ Automate Me · sitaggart bundleUse 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 skill-creator + unslop, optionally pulling fresh evidence from recent transcripts.
- ▌ Browser Use · sitaggart bundleBuild or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.
- ▌ Control CLI · sitaggartBuild or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
- ▌ Interrogate · sitaggart 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.
- ▌ Make Bot UI · sitaggart bundleUse when building a custom UI (page, dashboard, buttons) that should wake a agent over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale. Checks native runtime support first.
- ▌ No Comments · sitaggart bundleSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- ▌ Poteto Mode · sitaggart 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.
- ▌ Verify This · sitaggartVerify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
- ▌ Ce Plan · sitaggart bundleCreate structured plans for multi-step tasks once the goal is clear enough to plan. Use after ce-brainstorm or ce-grill, or directly for clear planning requests. If the request has branchy product/scope ambiguity, run ce-grill first.
- ▌ Ce Work · sitaggart bundleExecute implementation work with a compact product-contract loop. Use when the user asks to build, fix, implement, polish, or finish a scoped task. Favor reasoning, prior art, smallest correct changes, focused tests, and real-surface proof. Do not run autonomous PR, CI, ticket, or residual-work pipelines.
- ▌ Agents Md · sitaggartThis skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Guides discovery of local skills and enforces minimal documentation style.
- ▌ How · sitaggart 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.
- ▌ Tdd · sitaggart bundleUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
- ▌ Why · sitaggart 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.
- ▌ Arena · sitaggart bundleSpawn 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 · sitaggart bundleFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
- ▌ Teach · sitaggart bundleExplain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
- ▌
- ▌ Recall · sitaggart bundleReconstruct 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.
- ▌
- ▌ Babysit Pr · sitaggartKeep an open pull request green and ready for its author to merge. Use when asked to babysit, watch, shepherd, or maintain a PR after it opens.
- ▌ Git Commit · sitaggartCreate a git commit with a clear, value-communicating Conventional Commit message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work.
- ▌ Reflect · sitaggart 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.
- ▌ Git Worktree · sitaggart bundleCreate an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-review` offers a worktree option.