open-mercato

@open-mercato source repo

132 skills
0 followers
last month last updated

▌
Troubleshooter 2 · open-mercato bundle
Diagnose and fix common issues in Open Mercato standalone apps. Use when encountering errors, unexpected behavior, modules not loading, widgets not appearing, migrations failing, build errors, or any "it doesn't work" situation. Triggers on "error", "not working", "broken", "fix", "debug", "why isn't", "can't", "fails", "crash", "missing", "404", "500", "module not found", "widget not showing".

5 installs
▌
Module Scaffold 2 · open-mercato bundle
Scaffold a new module from scratch with all required files and conventions. Use when creating a new module, adding a new entity with CRUD, or bootstrapping module features (API routes, backend pages, DI, ACL, events, search). Triggers on "create module", "new module", "scaffold module", "add module", "bootstrap module", "generate module".

5 installs
▌
Backend UI Design 2 · open-mercato bundle
Design and implement consistent backend/backoffice interfaces using @open-mercato/ui. Use when building admin pages, CRUD interfaces, data tables, forms, detail pages, or any backoffice UI.

5 installs
▌
Data Model Design 2 · open-mercato bundle
Design entities, relationships, and manage the migration lifecycle. Use when planning a data model, designing entities, choosing relationship patterns, adding cross-module references, or managing database migrations. Triggers on "design entity", "data model", "add entity", "database schema", "migration", "relationship", "many-to-many", "junction table", "foreign key", "jsonb", "add column".

5 installs
▌
Integration Builder 2 · open-mercato bundle
Build integration provider packages for the Open Mercato Integration Marketplace. Use when creating new external integrations (payment gateways, shipping carriers, data sync connectors, communication channels, storage providers, webhook endpoints). Handles npm package scaffolding, adapter implementation, credentials, widget injection, webhook processing, health checks, i18n, and tests. Triggers on "build integration", "create integration", "add provider", "new connector", "integrate with", "add stripe/paypal/dhl/sendgrid" etc.

3 installs
▌
Code Review 2 · open-mercato bundle
Review code changes for architecture, security, conventions, and quality compliance. Use when reviewing pull requests, code changes, or auditing code quality.

3 installs
▌
Spec Writing 3 · open-mercato bundle
Guide for creating high-quality specifications for test. Use when starting a new SPEC or reviewing specs against architectural standards.

5 installs
▌
Om Code Review 2 · open-mercato
Open Mercato repo-local extension of the shared `om-code-review` skill (installed from open-mercato/skills into .agents/skills/). Adds the Docker-vs-local gate runner detection, the template parity gate, Open Mercato layer classification, and the repo's severity taxonomy on top of the shared workflow.

6 installs
▌
Om Pr Autopilot 2 · open-mercato
Open Mercato repo-local extension of the shared `om-pr-autopilot` skill (installed from open-mercato/skills into .agents/skills/). Adds this repo's label taxonomy and QA gate, the concrete diff-scope classification, what a triage-permission `403` means for the claim when the active account hits one, and the install command for a missing companion skill.

4 installs
▌
Om Spec Writing 2 · open-mercato bundle
Guide for creating high-quality, architecturally compliant specifications for Open Mercato. Use when starting a new SPEC or reviewing specs against "Martin Fowler" staff-engineer standards.

3 installs
▌
Om Prepare Issue 2 · open-mercato
Open Mercato repo-local extension of the shared `om-prepare-issue` skill (installed from open-mercato/skills into .agents/skills/). Adds the --enterprise spec scope, duplicate-spec checks across both spec trees, and the om-implement-spec/om-auto-fix-issue pickup path.

3 installs
▌
Om Auto Review Pr 3 · open-mercato
Open Mercato repo-local extension of the shared `om-auto-review-pr` skill (installed from open-mercato/skills into .agents/skills/). Makes the review GitHub-checks-first (local validation only as a narrow fallback) and keeps this repo's stricter verdict rule (Medium findings request changes).

5 installs
▌
Om Prepare Test Env 3 · open-mercato
Repo-local extension of the shared om-prepare-test-env skill (installed in .agents/skills/). Adds Open Mercato monorepo environment specifics — the generated entrypoint scripts, ephemeral runner commands, reuse TTL semantics, owner-lock teardown, and the env-block contract — on top of the shared skill's workflow. Local rules win on repo specifics only; this file never relaxes the shared skill's safety rules.

5 installs
▌
Om Integration Tests 2 · open-mercato
Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Defers all environment boot/reuse to the `om-prepare-test-env` skill and attaches to the shared descriptor it writes. Use when the user says "run integration tests", "test this feature", "create test for", "convert test case", "run QA tests", or "integration test".

7 installs
▌
Om Auto Create Pr Loop 2 · open-mercato
Open Mercato repo-local extension of the shared `om-auto-create-pr-loop` skill (installed from open-mercato/skills into .agents/skills/). Pins the spec-completion gates (OM integration suites + om-ds-guardian) and the .ai/specs/enterprise spec scope.

5 installs
▌
Om Auto Continue Pr Loop 2 · open-mercato
Open Mercato repo-local extension of the shared `om-auto-continue-pr-loop` skill (installed from open-mercato/skills into .agents/skills/). Pins the spec-completion gates (OM integration suites + om-ds-guardian), the .ai/specs/enterprise spec scope, and legacy flat-plan resume support.

5 installs
▌
Om Auto Update Changelog 2 · open-mercato
> **Repo-local override.** This file extends the external `om-auto-update-changelog` skill for Open Mercato release preparation. The external workflow remains authoritative except where this override explicitly broadens the release artifact set or corrects a release-window / credit-resolution default that is wrong for this repository.

5 installs
▌
Om Followup Issue From Pr 2 · open-mercato
Open Mercato repo-local extension of the shared `om-followup-issue-from-pr` skill (installed from open-mercato/skills into .agents/skills/). Pins design-doc detection to .ai/specs/ (+ enterprise/), keeps the `enterprise` label, and hands specs off to om-implement-spec.

5 installs
▌
Om Auto Create Pr 2 · open-mercato
> **Repo-local override.** This folder is a repo-local override for the external `om-auto-create-pr` skill installed from `open-mercato/skills` via `yarn install-skills`. The external skill reads this file in place and applies the overrides below **on top of** its built-in workflow — it is never installed as a standalone skill. Everything here adapts the skill from the Open Mercato monorepo to a standalone app scaffolded by `create-mercato-app`.

5 installs
▌
Om Auto Fix Issue 2 · open-mercato
> **Repo-local override.** This folder is a repo-local override for the external `om-auto-fix-issue` skill installed from `open-mercato/skills` via `yarn install-skills`. The external skill reads this file in place and applies the overrides below **on top of** its built-in workflow — it is never installed as a standalone skill. Everything here adapts the skill from the Open Mercato monorepo to a standalone app scaffolded by `create-mercato-app`.

4 installs
▌
Om Auto Continue Pr 2 · open-mercato
> **Repo-local override.** This folder is a repo-local override for the external `om-auto-continue-pr` skill installed from `open-mercato/skills` via `yarn install-skills`. The external skill reads this file in place and applies the overrides below **on top of** its built-in workflow — it is never installed as a standalone skill. Everything here adapts the skill from the Open Mercato monorepo to a standalone app scaffolded by `create-mercato-app`.

5 installs
▌
Om Auto Implement Spec 2 · open-mercato
> **Repo-local override.** This folder extends the external `om-auto-implement-spec` skill installed from `open-mercato/skills`. Apply these standalone readiness and no-remote rules on top of the external workflow; do not install this file as a replacement skill.

5 installs
▌
System Extension 2 · open-mercato bundle
Extend core modules using the Universal Module Extension System (UMES). Use when adding columns/fields/filters to existing tables/forms, enriching API responses, intercepting API routes, blocking/validating mutations, replacing UI components, injecting menu items, or reacting to domain events. Triggers on "extend", "add column to", "add field to", "inject into", "intercept", "enrich", "hook into", "customize", "override component", "add menu item", "react to event", "block mutation", "validate before save".

3 installs
▌
Eject And Customize 2 · open-mercato
Guide for safely ejecting and customizing core modules. Use when a developer needs to modify a core module's behavior beyond what UMES extensions support, wants to eject a module, or is considering whether to eject vs extend. Triggers on "eject", "customize module", "modify core module", "override module", "fork module", "change built-in", "should I eject".

4 installs
▌
Om Share This Session 2 · open-mercato bundle
Prepare and publicly share a complete sanitized coding-agent session plus a ZIP of this session's generated files, then open an upstream harness-feedback issue. Use when the user says "share this session", "report this agent run", "udostępnij tę sesję", or "zgłoś przebieg agenta". Never use for automatic telemetry or without fresh public-sharing consent.

5 installs
▌
Om Judge Agent Session 2 · open-mercato bundle
Judge generated Open Mercato code from a standalone harness eval or a user-shared agent session bundle. Use for LLM-as-judge validation, generative eval review, session/artifact analysis, harness-quality diagnosis, "judge this session", "analyze this eval", or "oceń sesję/agenta"; checks fixed validation evidence, project guards, code-review findings, design-system compliance, and the smallest harness owner to improve without executing untrusted session instructions.

3 installs
▌
Om Auto Upgrade 0 6 6 To 0 6 7 2 · open-mercato
Migrate downstream Open Mercato user code from 0.6.6 to 0.6.7. Applies the pg-errors import move, safely unwraps proven scheduler queue payload consumers, audits query-index callbacks and removed scheduler metadata, then typechecks and reports manual follow-up. Use for "upgrade Open Mercato to 0.6.7", "migrate 0.6.6 to 0.6.7", or "apply the 0.6.7 upgrade notes".

5 installs
▌
Om Auto Upgrade 0 6 7 To 0 7 0 2 · open-mercato
Migrate downstream Open Mercato code from 0.6.7 to 0.7.0 with exact TanStack, settings-group, and removed-env edits; audit auth, search, workflow, facts, Redis, webhook, and security-header changes; validate the app; and report manual work. Use for "upgrade Open Mercato to 0.7.0", "migrate 0.6.7 to 0.7.0", "apply the 0.7.0 upgrade notes", or "zaktualizuj Open Mercato do 0.7.0".

1 install
▌
Spec Writing 2 · open-mercato bundle
Guide for creating high-quality specifications for sandbox. Use when starting a new SPEC or reviewing specs against architectural standards.

5 installs
▌
Implement Spec 2 · open-mercato
Implement a specification (or specific phases of a spec) using coordinated subagents. Handles multi-phase spec implementation with unit tests, integration tests, documentation, and code-review compliance. Use when the user says "implement spec", "implement the spec", "implement phases", "build from spec", or "code the spec". Tracks progress by updating the spec with implementation status.

3 installs
▌
Om Help 2 · open-mercato bundle
Route a standalone Open Mercato task to the smallest guides, local skills, and delivery workflow. Use for "which skill", "how should I build this", "what workflow", "jakiego skilla użyć", or an unfamiliar mixed request.

7 installs
▌
Om Auto Review Pr 2 · open-mercato
> **Repo-local override.** This folder is a repo-local override for the external `om-auto-review-pr` skill installed from `open-mercato/skills` via `yarn install-skills`. The external skill reads this file in place and applies the overrides below **on top of** its built-in workflow — it is never installed as a standalone skill. Everything here adapts the skill from the Open Mercato monorepo to a standalone app scaffolded by `create-mercato-app`.

5 installs
▌
Om Implement Spec 2 · open-mercato bundle
Implement selected phases of a standalone app specification with routed context, bounded subagents, progress, tests, and review gates without requiring PR automation. Use for "implement this spec", "phase 2", "continue spec", "wdroż specyfikację", or a multi-phase local delivery.

5 installs
▌
Om Create AI Agent 2 · open-mercato bundle
Build or extend a typed standalone module AI agent/tool, approval-gated mutation, UI part, orchestrator file agent/subagent, attachment/artifact flow, or AI override. Use for "create AI agent", "add AI tool", "agent orchestrator", "subagent", "AI workflow", or "stwórz agenta AI".

5 installs
▌
Om Prepare Test Env 2 · open-mercato
Repo-local extension of the shared om-prepare-test-env skill. Adds this standalone Open Mercato app's environment specifics — the mercato CLI ephemeral runner commands, state-file semantics, readiness-probe contract, and the rule that generated entrypoint scripts stay machine-local — on top of the shared skill's workflow. Local rules win on repo specifics only; this file never relaxes the shared skill's safety rules.

5 installs
▌
Om Backend UI Design 2 · open-mercato bundle
Build or change standalone backend, frontend, and portal pages with CrudForm, DataTable, navigation, translations, accessibility, conflicts, and the design system. Use for "add page", "form/table", "navigation", "translation", "portal page", "UI", or "zbuduj widok".

5 installs
▌
Om Integration Builder 2 · open-mercato bundle
Build standalone email, shipping, payment, data-sync, webhook, storage, import/export, and external API provider integrations with packaging, encrypted credentials, idempotency, retries, cursor safety, health, and tests. Use for "build integration", "payment/shipping/email provider", "DataSyncAdapter", "webhook", or "integracja".

4 installs
▌
Om Auto Upgrade 0 4 10 To 0 5 0 2 · open-mercato
Migrate a standalone Open Mercato app from framework 0.4.10 to 0.5.0. This release is the biggest Open Mercato release so far and bundles 250+ post-Hackathon fixes plus several important dependency upgrades, so this skill acts as the executable companion to the 0.5.0 upgrade notes. It mechanically applies the documented codemods for the 0.4.10 → 0.5.0 window — Meilisearch class rename, Stripe API-version typing, lucide-react brand-icon removals and metadata-icon safety fixes, react-markdown className wrap, cron-parser `CronExpressionParser.parse` rename, @simplewebauthn Uint8Array narrowing, react-email CLI rename, plus the Jest ESM allow-list. Runs inside the user's app, detects which patterns are actually in use, edits files in place, typechecks, and reports what was migrated and what still needs a human eye. Use when a user asks to "upgrade my Open Mercato project from 0.4.10 to 0.5.0", "bump open-mercato to 0.5.0", or "apply the 0.5.0 upgrade notes".

5 installs
▌
System Extension · open-mercato bundle
Extend core modules using the Universal Module Extension System (UMES). Use when adding columns/fields/filters to existing tables/forms, enriching API responses, intercepting API routes, blocking/validating mutations, replacing UI components, injecting menu items, or reacting to domain events. Triggers on "extend", "add column to", "add field to", "inject into", "intercept", "enrich", "hook into", "customize", "override component", "add menu item", "react to event", "block mutation", "validate before save".

5 installs
▌
Eject And Customize · open-mercato
Guide for safely ejecting and customizing core modules. Use when a developer needs to modify a core module's behavior beyond what UMES extensions support, wants to eject a module, or is considering whether to eject vs extend. Triggers on "eject", "customize module", "modify core module", "override module", "fork module", "change built-in", "should I eject".

5 installs
▌
Spec Writing · open-mercato bundle
Guide for creating high-quality specifications for community modules in the official-modules repo. Use when starting a new SPEC, designing a new module, or reviewing an existing spec. Follows the same "Martin Fowler" staff-engineer standards as the core repo. Triggers on "write spec", "new spec", "design module", "spec for", "create spec".

5 installs
▌
Implement Spec · open-mercato bundle
Implement a specification (or specific phases) for a community module package in the official-modules repo. Handles multi-phase implementation with unit tests, sandbox verification, and code-review compliance. Use when the user says "implement spec", "implement SPEC-XXX", "implement phases", "build from spec", or "code the spec". Tracks progress by updating the spec with implementation status.

3 installs
▌
Scaffold Module · open-mercato
Scaffold a new community module package in the official-modules monorepo. Use when creating a new @open-mercato/* npm package from scratch, starting a new module, or when implement-spec needs a package skeleton before filling in business logic. Triggers on "scaffold module", "create module", "new module package", "new package", "add community module".

5 installs
▌
Code Review · open-mercato bundle
Review code changes for architecture, security, conventions, and quality compliance. Use when reviewing pull requests, code changes, or auditing code quality.

5 installs
▌
Auto Create Pr · open-mercato bundle
Execute an arbitrary autonomous agent task end-to-end and deliver it as a GitHub pull request against develop. Start by drafting an execution plan in .ai/runs/ that includes a Progress checklist, commit it on a fresh task branch in an isolated worktree, implement the work phase-by-phase with incremental commits, update the Progress checklist after every phase, optionally honor one or more external reference skills passed by URL, run the full validation gate (typecheck, unit tests, i18n, build) for any code changes, and open a PR with the correct pipeline labels. Resumable via the auto-continue-pr skill.

5 installs
▌
Auto Review Pr · open-mercato bundle
Review or re-review a GitHub pull request by number in an isolated git worktree. Fetch the specific PR from GitHub, run the full code-review skill, submit approve or request-changes, manage labels, and if blockers remain offer an optional autofix and fix-forward flow that iterates through conflict resolution, code fixes, unit tests, typecheck, and re-review until the PR is merge-ready or a real blocker remains. Usage - /auto-review-pr <PR-number>

3 installs
▌
Troubleshooter · open-mercato bundle
Diagnose and fix common issues in Open Mercato standalone apps. Use when encountering errors, unexpected behavior, modules not loading, widgets not appearing, migrations failing, build errors, or any "it doesn't work" situation. Triggers on "error", "not working", "broken", "fix", "debug", "why isn't", "can't", "fails", "crash", "missing", "404", "500", "module not found", "widget not showing".

5 installs
▌
Auto Fix Github · open-mercato bundle
Fix a GitHub issue by number from the current repository. First check whether the issue is already solved or already has an open solution, then use an isolated git worktree to implement the minimal fix, add unit tests, run code review and backward-compatibility checks, run validation including i18n, typecheck, unit tests, and other required checks, then push a branch and open a pull request with a full description linked to the original issue.

4 installs
▌
Module Scaffold · open-mercato bundle
Scaffold a new module from scratch with all required files and conventions. Use when creating a new module, adding a new entity with CRUD, or bootstrapping module features (API routes, backend pages, DI, ACL, events, search). Triggers on "create module", "new module", "scaffold module", "add module", "bootstrap module", "generate module".

5 installs
▌
Auto Continue Pr · open-mercato bundle
Resume an in-progress pull request that was started by the auto-create-pr skill. Given a PR number, claim the PR under the in-progress lock protocol, check its branch out into an isolated git worktree, locate the execution plan linked from the PR body, read its Progress checklist, and continue execution from the first unchecked step with incremental commits and progress updates until the PR is complete. Runs the same validation gate (typecheck, unit tests, i18n, build) and label discipline as auto-create-pr. Usage - /auto-continue-pr <PR-number>

5 installs
▌
Backend UI Design · open-mercato bundle
Design and implement consistent backend/backoffice interfaces using @open-mercato/ui. Use when building admin pages, CRUD interfaces, data tables, forms, detail pages, or any backoffice UI.

4 installs
▌
Data Model Design · open-mercato bundle
Design entities, relationships, and manage the migration lifecycle. Use when planning a data model, designing entities, choosing relationship patterns, adding cross-module references, or managing database migrations. Triggers on "design entity", "data model", "add entity", "database schema", "migration", "relationship", "many-to-many", "junction table", "foreign key", "jsonb", "add column".

3 installs
▌
Integration Tests · open-mercato
Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Use when the user says "run integration tests", "test this feature", "create test for", "convert test case", "run QA tests", or "integration test".

5 installs
▌
Auto Create Pr Loop · open-mercato
Advanced `auto-create-pr` workflow for long, multi-step spec implementations that need resumability and strict step tracking. Creates a run folder under `.ai/runs/<date>-<slug>/` with `PLAN.md`, `HANDOFF.md`, and `NOTIFY.md`, executes one lean commit per task-table step, batches verification into `checkpoint-<N>-checks.md` every 5 steps (with focused integration tests + screenshots when UI was touched), runs the full validation gate plus full/standalone integration suites and ds-guardian at spec completion, and opens a PR with the correct labels. Use the original `auto-create-pr` for small fixes.

5 installs
▌
Integration Builder · open-mercato bundle
Build integration provider packages for the Open Mercato Integration Marketplace. Use when creating new external integrations (payment gateways, shipping carriers, data sync connectors, communication channels, storage providers, webhook endpoints). Handles npm package scaffolding, adapter implementation, credentials, widget injection, webhook processing, health checks, i18n, and tests. Triggers on "build integration", "create integration", "add provider", "new connector", "integrate with", "add stripe/paypal/dhl/sendgrid" etc.

4 installs
▌
Trim Unused Modules · open-mercato
Propose disabling modules in src/modules.ts that the current standalone project does not actually use. Intended to be offered after the user adds a new custom module, because a fresh create-mercato-app scaffold enables every built-in module (classic mode) and that is rarely what the project actually needs in production.

1 install
▌
Auto Continue Pr Loop · open-mercato
Advanced `auto-continue-pr` workflow for PRs started by `auto-create-pr-loop`. Claims the PR, re-enters an isolated worktree, resumes from the first non-done row in `.ai/runs/<date>-<slug>/PLAN.md`, executes lean per-step commits, batches verification into `checkpoint-<N>-checks.md` every 5 resumed steps (with focused integration tests + screenshots when UI was touched), runs the full validation gate plus full/standalone integration suites and ds-guardian at spec completion, and preserves the run-folder and label contract. Use the original `auto-continue-pr` for simple `auto-create-pr` runs.

5 installs
▌
Auto Upgrade 0 4 10 To 0 5 0 · open-mercato
Migrate a standalone Open Mercato app from framework 0.4.10 to 0.5.0. This release is the biggest Open Mercato release so far and bundles 250+ post-Hackathon fixes plus several important dependency upgrades, so this skill acts as the executable companion to the 0.5.0 upgrade notes. It mechanically applies the documented codemods for the 0.4.10 → 0.5.0 window — Meilisearch class rename, Stripe API-version typing, lucide-react brand-icon removals and metadata-icon safety fixes, react-markdown className wrap, cron-parser `CronExpressionParser.parse` rename, @simplewebauthn Uint8Array narrowing, react-email CLI rename, plus the Jest ESM allow-list. Runs inside the user's app, detects which patterns are actually in use, edits files in place, typechecks, and reports what was migrated and what still needs a human eye. Use when a user asks to "upgrade my Open Mercato project from 0.4.10 to 0.5.0", "bump open-mercato to 0.5.0", or "apply the 0.5.0 upgrade notes".

4 installs
▌
Om Help · open-mercato bundle
Open Mercato workflow navigator. Use when a developer or agent asks: "what should I do now?", "which skill should I use?", "where do I start?", "next steps?", "I'm lost", "what comes after X?", "how do I add/create/build Y in Open Mercato?", "where does Z go?", "what's the order for a feature/bugfix/PR?", "how do I do X" (module, search, RBAC, events, commands, migrations, UI, AI agents, integrations). Covers both orientation (navigation mode) and technical how-to (knowledge mode).

3 installs
▌
Om Fix Specs · open-mercato bundle
Normalize spec filenames in .ai/specs and .ai/specs/enterprise to the date+slug convention. Use this when legacy `SPEC-*` / `SPEC-ENT-*` names need to be cleaned up, when filename collisions appear after dropping numeric prefixes, or when links must be updated after normalization.

5 installs
▌
Om Smart Test · open-mercato bundle
Run only the tests affected by changed code. Use when the user says "run affected tests", "run smart tests", "test only what changed", "run tests for this PR", "run tests for my changes", "selective tests", or asks to run tests without running the full suite.

5 installs
▌
Om Ds Guardian · open-mercato bundle
Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill whenever you are building or reviewing Open Mercato UI.

3 installs
▌
Om Gap Analysis · open-mercato bundle
Grounded platform gap analysis at engagement scale — turn a folder of client docs into an Epic/Story tree where every coverage verdict is re-run by executable gates against a validated checkout of the platform, scored in atomic commits, license-tier-tagged, and synthesized into a client-facing summary + backlog. Use when the user says "gap analysis", "what does the platform already cover", "coverage report", "analiza luk", "co platforma już pokrywa", "ile z tego już jest w platformie". This skill verifies coverage against the platform's code; it does not author requirements or specs — use the spec-writing skills for that.

3 installs
▌
Om Skill Creator · open-mercato bundle
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

4 installs
▌
Om Implement Spec · open-mercato bundle
Implement a specification (or specific phases) using coordinated subagents with unit tests, integration tests, docs, and code-review compliance. Tracks progress by updating the spec. Triggers on "implement spec", "implement phases", "build from spec", "code the spec".

4 installs
▌
Om Auto Publish Pr · open-mercato
Publish pkg.pr.new package previews for a same-repository Open Mercato PR by dispatching the Package Previews GitHub Actions workflow with gh. Use when a maintainer asks to publish, republish, or trigger a PR package preview. Does not publish npm snapshots.

3 installs
▌
Om Auto Sec Report · open-mercato
Driver that loops `om-auto-sec-report-pr` across a window (date, PR-number floor, branch, spec, or default last 7 days of merged PRs) and aggregates findings into one docs-only PR against `develop`. Writes markdown + HTML under `.ai/analysis/` with a top-level "Next steps — go deeper" list.

5 installs
▌
Om Create AI Agent · open-mercato
Build, override, or extend a typed Open Mercato AI agent (chat or structured-object) using the unified AI framework — declare `ai-agents.ts`, register tool packs via `defineAiTool`, patch existing agents with `aiAgentExtensions`, configure agentic loop controls (`loop.stopWhen` / `loop.prepareStep` / `loop.budget` / `executionEngine`), gate mutations through the approval contract, wire ACL features, and embed `<AiChat>` into a backoffice or portal page. Works in both the monorepo (`packages/<x>/src/modules/<module>/`) and standalone projects (`apps/<app>/src/modules/<module>/` or `node_modules/@open-mercato/<package>` consumers). Triggers on "create AI agent", "add AI agent", "build AI assistant", "extend AI agent", "override AI agent", "add tool to existing agent", "wire ai-agents.ts", "add ai-tools.ts", "embed AiChat", "agent for module", "agentic loop", "configure loop budget", "tool-loop-agent".

3 installs
▌
Om App Spec Writing · open-mercato bundle
Write and review a business-level App Spec — domain model, workflows with ROI, user stories with failure paths, platform gap analysis in atomic commits, and a phased rollout — BEFORE any feature spec or code exists. One level above om-spec-writing, which decomposes the finished App Spec into feature specs. Use when the user says "create an app spec", "define business requirements", "what should we build", "napisz app spec", "zdefiniuj wymagania biznesowe", "co powinniśmy zbudować".

2 installs
▌
Om Create Agents Md · open-mercato
Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, the Always/Ask First/Never/Validation Commands boundary structure, MUST-style rules, checklists, and consistent structure across all agent guidelines.

3 installs
▌
Om Mockup Prototype · open-mercato bundle
Build a clickable, commentable prototype for an Open Mercato backend or backoffice flow from requirements that already contain user stories. Use for interactive admin-flow prototypes, backend click-throughs, presentation walkthroughs, and anchored pre-implementation feedback. Do not use for generic design-system mockups, portal, storefront, or public frontend work; route those requests to the authoritative surface workflow.

4 installs
▌
Om Auto QA Scenarios · open-mercato
Generate a human QA report for a window of merged PRs (date floor, PR-number floor, or default last 7 days) and ship it as a docs-only PR against `develop`. Groups work into P0/P1/P2 testing routes with click paths, verification points, and risk callouts. Writes markdown + HTML under `.ai/analysis/`. Hands off to `om-auto-continue-pr` if it cannot finish in one pass.

3 installs
▌
Om Backend UI Design · open-mercato bundle
Design and implement consistent, production-grade backend/backoffice interfaces using the @open-mercato/ui component library. Use this skill when building admin pages, CRUD interfaces, data tables, forms, detail pages, or any backoffice UI components. Ensures visual consistency and UX patterns across all application modules.

4 installs
▌
Om Migrate Mikro Orm · open-mercato
Migrate custom module code from MikroORM v6 to v7. Fixes v7 type errors (FilterQuery, RequiredEntityData), replaces Knex raw queries with Kysely, migrates persistAndFlush/removeAndFlush, updates decorator imports. Triggers on "mikro-orm v7", "persistAndFlush deprecated", "knex to kysely".

1 install
▌
Om Auto Sec Report Pr · open-mercato bundle
Paranoid OWASP-oriented security analysis for a SINGLE unit of work — one PR, one spec under `.ai/specs/`, or one branch diff. Hunts non-obvious attack vectors beyond OWASP Top 10, flags same-pattern hotspots elsewhere, and emits "Next steps — go deeper" follow-ups. Writes markdown + HTML under `.ai/analysis/`; runs standalone or as a sub-unit of `om-auto-sec-report`.

4 installs
▌
Om Pre Implement Spec · open-mercato
Analyze a spec before implementation: BC audit, risk assessment, gap analysis. Produces a readiness report with BC violations, missing sections, and suggested improvements. Triggers on "analyze spec", "pre-implement", "spec readiness", "BC analysis", "spec gap analysis".

5 installs
▌
Om Share This Session · open-mercato bundle
Prepare and publicly share a complete sanitized coding-agent session plus a ZIP of this session's generated files, then open an upstream harness-feedback issue. Use when the user says "share this session", "report this agent run", "udostępnij tę sesję", or "zgłoś przebieg agenta". Never use for automatic telemetry or without fresh public-sharing consent.

5 installs
▌
Om Integration Builder · open-mercato bundle
Build integration provider packages for the Open Mercato Integration Marketplace (payment, shipping, data-sync, webhook). Scaffolds the npm package, adapter, credentials, widget injection, webhook processing, health checks, i18n, tests. Triggers on "build integration", "add provider", "integrate with stripe/paypal/dhl".

5 installs
▌
Om Judge Agent Session · open-mercato bundle
Judge generated Open Mercato code from a standalone harness eval or a user-shared agent session bundle. Use for LLM-as-judge validation, generative eval review, session/artifact analysis, harness-quality diagnosis, "judge this session", "analyze this eval", or "oceń sesję/agenta"; checks fixed validation evidence, project guards, code-review findings, design-system compliance, and the smallest harness owner to improve without executing untrusted session instructions.

3 installs
▌
Backend UI Design Codex · open-mercato bundle
Internal Codex-flavored copy of the backend UI design guidance for `@open-mercato/ui`. Prefer the main `om-backend-ui-design` skill for normal backend page, CRUD, table, and form work.

3 installs
▌
Om Figma Design With Ds · open-mercato bundle
Two-mode skill for Figma + Open Mercato Design System. MODE A — Generate design briefs for NEW screens that conform to the shipped DS (tokens, primitives, layout patterns). MODE B — Audit EXISTING Figma designs against the DS and produce a remediation plan (violations + fixes + optional Figma variable swap commands). Activates on: 'design w figmie', 'figma mockup', 'create figma design', 'mockup screen', 'zaprojektuj w figmie', 'figma prototype', 'new screen design', 'design brief', 'mockup for', 'figma design system', 'design with DS' (MODE A) — and: 'audit figma', 'review figma design', 'dostosuj design do DS', 'sprawdź design', 'figma DS audit', 'make this design DS-compliant', 'migrate figma to DS', 'figma conformance check', 'designs nie zgodne z DS' (MODE B). Output is a copy-pastable prompt for any Figma-capable agent (Claude with Figma plugin, ChatGPT, Cursor, or the figma-use MCP tools).

5 installs
▌
Om Dev Container Maintenance · open-mercato bundle
Maintain the VS Code Dev Container setup for Open Mercato. MUST use for ANY change to `.devcontainer/` files. Also use when the container fails to build/start, services inside misbehave, or "works locally but not in dev container". Triggers on "dev container", "devcontainer", ".devcontainer".

3 installs
▌
Om Refresh Standalone Harness · open-mercato bundle
Refresh the standalone-app AI harness from an explicit local Git release range. Use for "refresh standalone harness", "release harness audit", "scan release range", `--from/--to`, "odśwież harness", or when platform work changes a module, UMES extension point, installed public contract, generator surface, or release.

5 installs
▌
Om Auto Upgrade 0 6 6 To 0 6 7 · open-mercato
Migrate downstream Open Mercato user code from 0.6.6 to 0.6.7. Applies the pg-errors import move, safely unwraps proven scheduler queue payload consumers, audits query-index callbacks and removed scheduler metadata, then typechecks and reports manual follow-up. Use for "upgrade Open Mercato to 0.6.7", "migrate 0.6.6 to 0.6.7", or "apply the 0.6.7 upgrade notes".

3 installs
▌
Om Auto Upgrade 0 6 7 To 0 7 0 · open-mercato
Migrate downstream Open Mercato code from 0.6.7 to 0.7.0 with exact TanStack, settings-group, and removed-env edits; audit auth, search, workflow, facts, Redis, webhook, and security-header changes; validate the app; and report manual work. Use for "upgrade Open Mercato to 0.7.0", "migrate 0.6.7 to 0.7.0", "apply the 0.7.0 upgrade notes", or "zaktualizuj Open Mercato do 0.7.0".

4 installs
▌
Om Auto Upgrade 0 4 10 To 0 5 0 · open-mercato
Migrate a downstream Open Mercato user codebase from 0.4.10 to 0.5.0. Executable companion to UPGRADE_NOTES.md — detects which codemod patterns are in use, applies them in place, typechecks, and reports what still needs human review. Triggers on "upgrade open-mercato to 0.5.0", "bump to 0.5.0", or "apply UPGRADE_NOTES migrations".

5 installs
▌
Om Build Workflow · open-mercato bundle
Build or extend standalone business workflows, activities, event triggers, durable user tasks, compensation, output paths, idempotency, and live progress. Use for "add workflow", "custom activity", "CALL_API", "approval task", "workflow progress", or "zbuduj workflow".

5 installs
▌
Om Evolve Harness · open-mercato bundle
Add a reproducible standalone agent-harness use case or correct failed routing/context with semantic assertions, one knowledge owner, and before/after evaluation. Use for "add harness case", "agent got this wrong", "extend the harness", "new use case", or "rozszerz harness".

5 installs
▌
Om Troubleshooter · open-mercato bundle
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.

5 installs
▌
Om Module Scaffold · open-mercato bundle
Build a complete standalone business app, module, or CRUD vertical slice using Open Mercato discovery, commands, APIs, ACL/setup, UI, events, search, migrations, and tests. Use for customer management, deal-pipeline changes, CRM lead capture, library/booking/rental systems, "create a module", "add CRUD entity", "stwórz moduł", or another one-shot domain outcome.

5 installs
▌
Om System Extension · open-mercato bundle
Extend installed Open Mercato modules through UMES enrichers, interceptors, mutation guards, widgets, menus, entity extensions, events, component/page replacements, and overrides. Use for "extend core", "add field/column/action", "hide page", "intercept API", "UMES", or "rozszerz moduł".

6 installs
▌
Om Data Model Design · open-mercato bundle
Design or change standalone module entities, relations, encryption maps, migrations, snapshots, locking, and atomic writes. Use for "add entity", "database model", "migration", "encrypt this field", "optimistic locking", "model danych", or persistence bugs.

5 installs
▌
Om Framework Context · open-mercato bundle
Resolve exact installed Open Mercato package/module versions, original AGENTS.md hierarchy, source roots, generated-fact skew, and bounded ignored-source search without editing node_modules. Use for "inspect framework source", "find module AGENTS", "node_modules context", "exact installed contract", or "kontekst frameworka".

5 installs
▌
Om Eject And Customize · open-mercato bundle
Decide whether to eject an installed module and, after approval, copy it into standalone app ownership with version/upgrade evidence. Use for "eject module", "customize core beyond UMES", "fork installed module", "wyodrębnij moduł", or unsupported overrides.

5 installs
▌
Om Trim Unused Modules · open-mercato bundle
Analyze and disable unused built-in modules in a standalone app without breaking dependencies, navigation, backend landing, bootstrap, or generation. Use for "trim classic mode", "remove unused modules", "slim app", "disable built-ins", or "wyłącz moduły".

5 installs
▌
Om Fix · open-mercato bundle
Implements the minimal code change identified by the om-root-cause step, adds regression tests, and runs the configured validation gate. Claims the tracker issue at start (assignee + in-progress label + claim comment) so concurrent automation backs off. Does not commit, push, or open a PR — that is the om-open-pr step's job.

6 installs
▌
Om Open Pr · open-mercato bundle
Shared PR opener for the auto pipeline — commits the worktree, pushes, reuses an existing PR or opens a ready (non-draft) PR against the configured base branch with the unified body template, applies the full SDLC label set with rationale comments, and for issue-driven runs hands the issue back and releases the lock. Emits the `PR:`/`Issue:` chaining reference lines.

6 installs
▌
Om Discover · open-mercato bundle
Product-level discovery and define session that leaves a product-brief.md every later skill reads — problem and who has it, stakeholders, rules, flows, benchmark, success criteria, scope, assumptions, decisions. Three modes (existing product, client idea, own idea). Gathers real material before writing; never invents evidence. Use for "discovery", "define the product", "product brief".

6 installs
▌
Om UX Setup · open-mercato bundle
Extract the repository's design contract (tokens, component registry, screen archetypes, conventions) into .uxproof/ so every UX skill judges against THIS repo's design system, whatever it is. Run once per repository; re-run to refresh after design-system changes.

4 installs
▌
Om UX Shape · open-mercato bundle
Turn a vague product, UI/UX, or AI feature idea into a decided direction. Use when shaping a feature, simplifying an overcomplicated flow, deciding whether and how to use AI, defining screen states, planning validation, or preparing a design handoff for engineering.

8 installs

132 published skills · page 1 of 2