SHGrowth

SHGrowth/om-superpowers

Plugin Claude Code

Claude Code plugin for Open Mercato developers — 11 user-facing skills (plus on-demand specialist references) covering the full OM lifecycle from ideation through PR review.

SHGrowth/om-superpowers

Plugin Claude Code

Claude Code plugin for Open Mercato developers — 11 user-facing skills (plus on-demand specialist references) covering the full OM lifecycle from ideation through PR review.

SHGrowth/om-superpowers

Hook

Runs when a session starts on startup, clear and compact, executing run-hook.cmd. From SHGrowth/om-superpowers.

SHGrowth/om-superpowers

Skill Claude CodeCodex

Resume an in-progress PR started by auto-create-pr. Claims the PR, checks out the branch in an isolated worktree, picks up from the first unchecked Progress step, and runs the same validation gate + label discipline. Usage — /auto-continue-pr .

SHGrowth/om-superpowers

Skill Claude CodeCodex

Execute an autonomous agent task end-to-end and deliver it as a GitHub PR against develop. Drafts an execution plan with a Progress checklist, implements phase-by-phase in an isolated worktree with incremental commits, runs the validation gate (typecheck, unit tests, i18n, build). Resumable via auto-continue-pr.

SHGrowth/om-superpowers

Skill Claude CodeCodex

Review or re-review a GitHub PR by number in an isolated worktree. Fetch the PR, run the code-review skill, submit approve/request-changes, manage labels. Offers an optional autofix flow that iterates conflicts, fixes, tests, typecheck, re-review until merge-ready. Usage — /auto-review-pr .

SHGrowth/om-superpowers

Skill Claude CodeCodex

Review code changes for Open Mercato compliance — architecture, security, conventions, quality. Covers module structure, naming, data security, UI patterns, event/cache/queue rules, and anti-patterns. Use for PR reviews, audits, diffs, or commit reviews.

SHGrowth/om-superpowers

Skill Claude CodeCodex

Open Mercato architecture skill — gap analysis, BC/risk analysis, skill-corpus audits, upstream bug triage, and orchestrating spec writing or implementation. Routes via Task Router. Triggers — "does OM do X", "analyze spec", "BC analysis", "review skills", "OM upstream bug", "write specs", "implement specs".

SHGrowth/om-superpowers

Skill Claude CodeCodex

OM design-system enforcement + backend admin page builder — flag hardcoded colors/typography/raw HTML controls, build DS-compliant CRUD/data-table/form pages, run DS health checks. Triggers — "DS review", "build admin page", "data table", "CRUD interface", "migrate colors", "DS health".

SHGrowth/om-superpowers

Skill Claude CodeCodex

Implement OM specs end-to-end (or by phase) — coordinated subagents, code-review + tests gated per phase. Loads references for module scaffolding, data-model design, system extension (UMES), integration builders. Triggers — "implement spec", "create module", "design entity", "extend module", "build integration".

SHGrowth/om-superpowers

Skill Claude CodeCodex

Run and create QA integration tests (Playwright TypeScript) — execute the full suite, convert optional markdown scenarios, generate tests from specs or features. Triggers — "run integration tests", "test this feature", "create test for", "QA tests".

SHGrowth/om-superpowers

Skill Claude CodeCodex

Use when defining business requirements for a new app or feature — BEFORE any spec or code exists. Triggers on "what should we build", "define requirements", "create app spec", or when user stories lack success criteria. Also use when reviewing existing specs for gaps.

SHGrowth/om-superpowers

Skill Claude CodeCodex

Diagnose and fix common issues in Open Mercato standalone apps — errors, modules not loading, widgets missing, failed migrations, build errors. Triggers — "error", "not working", "broken", "fix", "debug", "404", "500", "module not found". When the trace points into nodemodules/@open-mercato/, STOP and route to om-cto…

SHGrowth/om-superpowers

Skill Claude CodeCodex

Use when defining UI architecture, reviewing page layouts, navigation, widget placement, or user flow. Triggers — "what should the user see", "where does this go in the UI", "what pages do we need", or App Spec §3.5 UI Architecture reviews.