catalyst-appsail

How It Works

1. Identify the runtime — Managed runtime (Node.js, Java, Python) or custom Docker container.

2. Load references/appsail-basics.md — for PORT config, project structure, and Dockerfile requirements. For deploy commands and environment variables, load references/appsail-deploy.md.

3. PORT rule — Always use process.env.X_ZOHO_CATALYST_LISTEN_PORT, never hardcode PORT or 3000.

4. AppSail vs Functions decision — If the user is unsure which to use, apply this matrix:

   	Catalyst Functions	AppSail
   Code structure	Catalyst-specific templates required	Any framework, any format, fully independent
   Use case	HTTP handlers, events, cron, Zoho integrations	Persistent servers, long-running processes, Docker
   Billing	Per API call	Per instance uptime
   Dependency management	Handled by Catalyst	You manage all libraries and frameworks

Triggers

Use this skill for: "AppSail", "persistent server", "Docker on Catalyst", "backend hosting", X_ZOHO_CATALYST_LISTEN_PORT, appsail:add, "catalyst managed runtime", "deploy Express app", "AppSail vs Functions", "long-running process on Catalyst", or "containerized app on Catalyst".

References

Reference	Load when the query is about…
references/appsail-basics.md	Runtimes, project structure, app-config.json fields, Node.js/Docker templates, SDK version
references/appsail-deploy.md	Deployment commands (Path A/B/C), env variables, health checks, AppSail URL pattern, configurations
references/appsail-crossorigin.md	Slate + AppSail cross-origin errors, CORS setup via MCP, catalyst_auth, custom domain SSL