glubeanlisted

# Glubean Use this skill as a Glubean best-practice guide. Default to the real project workflow. Scratch mode is an extension quick demo path, not the normal agent path. ## Modes 1. **Docs**: product questions, concepts, comparison, migration, editor support, or cloud features. 2. **Onboarding**: no Glubean project yet; the user needs extension, MCP, cookbook, or project init guidance. 3. **Project**: the user is already in a Glubean project, or clearly wants to do real project test work, including migration from existing API assets. ## Route first Before choosing a mode: - Check for `package.json`, `config/`, `schemas/`, `contracts/`, `tests/`, `explore/`, `.env`, `.env.secrets`, and `GLUBEAN.md`. - Check whether `@glubean/sdk` is already present in dependencies or devDependencies. - Check whether MCP tools are available. - If `GLUBEAN.md` exists, read it first as the project's context file. - Users should keep key context there, including pointers to relevant code, docs, specs, and sibling workspaces. - If the user explicitly provides additional context locations, read those too before guessing from the API alone. Then route by intent plus environment: - **Docs**: explanation only, with no active project task. Read [references/docs-mode.md](references/docs-mode.md). - **Onboarding**: no Glubean project yet, and the user wants to get set up properly. Read [references/onboarding.md](references/onboarding.md). - **Project**: the repo already looks like a Glubean projec