Menu
Backend capabilities are now modules. Redirects to add-module.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Set up Mozaiks from scratch. Walks through Docker, Python, Node, environment variables, and verification.
Customize app shell branding - themes, colors, navigation, logos. Works with app/brand/ and app/config/ declarative files.
Add features to an existing Mozaiks project. Helps users upgrade tiers or enable individual capabilities.
Add a backend module (deterministic CRUD/action handler) to an existing Mozaiks app.
Add a frontend page (AppPageSchema) to an existing Mozaiks app.
Review or implement a change to AgentGenerator prompts, workflow bundle structured outputs, workflow scaffolds, universal prompt injection, or workflow-agent safety guidance.
| name | add-capability |
| description | Backend capabilities are now modules. Redirects to add-module. |
| argument-hint | [capability name or description] |
The add-capability pattern (FastAPI router + Pydantic models under platform/capabilities/) is
no longer the canonical way to add backend logic to a Mozaiks app.
Use the add-module skill instead. Modules are the canonical deterministic backend unit in
Mozaiks. They follow the 4-layer contract (handler → service → repo → policy + schemas) and are
auto-discovered by the platform host at startup.
See: .agents/skills/add-module/SKILL.md
