supi-skills

Plugin supi-skills from marketplace supi in mrclrchtr/supi. Commands read from the repo's manifest — today.

Skills (24)

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• grill-me

  A relentless interview to sharpen a plan or design.

• grill-with-docs

  A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

• implement-spec

  Implement the result of /to-spec and /to-tickets in code.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• retro

  Conduct a retrospective on a coding session.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

• evaluate-code-tools

  Evaluate Code Intelligence (`code_*`) tools from benchmark, session usage, retrospectives, and open issues; judge one change or rank current weaknesses.

• pi-tui-design

  Create distinctive, crafted TUI components for pi using @earendil-works/pi-tui and @earendil-works/pi-coding-agent. Use when building interactive terminal UIs — custom components, overlays, dialogs, dashboards, widgets, data visualizations, animated elements, game-like interfaces, or any visual TUI

• release

  Prepare, curate, and ship a SuPi release from main.

• update-package-readme

  Update one SuPi package README and its direct user-facing Markdown references from installed Pi docs and verified package evidence.

• claude-md-improver

  Audit and improve existing CLAUDE.md files across a repository. Use for a deliberate, repo-wide quality review—not to record learnings from the current session.

• claude-md-revision

  Record durable, project-specific learnings from the current session in CLAUDE.md, .claude.local.md, or AGENTS.md—not general documentation, session summaries, or repo-wide audits.

• gather-retrospectives

  Gather retrospective feedback from past Pi sessions about a package, tool, or workflow. Use for historical retros and recurring friction, not assessment of only the current session.

• supi-setup

  Audit SuPi packages and configuration for the current project and propose fixes.

• commit

  Create a Git commit for the current task. Use when the user asks to commit changes.

• code-review

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them s

• implement

  Implement a piece of work based on a spec or set of tickets.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.