cloudbase

# CloudBase Development Guidelines ## Workflow ``` 1. Exploration → Read the matching skill completely before writing any code. Search with searchKnowledgeBase(mode="skill"), then Read full SKILL.md. 2. Implementation ├── 2a. Resource preparation → Prefer MCP; if MCP tools are missing in THIS session, │ configure MCP for next session and use `tcb` CLI now (see tooling-fallback.md) └── 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 must precede frontend code. Stage 3 is mandatory. ## Activation Contract Routing uses stable skill ids (`auth-tool-cloudbase`, `auth-web-cloudbase`, `http-api-cloudbase`, …) across source, generated artifacts, and installs. ### Standalone skill fallback If only one published skill is exposed: - Prefer local relative paths (`references/<skill-id>/SKILL.md` or sibling skill directories) when those files exist in the workspace. - Do **not** fetch sibling skill markdown from remote raw URLs into the agent context. - If a required sibling skill is missing locally, ask the user to install the full CloudBase skills pack or IDE plugin (`npx skills add tencentcloudbase/cloudbase-skills`), then continue using local files only. Follow relative `references/...` paths from the current skill. If MCP is unavailable in this session, follow `references/tooling-fallback.md`: configure MCP via `re...