add-module

Add deterministic Mozaiks backend modules with CRUD/action handlers and MongoDB persistence.

14|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill add-module-blocunited-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-module
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/add-module
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill add-module-blocunited-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you add deterministic backend CRUD/action handlers to an existing Mozaiks app without relying on AI for core logic, so your new entity becomes callable via stable API routes.

Core Features & Use Cases

  • Define module identity and actions using module.yaml, including permissions, input/output schemas, and action-to-handler method wiring.
  • Author required backend dispatch code in backend/handler.py and delegate real business logic to backend/service.py and persistence to backend/repo.py.
  • Use event and contract plumbing safely by optionally defining contracts/events.yaml, contracts/reactions.yaml, contracts/notifications.yaml, and keeping reactions as the canonical event→handler routing contract.
  • Expose data to the UI and workflows by connecting module actions to page data tables and workflow backend requests.
  • Maintain production-honest behavior by ensuring module actions query real state and avoid mock KPI data or fabricated metrics.

Quick Start

Tell me: “Add a backend module for {entity} with list and create actions, including CRUD handlers, MongoDB persistence scoping, and API routes wired to a new page.”

Frequently Asked Questions about add-module

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add backend CRUD handlers and MongoDB persistence to an existing app?

To add backend CRUD handlers, you define a root module.yaml identity and dispatch backend/handler.py, delegating business logic to service.py and MongoDB access to repo.py for stable entity-focused API routing.

What is the best way to wire backend API routes to UI page data tables?

The best way to wire API routes to UI pages is by defining module actions in module.yaml and connecting those actions directly to page data tables and workflow backend requests for production-ready data exposure.

How do event reactions and notification contracts work in backend module routing?

Event reactions and notification contracts work by defining contracts in events.yaml, reactions.yaml, and notifications.yaml, keeping reactions as the canonical event-to-handler routing contract for production workflows.

Do I need a root SKILL.md file to create a backend module?

Yes, you need a root SKILL.md module definition containing module.yaml identity, backend handler dispatch, service.py logic, and repo.py MongoDB access to create a deterministic backend module.

Can I use mock KPI data when generating backend module actions?

No, you should not use mock KPI data. Backend module actions must query real state and maintain production-honest behavior by avoiding fabricated metrics to ensure reliable API execution and data integrity.