ワンクリックで
setup
Set up Mozaiks from scratch. Walks through Docker, Python, Node, environment variables, and verification.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Set up Mozaiks from scratch. Walks through Docker, Python, Node, environment variables, and verification.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
Review or implement a change to AppGenerator prompts, AppBuildPlan contracts, file contracts, assembly behavior, generated UI quality gates, or app-bundle generation guidance.
SOC 職業分類に基づく
| name | setup |
| description | Set up Mozaiks from scratch. Walks through Docker, Python, Node, environment variables, and verification. |
| argument-hint | [optional: your OpenAI API key] |
Help the user set up Mozaiks from a fresh clone.
Mozaiks supports four development tiers:
| Tier | Use Case | What's Included |
|---|---|---|
| engine | Headless AI API | Workflows only, no UI |
| chat | Chatbot builders | Workflows + chat UI |
| integrated | SaaS builders | + modules + event bus + auth |
| full | Product builders | + admin portal + full management surfaces |
For more info on tiers: /init-project or /add-feature skills.
Run these commands and verify versions:
If anything is missing, help them install it first.
For this repo, the default local contributor experience is:
http://localhost:8000web_shell/ frontend on http://localhost:3000factory_app/app as the first-party builder/reference app bundle when no
external app workspace is selected# Copy .env.example to .env
cp .env.example .env # or Copy-Item on Windows
Set OPENAI_API_KEY=sk-... in .env. If $ARGUMENTS contains an API key, use it.
python -m venv .venv
# Activate: .\.venv\Scripts\Activate.ps1 (Windows) or source .venv/bin/activate (Unix)
python -m pip install --upgrade pip
python -m pip install -e ".[dev]"
npm --prefix web_shell install
Preferred path in this repo:
.\scripts\run-studio.ps1
That starts the Studio host backend and the web_shell frontend together.
http://localhost:3000/appshttp://localhost:8000/health.\scripts\smoke-studio-local.ps1 for the full local Studio smokefactory_app/appIf the user wants separate backend and frontend terminals:
.\scripts\run-backend.ps1
.\scripts\run-frontend.ps1
If they are developing against an external app workspace, rerun those scripts
with -AppWorkspacePath <path>.
=-AppWorkspacePath <path> or set PLATFORM_PATHrun-studio.ps1, run-backend.ps1, or run-frontend.ps1 with -ForceStop| Service | URL |
|---|---|
| Frontend | http://localhost:3000 |
| Backend | http://localhost:8000 |
| Keycloak | http://localhost:8080 |
| Keycloak Admin | http://localhost:8080/admin (admin/admin) |
| MongoDB | localhost:27017 |