The AI-Engineering Foundation Framework for CRM/ERP and commerce: open-source TypeScript, with multi-tenancy, RBAC, events and domain modules already decided as conventions and specs, so Cursor, Claude Code and Codex build features instead of re-deciding architecture. Start with 80% done.
About the project
Open Mercato is an open-source TypeScript foundation framework for building CRM, ERP, commerce, and other business applications with established architecture, specifications, permissions, events, and domain modules. It is for teams and developers who want AI coding assistants to build consistent business software on top of ready-made foundations. The catalogue add-ons teach agents the framework’s conventions and workflows for implementing, testing, reviewing, and debugging features.
This skill was authored inside the Open Mercato monorepo. In a standalone app the differences below apply. Everything tracker-facing (branches, labels, comments, PRs, issues) goes through the tracker abstraction: execute the operations and label guards exactly as .ai/trackers/github.md defines them, and never inline…
This skill was authored inside the Open Mercato monorepo. In a standalone app the differences below apply. Everything tracker-facing (branches, labels, comments, PRs, issues) goes through the tracker abstraction: execute the operations and label guards exactly as .ai/trackers/github.md defines them, and never inline…
This skill was authored inside the Open Mercato monorepo. In a standalone app the differences below apply. Everything tracker-facing (branches, labels, comments, PRs, issues) goes through the tracker abstraction: execute the operations and label guards exactly as .ai/trackers/github.md defines them, and never inline…
Everything tracker-facing uses the operations and guards from .ai/trackers/github.md. Resolve an automatic base branch through default-branch; never assume main or develop.
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", "CALLAPI", "approval task", "workflow progress", or "zbuduj workflow".
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.
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".
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"…
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".
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.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: