catalyst-basics
⚠️ PRE-FLIGHT CHECK: Before creating any project files, confirm that
.catalystrcandcatalyst.jsonexist in the project directory. If they don't:
- Use MCP (
CatalystbyZoho_List_All_Organizations→CatalystbyZoho_List_All_Projects) to get the org ID and project ID.- Run:
catalyst init --org <orgId> -p <projectId> -ni- Never ask the user to run
catalyst initinteractively. Never create these files manually — they are CLI-generated and must come from the CLI.
How It Works
- MCP check first — Before reading any local files, look for
CatalystbyZoho_*tools. If available, use MCP to get org ID, project ID, and all resource IDs instead of asking the user. - New to Catalyst? — If the user is setting up Catalyst for the first time or asking "how do I start", load
references/quick-start.mdfor the full walkthrough. - Console navigation — If the user asks how to find IDs, create tables, set permissions, or configure CORS in the console, load
references/console-ui-guide.md. - Pre-flight — Confirm
.catalystrcandcatalyst.jsonexist. If missing, use MCP to get org/project IDs and runcatalyst init --org <orgId> -p <projectId> -ni. Never use interactivecatalyst init. - Project structure — Load
references/project-basics.mdfor directory layout,catalyst.json, IDs, and dev-to-prod checklist. - CLI questions — Load
references/cli.mdfor the exact command, flags, and safety rules. - Answer — Provide the specific ID path or CLI command needed. Never ask the user to manually look up IDs when MCP is connected.
Triggers
Use this skill for: "how do I start a Catalyst project", "what is .catalystrc", "where do I find my Table ID / ZAID / Segment ID / Project ID", "difference between Development and Production", "Catalyst project structure", "catalyst.json explained", catalyst init, catalyst deploy, catalyst serve, catalyst login, "how do I set up Catalyst with Claude", "how do I use Catalyst in Cursor", "how do I use Catalyst with GitHub Copilot", "which service should I use", "what Catalyst service for X", or any question about Catalyst IDs, environments, organizations, IDE setup, architecture decisions, or CLI subcommands.