From catalyst-by-zoho
Guides Catalyst project setup including directory structure, environments, CLI commands, and resource IDs. Triggered by questions about project initialization, configuration files, and deployment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/catalyst-by-zoho:catalyst-basicsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **⚠️ PRE-FLIGHT CHECK:** Before creating any project files, confirm that `.catalystrc` and
⚠️ PRE-FLIGHT CHECK: Before creating any project files, confirm that
.catalystrcandcatalyst.jsonalready exist in the project directory. If they don't, STOP — do not create files, do not scaffold. Tell the user to runcatalyst initin their terminal first.catalyst.json,.catalystrc, andfunctions/are auto-generated by the CLI and cannot be created manually.
CatalystbyZoho_* tools. If available, use MCP to get org ID, project ID, and all resource IDs instead of asking the user.references/quick-start.md for the full walkthrough.references/console-ui-guide.md..catalystrc and catalyst.json exist. If missing, stop and direct the user to run catalyst login then catalyst init.references/project-basics.md for directory layout, catalyst.json, IDs, and dev-to-prod checklist.references/cli.md for the exact command, flags, and safety rules.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.
Before reading .catalystrc, asking the user for IDs, or doing anything project-related — check whether Zoho MCP tools are available in your tool list.
Look for tools prefixed with CatalystbyZoho_ (e.g., CatalystbyZoho_List_All_Projects, CatalystbyZoho_List_All_Tables).
If MCP tools ARE available:
CatalystbyZoho_List_All_Organizations to get the org IDCatalystbyZoho_List_All_Projects to get the project IDIf MCP tools are NOT available:
claude_desktop_config.json) and add the Catalyst MCP server.catalystrc and catalyst.json from the local project directory only as a last resortNever ask the user to manually look up IDs from the console if MCP is connected. Every project detail — org ID, project ID, table IDs, ZAIDs, bucket names — is retrievable via MCP tools. Asking the user to hunt for IDs when MCP is available wastes time and introduces copy-paste errors.
Load the relevant reference file for detailed information:
| Reference | Contents |
|---|---|
references/quick-start.md | First-time setup — install CLI, catalyst init, find org/project IDs, add a function, serve locally, deploy, create a Data Store table, configure CORS/Authorized Domains |
references/console-ui-guide.md | Console navigation — finding Project ID/ZAID/Table ID, creating tables with typed columns, enabling App User permissions (Scopes and Permissions), Authorized Domains + CORS toggle |
references/project-basics.md | Project directory structure, catalyst.json, .catalystrc, catalyst-config.json, environments, dev-to-prod checklist, all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, etc.) |
references/cli.md | Full CLI command reference — all subcommands with flags, Slate/AppSail non-interactive setup, catalyst serve port behavior, deploy scoping, safety rules, resource-first development order |
references/architecture.md | Service selection guide — which Catalyst service to use for which pattern, typical stack combinations, DC availability table for regionally restricted services |
references/setup/claude-code.md | Installing skills and connecting Zoho MCP in Claude Code (Claude Desktop) |
references/setup/cursor.md | Installing skills and connecting Zoho MCP in Cursor |
references/setup/github-copilot.md | Installing skills and connecting Zoho MCP in GitHub Copilot (VS Code) |
npx claudepluginhub catalystbyzoho/agent-skills --plugin catalyst-by-zohoManages Catalyst Zoho infrastructure (tables, buckets, cache) via CatalystbyZoho_* MCP tools using natural language. For users of MCP-capable AI hosts who want to create tables or configure MCP servers.
Bootstraps new projects with identity, design system, i18n, SEO, test infrastructure, and 8-gate deploy pipeline. Prevents tech debt from day zero.
Scaffolds CLAUDE.md and .claude/rules/ for Craft CMS projects, detecting project type (plugin, site, module, hybrid, monorepo) from composer.json and other files.