Cloudbase All In One

Route quickly to the minimum needed skills

• Web app execution -> ./web-development/SKILL.md
• Web auth provider readiness -> ./auth-tool/SKILL.md
• Web auth implementation -> ./auth-web/SKILL.md
• Browser-side document database CRUD -> ./no-sql-web-sdk/SKILL.md
• Browser-side file upload -> ./cloud-storage-web/SKILL.md
• Platform overview only when capability selection is still unclear -> ./cloudbase-platform/SKILL.md

High-yield guardrails

• If the same path fails 2-3 times, stop retrying and reroute. Check platform skill, auth domain, runtime, and permission model before editing more code.
• Always specify EnvId explicitly in code, configuration, and command examples when initializing CloudBase clients or manager operations. Do not rely on the current CLI-selected environment or implicit defaults.
• When saving MCP or tool results to a local file with a generic file-writing tool, pass text, not raw objects. For JSON output files, serialize first with JSON.stringify(result, null, 2) and write that string as the file content.
• If the file-writing tool reports that a field such as content expected a string but received an object, do not retry with the same raw object. Serialize the object first, then retry once with the serialized text, and make sure the retried call actually passes the serialized string rather than the original object.

Do NOT use this as

• A reason to read every CloudBase skill before touching code.
• A reason to start from platform overview when the existing code already reveals the stack and the missing pieces.

Working rules

1. Existing application with TODOs:

   • Treat it as a targeted repair task, not a greenfield build.
   • Prefer the shortest path from current code to working flow.

2. Auth tasks:

   • If the account identifier is a plain username such as admin, editor, or another string without @, treat usernamePassword login as a blocking prerequisite.
   • First call queryAppAuth(action=\"getLoginConfig\").
   • If loginMethods.usernamePassword !== true, immediately call manageAppAuth(action=\"patchLoginStrategy\", patch={ usernamePassword: true }).
   • In code, use auth.signUp({ username, password }) and auth.signInWithPassword({ username, password }).
   • Never use signUpWithEmailAndPassword or signInWithEmailAndPassword for these username-style account flows.
   • Once readiness is confirmed, return to the active frontend handler and finish the real login/register flow.

3. Database and storage tasks:

   • Reuse the current shared app, auth, db, and storage helpers instead of creating parallel SDK wrappers.
   • For writes, validate the actual SDK result instead of assuming success.

4. Targeted repair tasks:

   • Functional closure beats exploration.
   • Avoid broad repo sweeps, UI redesign, and detached demo code.
   • Keep file discovery narrow. Prefer direct reads of the known active files over Glob / broad search across the whole project.