add-capability

Redirect backend logic from deprecated capabilities to Mozaiks add-module workflows.

14|1|Updated Jan 8, 2026

Search Tags:#architecture #pydantic #fastapi #backend #modules #auto-discovery #mozaiks

Ready to run

npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill add-capability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-capability
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/add-capability
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill add-capability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents teams from using an outdated backend pattern for Mozaiks apps, reducing rework and ensuring new backend logic follows the platform’s current deterministic module contract.

Core Features & Use Cases

Redirects to add-module: Guides users away from the deprecated FastAPI router + Pydantic pattern under platform/capabilities/.
Aligns with Mozaiks modules: Ensures backend logic is implemented as canonical deterministic modules using the 4-layer contract (handler → service → repo → policy + schemas).
Supports auto-discovery: Helps users produce artifacts that the platform host can discover and validate at startup.

Quick Start

Use the add-module skill to add your backend logic in a module that satisfies the 4-layer contract and is auto-discovered at Mozaiks startup.

Frequently Asked Questions about add-capability

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

FAQPage Schema

How do I add backend logic to a Mozaiks app using FastAPI and Pydantic?▼

To add backend logic to a Mozaiks app, use the canonical add-module workflow to implement deterministic modules with a handler → service → repo → policy + schemas structure for platform validation and auto-discovery.

Why does my Mozaiks platform not auto-discover my new backend modules?▼

Mozaiks auto-discovery requires backend modules to follow the deterministic 4-layer contract: handler → service → repo → policy + schemas. Deprecated capabilities patterns under platform/capabilities/ are no longer validated or discovered at startup.

What is the correct module structure for Mozaiks server-side logic?▼

The correct module structure for Mozaiks server-side logic is a deterministic 4-layer contract: handler → service → repo → policy + schemas. This ensures platform validation and auto-discovery at startup.

Can I still use the platform/capabilities/ pattern for backend development?▼

The platform/capabilities/ pattern is deprecated for backend development. You should redirect to the add-module workflow to implement canonical deterministic modules that satisfy the platform's current validation contract.

How do I migrate deprecated FastAPI router capabilities to Mozaiks modules?▼

To migrate deprecated FastAPI router capabilities, redirect your backend logic to the add-module workflow and restructure it into the handler → service → repo → policy + schemas format for auto-discovery.