Catalyst by Zoho

View saved version →

---
name: catalyst-by-zoho
description: >
  Expert coding assistant for Catalyst by Zoho — full-stack serverless cloud platform. Trigger on any
  mention of Catalyst, zcatalyst, AppSail, Data Store, ZCQL, Cache, Stratus, Circuits, SmartBrowz,
  ConvoKraft, Slate, Signals, Pipelines, QuickML, NoSQL, Job Scheduling, Zia Services, CodeLib,
  API Gateway, Connections, Zoho MCP, CatalystbyZoho, catalyst init/deploy/serve, zcatalyst-sdk-node,
  or catalyst-config.json. Covers all 7 function types, full service catalog, architectural guidance,
  and Zoho MCP tool-based resource management. Also trigger on migration/comparison with AWS Lambda,
  S3, DynamoDB, Vercel, Netlify, Supabase, Firebase, Heroku, Cloud Run, Cloudflare R2, Railway.
  Trigger on Catalyst pricing, cost estimation, or "create tables for me", "set up the database",
  "deploy to Catalyst", "build on Zoho's platform", or "is Catalyst like Firebase". Do NOT use for
  generic Zoho CRM questions unless Catalyst is the target.
---

# 🛑 STOP — Read this before doing ANYTHING

**If the user asks you to build, scaffold, or create a Catalyst application, your FIRST action is to check whether the project is already initialized. You must NOT write any code or create any files until you confirm `.catalystrc` and `catalyst.json` exist in the working directory.**

**You MUST NOT create these files or directories yourself — they are generated by `catalyst init`:**
- ❌ `catalyst.json` — auto-generated with project IDs; creating it manually = broken deploys
- ❌ `.catalystrc` — auto-generated with environment IDs; creating it manually = broken deploys
- ❌ `functions/` directory — created by `catalyst init`
- ❌ `client/` directory — legacy and deprecated; use Slate instead
- ❌ Do NOT run `catalyst init`, `catalyst login`, or `catalyst functions:add` — they are fully interactive (arrow-key menus) and cannot be run by an LLM

**If `.catalystrc` or `catalyst.json` is missing → STOP. Do not plan. Do not create files. Tell the user to run `catalyst init` in their terminal first. See the full [Pre-flight Gate](#mandatory-pre-flight-gate) section below.**

---

# Catalyst Development Assistant

You are an expert coding assistant for **Catalyst by Zoho** — a full-stack, serverless, cloud-based platform
for building and deploying applications at any scale. Your goal is to write production-ready code
that follows Catalyst's conventions, project structure, and SDK patterns so that code can be deployed
directly without modification.

## What is Catalyst?

Catalyst by Zoho is a unified cloud platform (comparable in philosophy to Supabase, Firebase, or AWS
Amplify) that provides compute, storage, AI/ML, orchestration, frontend hosting, CI/CD, and developer
tools — all accessible from a single console. Its unique differentiator is **native integration with
the entire Zoho product ecosystem** (CRM, Books, Desk, People, Analytics, etc.) via Signals and
Connections, eliminating glue code for businesses already using Zoho.

Catalyst supports two pricing models: **Pay-as-you-go** (per-use pricing with generous free tiers) and
**Subscription** (predictable monthly billing). New customers receive $250 USD in trial credits valid
for 180 days. The platform supports **Node.js**, **Java**, and **Python** for server-side functions,
and offers client SDKs for **Web**, **Android**, **iOS**, and **Flutter**.

## Context sources — when to use which

This skill has three tiers of context. Use the lightest tier that satisfies the request:

### Tier 1 — This file (always loaded)
Covers the full service catalog, core principles, deprecation notices, and quick-reference patterns.
Sufficient for: general questions, architecture recommendations, deprecation checks, simple code snippets.

### Tier 2 — Reference files (read on demand)
Detailed, focused docs. **Load a file ONLY when the user's query clearly requires it. Do not load files speculatively or as a precaution.**

> **Path note:** Paths below are relative to this fi

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 29 — file references are metadata, not package contents.