cloudbase

# CloudBase Development Guidelines ## Workflow Every CloudBase task follows this three-stage process: ``` 1. Exploration → Read the matching skill completely before writing any code. Search for it with searchKnowledgeBase(mode="skill"), then Read the full SKILL.md content. Do not rely on search summaries. 2. Implementation ├── 2a. Resource preparation → Use MCP tools to prepare backend resources │ (enable auth providers, create database tables, configure storage, │ set up security rules — before writing any frontend code) └── 2b. Frontend implementation → Write code, install deps, start server, test 3. Close-out → Run cloudbase-code-review, fix errors, declare done ``` **Key constraints:** - Stage 2a (resource preparation) must precede frontend code. Always use MCP tools. - Stage 3 is mandatory. The close-out includes automated lint checks and manual LLM review. Do not skip it. ## Activation Contract Read this section first. The routing contract uses stable skill identifiers such as `auth-tool`, `auth-web`, and `http-api`, so it works across source files, generated artifacts, and local installs. ### Standalone skill fallback If the current environment only exposes a single published skill, start from the CloudBase main entry: - CloudBase main entry: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/SKILL.md` - Sibling skill pattern: `https://cnb.cool/tencent/cloud/...