What problem does it solve? Building and shipping a Miaoda (Spark) application involves many distinct operations—creating the app asset, choosing between local full-stack development, HTML static hosting, or cloud AI generation, managing databases, and deploying releases. This Skill routes every user intent to the correct lark-cli command with the right guardrails, so nothing gets misrouted or deployed prematurely. ## Core Features & Use Cases - Intent Routing: Maps user requests (create, list, update, publish, deploy, set access scope, run SQL) to the exact lark-cli apps +<cmd> command and its detailed reference doc. - Three Development Paths: Distinguishes HTML static publishing (+html-publish), local full-stack development (+init + native git + +release-create), and cloud AI generation sessions (+session-create → +chat → +session-get polling). - Release Guardrails: Enforces that only a +release-get status of finished (with online_url) or a successful +html-publish proves deployment, preventing confusion between dev-mode links and published links. - Use Case: A user says "build me a polling tool and give me a shareable link." The Skill asks whether they prefer local coding or cloud AI generation, creates a full_stack app, drives the chosen workflow, deploys via +release-create, polls until finished, and returns the online_url. ## Quick Start Ask the assistant to create a new Miaoda app named "team poll" and deploy it so you get a shareable link.