catalyst-slate

Name: catalyst-slate
Author: catalystbyzoho

70installs6forks

How to install catalyst-slate?

catalystbyzoho/agent-skills/catalyst-slate

$npx -y skills add catalystbyzoho/agent-skills --skill catalyst-slate

Installs into the current project.

Summary

Catalyst Slate — Git-based frontend hosting for React, Next.js, Vue, Angular, Svelte, Astro, SolidJS, Preact and other frameworks with preview deploys. Trigger on 'Slate', 'frontend hosting', 'slate-config.toml', 'deploy React app', or 'cross-domain Slate to function'. Do NOT use

Files · 1

View on GitHub

SKILL.md

1	## How It Works
2
3	1. Check if Slate is activated — Use MCP: call `CatalystbyZoho_List_All_Slate_Apps` with the project ID.
4	- If it returns apps or an empty list → Slate is activated. Proceed.
5	- If it returns an error or "not found" → Slate needs a one-time activation. Tell the user:
6	> "Please open the Catalyst console, go to your project → Slate (left sidebar) → click Start Exploring. This is a one-time step that takes 5 seconds. Let me know when done and I'll continue."
7	Wait for confirmation, then proceed.
8	- Never fall back to Web Client (legacy) because Slate isn't activated yet. Web Client is deprecated — Slate is always the right choice for frontend hosting. The one-time activation is not a reason to change the approach.
9	> If Slate was not selected during `catalyst init`, run `catalyst slate:create --name <name> --framework <framework> --default` immediately after init. This command updates `catalyst.json` and prompts for the source directory automatically — it is faster than manual setup and should be the default recommendation.
10	2. Check if Slate app exists — If no app exists yet, run `catalyst slate:create --name <name> --framework <framework> -ni` to scaffold one. If Slate was not selected during `catalyst init`, run this immediately after init.
11	3. Load `references/slate-basics.md` — for framework setup, `slate-config.toml` format, and baseUrl configuration.
12	4. Cross-domain calls — If the query involves calling functions from a Slate app, apply the full URL + `generateAuthToken()` + CORS whitelist pattern.
13	> ⚠️ Migrating from basic client hosting? Relative paths like `/server/fn/execute` that worked in basic client silently break on Slate — Slate is served from `.onslate.com` while functions are on `.catalystserverless.com`. Every function call must become an absolute URL. Find and replace all relative `/server/...` paths with the full `https://<project>.catalystserverless.com/server/...` URL and add `generateAuthToken()` headers.
14	5. Deploy — `catalyst deploy slate <name> -ni` deploys to the current environment. Preview URLs are available after the build completes.
15
16	## Triggers
17
18	Use this skill for: "Slate", "frontend hosting", `catalyst slate`, `slate-config.toml`, "deploy React app", "Slate framework", `slate:create`, `slate deploy`, "frontend on Catalyst", "Slate vs Vercel", "cross-domain Slate to function", "Slate baseUrl", "Next.js on Catalyst", or "static frontend on Catalyst".
19
20	## References
21
22	\| Reference \| Load when the query is about… \|
23	\|-----------\|-------------------------------\|
24	\| `references/slate-basics.md` \| Framework setup, `slate-config.toml` gotchas, baseUrl config, CORS for Slate→function calls, Git deploy, CLI commands \|

People who liked this also viewed

6 picks

Type

catalyst-slate

70installs6forks

View on GitHub

How to install catalyst-slate?

catalystbyzoho/agent-skills/catalyst-slate

$npx -y skills add catalystbyzoho/agent-skills --skill catalyst-slate

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## How It Works
2
3	1. Check if Slate is activated — Use MCP: call `CatalystbyZoho_List_All_Slate_Apps` with the project ID.
4	- If it returns apps or an empty list → Slate is activated. Proceed.
5	- If it returns an error or "not found" → Slate needs a one-time activation. Tell the user:
6	> "Please open the Catalyst console, go to your project → Slate (left sidebar) → click Start Exploring. This is a one-time step that takes 5 seconds. Let me know when done and I'll continue."
7	Wait for confirmation, then proceed.
8	- Never fall back to Web Client (legacy) because Slate isn't activated yet. Web Client is deprecated — Slate is always the right choice for frontend hosting. The one-time activation is not a reason to change the approach.
9	> If Slate was not selected during `catalyst init`, run `catalyst slate:create --name <name> --framework <framework> --default` immediately after init. This command updates `catalyst.json` and prompts for the source directory automatically — it is faster than manual setup and should be the default recommendation.
10	2. Check if Slate app exists — If no app exists yet, run `catalyst slate:create --name <name> --framework <framework> -ni` to scaffold one. If Slate was not selected during `catalyst init`, run this immediately after init.
11	3. Load `references/slate-basics.md` — for framework setup, `slate-config.toml` format, and baseUrl configuration.
12	4. Cross-domain calls — If the query involves calling functions from a Slate app, apply the full URL + `generateAuthToken()` + CORS whitelist pattern.
13	> ⚠️ Migrating from basic client hosting? Relative paths like `/server/fn/execute` that worked in basic client silently break on Slate — Slate is served from `.onslate.com` while functions are on `.catalystserverless.com`. Every function call must become an absolute URL. Find and replace all relative `/server/...` paths with the full `https://<project>.catalystserverless.com/server/...` URL and add `generateAuthToken()` headers.
14	5. Deploy — `catalyst deploy slate <name> -ni` deploys to the current environment. Preview URLs are available after the build completes.
15
16	## Triggers
17
18	Use this skill for: "Slate", "frontend hosting", `catalyst slate`, `slate-config.toml`, "deploy React app", "Slate framework", `slate:create`, `slate deploy`, "frontend on Catalyst", "Slate vs Vercel", "cross-domain Slate to function", "Slate baseUrl", "Next.js on Catalyst", or "static frontend on Catalyst".
19
20	## References
21
22	\| Reference \| Load when the query is about… \|
23	\|-----------\|-------------------------------\|
24	\| `references/slate-basics.md` \| Framework setup, `slate-config.toml` gotchas, baseUrl config, CORS for Slate→function calls, Git deploy, CLI commands \|

People who liked this also viewed

6 picks

Type