supipowers

Handle cross-platform compatibility including file paths, environment detection, platform-specific dependencies, and testing across Windows, macOS, and Linux. Use when dealing with platform-specific code or OS compatibility.

Use when creating, modifying, debugging, or scaffolding OMP extensions, slash commands, custom tools, event hooks, TUI primitives, ExtensionAPI integrations, .omp/extensions, .omp/commands, .omp/tools, package.json omp.extensions, or OMP lifecycle handlers.

Design Director state machine for `/supi:ui-design`. Drives 9 model-owned phases from scope selection through user review, producing a validated HTML mockup artifact.

Guides the harness-engineering pipeline — turn a codebase into one that resists agentic slop with agent-neutral docs, mechanically enforced architecture, and three runtime guardrails

Gray-area extraction stage — surfaces decisions the user must make before the plan can be authored, without expanding scope

Structured extraction of the user's seed prompt into a typed intake artifact — first stage of the UltraPlan authoring pipeline

Per-stack research stage — produces library choices, established patterns, pitfalls, and test architecture for one applicable stack

Requirement coverage checker — verifies every intake success criterion maps to a scenario, no scope creep exists, and deferred ideas are not silently included

Generic plan-review framing — what each checker catches, severity semantics, and the revision contract

Structural integrity checker — verifies every applicable stack has domains and scenarios, all fields are present, IDs are unique, and the dependency graph is acyclic

TDD ownership correctness checker — verifies executor/tester slot assignments match scenario levels and every scenario's first step is a failing test

Codebase reconnaissance stage — maps reusable assets, integration points, conventions, and test patterns for each applicable stack

Scenario decomposition stage — produces a complete authored.json and manifest.json draft from all prior pipeline artifacts

Guides collaborative brainstorming, design, and planning — from idea to implementation plan with review gates

Deep code review methodology for thorough quality assessment

Interactive guide for creating a new supipowers review agent from scratch

Systematic debugging — find root cause before attempting fixes, 4-phase investigation process

Critically assess PR review comments — verify, investigate ripple effects, then fix or reject with evidence

E2E QA strategy — flow-based product testing with disciplined triage, regression detection, and autonomous execution

Receiving code review feedback — verify before implementing, technical rigor not performative agreement

Test-driven development — write the test first, watch it fail, write minimal code to pass

Verification before completion — evidence before claims, always

Aggressively remove grammatical scaffolding LLMs reconstruct while preserving meaning-carrying content. Output may be fragments. Use when compressing text for prompts, reducing token count, preparing context for LLM input, or making documentation more token-efficient. Applies LLM-aware compression rules that delete predictable grammar while preserving semantics.

Write system prompts, tool docs, and agent definitions. Combines research-backed prompt engineering (+15-30% measured improvements) with project XML conventions. Covers tag hierarchy, structural templates, high-impact interventions, anti-patterns.