Skip to content

xinetzone/SpecWeave / .agents/skills/meoo-cli

meoo-cli

Verified

从零到上线的全栈应用构建指南,基于秒悟(Meoo)平台。 触发条件: (1) 用户提到"秒悟"或"Meoo"; (2) 用户要从零构建应用,且需求可被以下架构覆盖:前端 SPA(React/Vue)+ Supabase(数据库/Auth/Storage)+ Deno 边缘函数 + AI 大模型服务; (3) 用户需要部署全栈应用(含后端进程),如 Next.js SSR、Express、FastAPI 等; (4) 用户需要把项目部署到自己的阿里云账号(ECS/RDS/SLB,费用自付) 覆盖完整生命周期:项目初始化、本地开发、云服务开通、数据库管理、边缘函数部署、CDN 发布、全栈镜像部署、沙箱代码同步、账户与权益管理。

秒悟(Meoo)CLI 完整指南

从零构建和部署全栈应用。覆盖项目初始化到生产部署的完整生命周期,包括云服务、代码规范、沙箱同步和部署。

Meoo 支持两种 Mise 发布模式:static(静态文件 → CDN)和 server(全栈服务 → 容器)。

项目类型部署模式命令
单 HTML、多 HTML、前端 SPAstaticmeoo deploy
前端 + Supabase + Edge Functions静态部署meoo deploy
含后端进程(Express、FastAPI、Next.js SSR、Go 等)servermeoo deploy

BLOCKING:执行 meoo deploy 或 meoo sandbox push 前,必须先完整读取 references/mise-import.md,让项目具备根 mise.toml 并完成对应预览和发布门禁。CLI 不会自动改造源码。

Install

npm install -g @aliyun-meoo/cli

Verify: meoo --version

Project lifecycle

Static deploy (SPA)

meoo login                      # 1. Authenticate (opens browser)
meoo init react-design          # 2. Initialize from template
meoo projects create "My App"   # 3. Create remote project (MUST do after init)
pnpm install                    # 4. Install dependencies
pnpm dev                        # 5. Local dev server (port 3015)
meoo deploy                     # 6. Build and publish to CDN

CRITICAL: Step 2 (init) and Step 3 (projects create) MUST be done together. init only creates local files — you MUST also run projects create to create the remote project on the platform. Without this, cloud services and deployments will fail or attach to the wrong project.

Server deploy (full-stack)

meoo login                      # 1. Authenticate
meoo init nextjs-app            # 2. Initialize from template (or bring your own project)
meoo projects create "My App"   # 3. Create project and bind to current directory
# ... develop your app locally ...
meoo deploy                     # 4. Upload, build remotely, deploy to container

无论模板还是已有工程,都先按 references/mise-import.md 建立 Mise 协议。服务端项目同样会同步到 Sandbox,并可在 meoo.com 预览。旧 .meoo/config.json runtime 和 --runtime image 仅用于迁移兼容,不再决定新链路。

Common steps (both modes)

Cloud services are OPTIONAL — only enable when the project needs database, user auth, or file storage:

meoo cloud enable               # Provision cloud services (PostgreSQL + Auth + Storage)
meoo cloud pull-env             # Pull Supabase keys to local .env

Do NOT run meoo cloud enable for purely frontend projects (static sites, CSS demos, calculators, etc.).

Cloud services are independent of deploy mode — see references/cloud-patterns.md for calling patterns.

Run meoo info or meoo --json info anytime to check environment constraints.

Publishing & deployment targets

Meoo has three deployment targets. Understanding them prevents common confusion.

  • Sandbox(沙箱):秒悟应用内的测试运行环境。所有受支持项目的源码通过 meoo sandbox push 或 meoo deploy 同步,统一由 mise run dev 在 3015 提供预览。
  • CDN(公网静态):static 模式专属。通过 meoo deploy 将 Mise output 声明的静态产物发布到 CDN。
  • FC 容器(公网服务):server 模式专属。通过 meoo deploy 将源码上传到远程构建机,按 Mise 构建并部署到函数计算容器。
Sandbox(沙箱)CDN(静态部署)FC 容器(镜像部署)
用途秒悟应用内预览、调试、协作公网正式访问(静态)公网正式访问(全栈)
更新方式meoo sandbox push 或 meoo deploymeoo deploymeoo deploy
访问入口meoo.com/chat/<projectId><id>.meoo.fun<id>.meoo.fun

meoo deploy 流程:通过 Mise 公共前置校验后,默认先尝试同步 Sandbox,再执行正式发布。Sandbox 同步失败必须告知用户,但不影响正式发布结果;静态项目会回退到本地产物 CDN 发布。

静态云服务项目同步成功后,从已确认的 Sandbox Git HEAD 构建并发布;DUAL 环境随后同步生产云服务。默认同步云函数,不同步 Auth 与定时任务。--skip-push 只跳过 Sandbox 并走本地产物发布;--skip-build 使用已有 Mise output;--no-dev 同步源码但不触发预览重启。不要把 Sandbox 未更新或预览为空报告为完整成功。

静态项目若要在秒悟应用内预览或协作,源码必须通过 meoo sandbox push 或 meoo deploy(不加 --skip-push)同步到沙箱。全栈项目由 Mise server 模式决定正式发布,并由同一次 meoo deploy 尝试同步 Sandbox。

Migrating an existing project

已有单/多 HTML、SPA 或全栈工程都不要重建脚手架。先读 references/mise-import.md,保留技术栈并做最小运行适配;静态细节见 references/static-deploy.md,服务端细节见 references/image-deploy.md。


Platform constraints

Constraints differ by deploy mode. Read the relevant reference before starting any project work:

  • 所有 deploy/push:先读 references/mise-import.md。
  • Static deploy:再读 references/static-deploy.md。
  • Server deploy:再读 references/image-deploy.md。

CLI command reference

All commands support --json for structured output. Run meoo <command> --help for details.

Authentication & Account

meoo login                         # Browser-based login (recommended, opens browser for authorization)
meoo login --ak <key>              # Login with API Key (for CI/CD or manual setup)
meoo logout                        # Clear credentials
meoo whoami                        # Current user info + plan tier
meoo account                       # Full account info: plan, benefits, credits

meoo login (without --ak) opens the browser for one-click authorization. The server auto-creates an API Key and the CLI saves it locally. For CI/CD environments, use --ak or set MEOO_API_KEY / MEOO_API_URL environment variables.

meoo account shows your plan tier (FREE/PRO/MAX), credit balance (available, granted, consumed), and detailed benefit quotas (cloud instances, storage, projects, etc.).

Project management

Project binding is per-directory — each project directory has its own .env with MEOO_PROJECT_URL_ID. There is no global "current project". Switching directories switches projects automatically.

meoo projects list                 # List projects (▸ = bound to current directory)
meoo projects create [name]        # Create project and bind to current directory (.env)
meoo projects use <urlId>          # Bind existing project to current directory (.env)
meoo projects current              # Show project bound to current directory

If a command fails with NO_PROJECT_BOUND, run meoo projects use <urlId> in the target directory first.

Templates (static deploy only)

meoo init --list                   # List available templates
meoo init <template>               # Initialize in current (empty) directory

Static deploy templates (前端 SPA → CDN):

TemplateStackKey rules
react-designReact 19 + Vite 7 + shadcn/ui + TanStack RouterDefault Web template; do NOT reinstall Radix, use @ path alias
custom-projectVue / Svelte / other non-ReactUser must explicitly request non-React framework
taro-projectTaro 4 + React + ZustandNo native HTML tags, no arbitrary values

Server deploy templates (全栈应用 → 容器;模板默认生产端口可按项目实际保留):

TemplateStackKey rules
nextjs-appNext.js 15 + React 19 + Tailwind CSSstandalone output, port 9000
nuxt-appNuxt 3 + Vue 3 + Tailwind CSSnitro server, port 9000
java-appSpring Boot 3 + React SPAMaven build, port 9000
go-appGo net/http + React SPAgo build, port 9000
python-appFastAPI + React SPApip + uvicorn, port 9000

See references/templates.md for full template-specific constraints.

Cloud services

meoo cloud enable                  # Provision PostgreSQL + Auth + Storage + Realtime
meoo cloud enable --env-mode DUAL  # Choose dual development/production environments on first enable (requires server-side qualification)
meoo cloud status                  # Check status
meoo cloud pull-env                # Pull Supabase keys to .env
meoo cloud enable-register-login --providers <type>  # Enable email/SMS verification auth

After cloud enable, the CLI shows your current cloud service quota, storage usage, and available credits. It also warns that deploying AI services consumes credits. Always run pull-env next to sync connection info locally. The .env tracks which project it belongs to via MEOO_PROJECT_URL_ID. Omitting --env-mode preserves the existing platform default. --env-mode SINGLE selects a single environment; --env-mode DUAL explicitly requests separate development and production environments. The server rejects DUAL when the project or account is not eligible; do not silently retry as SINGLE. This option only applies when first enabling cloud service; it does not convert an existing instance.

IMPORTANT — Quota / entitlement errors: If cloud enable or any cloud command fails with QUOTA_EXCEEDED, STORAGE_EXCEEDED, or similar entitlement errors, you MUST:

  1. Stop all cloud operations immediately — do not retry or attempt workarounds.
  2. Inform the user clearly — explain which quota is full (e.g. cloud instance count, storage capacity).
  3. Guide the user to upgrade — direct them to https://docs.meoo.com/coindesc to view plan tiers and upgrade. Example: "您的云服务实例数已达当前套餐上限,请前往 https://docs.meoo.com/coindesc 查看套餐详情并升级后继续使用。"
  4. Ask the user how to proceed — do not assume they will upgrade. They may choose to go to https://meoo.com to delete unused projects/instances to free quota, or decide not to continue.

enable-register-login activates email/SMS verification + password auth. Provider types: email, sms, or email,sms. Single-provider requires --confirmed-provider-set flag. This command is idempotent — if the requested providers are already enabled, it skips activation and avoids unnecessary service restart. When activation is needed, it triggers a cloud service restart — always run it LAST, after all migrations and code changes.

Database

meoo db query "SELECT * FROM users"        # Execute SQL
meoo db query --file setup.sql             # From file
meoo db tables                             # List tables + columns
meoo db migrate --name <n> --sql <ddl>     # DDL + save migration + update types

--name, --sql are both required for migrate. It writes:

  • migrations/{timestamp}_{name}.sql
  • src/supabase/types.ts (auto-generated from DB schema)

Edge Functions

meoo fn list                               # List functions + secrets
meoo fn deploy <name>                      # Deploy from ./functions/<name>/
meoo fn deploy <name> --no-verify-jwt      # Allow anonymous access
meoo fn delete <name>                      # Delete function

Functions run on Deno. Entry must be index.ts. Name regex: /^[A-Za-z][A-Za-z0-9_-]*$/.

MEOO_PROJECT_API_KEY can be used in Edge Functions and image deploy server code. Never in frontend. For static deploy projects, proxy AI calls through Edge Functions.

Secrets

meoo secrets list                          # List all
meoo secrets set <KEY> <VALUE>             # Set or update
meoo secrets delete <KEY>                  # Delete

Sandbox (code sync)

所有符合 Mise 协议的 static/server 项目都能在本地与云端 Sandbox 之间同步代码。

meoo sandbox push [path]                   # Upload local code to sandbox
meoo sandbox push --dry-run                # Check status without uploading
meoo sandbox push --force                  # Skip confirmation prompts
meoo sandbox push --summary "changed X"    # Attach change summary (for AI agent context)
meoo sandbox push --message "my commit"    # Custom commit message
meoo sandbox push --no-commit              # Upload without git commit
meoo sandbox push --no-dev                 # Upload without preview restart

meoo sandbox pull [path]                   # Download code from sandbox to local
meoo sandbox pull --dry-run                # List sandbox files without downloading
meoo sandbox pull --force                  # Skip confirmation prompts
meoo sandbox pull --output <dir>           # Output to specific directory

Push safety checks (automatic before upload):

  1. Validates the root mise.toml before any upload
  2. Detects if sandbox Agent is running — blocks standalone push (AGENT_RUNNING error)
  3. Compares sandbox HEAD with last synced commit and warns about remote changes
  4. Prompts for confirmation when overwrite risk exists (use --force to skip)

传入单个文件时仍会附带并持久化根 mise.toml 控制文件。独立 sandbox push 失败为非零;deploy 内部同步失败只影响 sandboxSync,会继续正式发布。

Pull restrictions: Free plan users cannot pull code — only push is allowed. Upgrade to PRO/MAX for code download.

Sync tracking: After each push/pull, the CLI records the sandbox HEAD commit hash locally (~/.meoo/config.json). On next push, it compares this with the current sandbox HEAD to determine if remote changes occurred since last sync.

Mock conversation: After a successful push, a conversation record is created in the project so the AI agent has context about the code change.

Deployment

# Mise decides static CDN or server container
meoo deploy                                # Default: sync Sandbox, then formal release
meoo deploy --force                        # Skip all confirmation prompts (for AI/CI)
meoo deploy --skip-build                   # Static: use existing Mise output
meoo deploy --skip-push                    # Formal release only
meoo deploy --no-dev                       # Sync source without preview restart
meoo deploy --sync-auth                    # DUAL: also sync login configuration
meoo deploy --sync-cron                    # DUAL: also sync cron (implies functions)
meoo deploy --no-sync-functions            # DUAL: omit function sync (unless cron selected)

meoo releases list                         # Version history (both static and image releases)

After successful deploy, the CLI shows the project settings URL for custom domain configuration and permission management.

Server deploy upload: Source upload honors .dockerignore; source archive must be ≤100MiB. Build/start behavior comes from mise.toml, not fixed shell-script filenames.

Upgrade

meoo skill install 安装当前 CLI 包内置的 Skill,不请求在线 manifest 或 ZIP。升级 CLI 后执行此命令;未识别当前 Agent 的工具目录时用 --target <Skill目录> 指定。安装后重新读取 SKILL.md 和 references/mise-import.md。遇到 MISE_ADAPTATION_REQUIRED 或 RUNTIME_CONFIG_CONFLICT 时先更新 Skill,再根据实际项目修复 Mise 配置;不要从旧 HTTP 地址覆盖新版 Skill。

meoo upgrade                               # Check and install latest version

The CLI automatically checks for updates once every 24 hours. When a new version is available, a notice is shown after command output.

Info

meoo info                                  # Human-readable constraints
meoo --json info                           # JSON (for AI agent parsing)

Cloud service rules

BLOCKING: Read docs before cloud operations

Before writing any cloud service code, you MUST read the relevant reference:

  • Cloud patterns: references/cloud-patterns.md — Supabase client (frontend + server-side), Edge Functions, AI chat, Auth, RLS, migrations
  • Email/SMS verification auth: references/auth-verification.md — registration state machine, API usage rules, common pitfalls

MEOO_PROJECT_API_KEY can be used in Edge Functions and image deploy server code — never in frontend.

Data rules

  • All data MUST be real cloud data. NEVER use mock/fake data.
  • src/supabase/client.ts and src/supabase/types.ts are auto-generated — do NOT edit.
  • Do NOT modify system schemas (auth/storage/realtime/supabase_functions/vault).
  • Cloud commands must be called individually (not chained with &&).

Template-specific constraints (static deploy only)

Each template has strict constraints that will break the build if violated. Read references/templates.md BEFORE writing code for any template project.


Available models (for AI integration)

ModelID
Qwen 3.6 Plus (default)qwen3.6-plus
Kimi K2.5kimi-k2.5
DeepSeek V3.2deepseek-v3.2
GLM 5glm-5
MiniMax M2.5MiniMax-M2.5

Documentation

When users ask about plan differences, credit consumption, pricing, or feature availability across tiers, direct them to the plans & credits page. When users need detailed platform usage instructions beyond what this skill covers, direct them to the product documentation.


Known limitations

Do NOT attempt unsupported patterns — they will fail.

Application types

  • Static deploy: any project that produces a valid static output with index.html, including single/multi HTML and supported SPAs.
  • Server deploy: any supported language/framework that can provide a single HTTP entry and satisfy the Mise contract.
  • No native mobile apps — Taro covers WeChat mini programs + H5 only.

Authentication (Supabase Auth)

Supported: username+password (default), email+password, phone-as-username, WeChat (mini program only), email/SMS verification code + password (requires enable-register-login). Pure passwordless verification-code login is NOT supported. No third-party OAuth (GitHub/Google/QQ/Alipay), no QR scan, no biometric. See references/auth-verification.md.

Cloud services

  • Cloud environment may be SINGLE or DUAL. DUAL keeps development and production Supabase instances separate; CLI cloud development commands remain on the development instance, while meoo deploy performs the explicit production sync.
  • Edge Functions run Deno (not Node.js). Image deploy server code can use any runtime.
  • Secrets are write-only — values cannot be read back after setting.

AI service

  • Fixed model list only (see Available models above). No GPT/Claude.
  • For static deploy projects, must proxy AI calls through Edge Functions. Image deploy server code can use MEOO_PROJECT_API_KEY directly.
  • Vision and image generation available at meoo.com.

Deployment

  • No rollback — can only deploy a new version.
  • No per-deploy preview release — every formal deploy goes to production immediately; Sandbox development preview is supported separately.

Plans and entitlements

  • Three tiers: FREE, PRO, MAX. FREE users cannot pull code from sandbox.
  • AI services consume credits. Check with meoo account.
  • Quota enforcement — when limits are reached, cloud operations are rejected. MUST stop immediately, explain the quota, and direct user to https://docs.meoo.com/coindesc to upgrade or to https://meoo.com to free up resources.

CLI features not yet available

  • meoo domains — custom domain management
  • meoo open — open project in browser
  • meoo projects delete — delete a project
  • meoo logs — edge function logs

Deploy to your own Alibaba Cloud account

触发条件:仅当用户明确说了类似"部署到我自己的阿里云账号"、"用 ECS/RDS 跑这个,费用我自己出"这样的话才使用本节。用户单纯说"部署"、"上线"、"发布"时,走上面的 meoo deploy,不要联想到这里。

这是一个完全独立的第四条部署路径(meoo aliyun <sub>),不属于本技能其余部分覆盖的生命周期。一旦触发,唯一的信息来源是 references/aliyun-deploy.md——命令、flag、判断规则、状态文件、流程细节全部在那份文档里,本技能主文档和其他 references/*.md 的任何内容都与阿里云部署无关,不适用、也不要参照。触发后先读那份文档,再操作。


slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 192kUpdated Claude CodeCodexVerifiedInstall