modly_CLI_MCP

Plans local Modly extension development through `modly ext-dev` without inventing runtime execution. Trigger: When the AI must analyze or draft an extension development plan from a local `manifest.json` workspace, classify `ext-dev` buckets, explain metadata, or keep extension planning aligned with Modly CLI V1 boundaries.

Operates Modly correctly in headless or assisted modes by respecting its real architecture boundaries: FastAPI for models, generation, jobs, and mesh ops; Electron IPC for setup, GitHub extension install/repair, logs, workflows, and app-level orchestration. Trigger: When the AI must use Modly, design or use a Modly CLI, integrate Modly with MCP/OpenCode, or operate Modly models, generation, jobs, extensions, or workflows.