catalyst-basics

Name: catalyst-basics
Author: catalystbyzoho

72installs6forks

How to install catalyst-basics?

catalystbyzoho/agent-skills/catalyst-basics

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

Installs into the current project.

Summary

Core Catalyst project setup — directory structure, environments, CLI commands, and all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, Org ID). Trigger on 'start a Catalyst project', 'what is .catalystrc', 'where do I find my Table ID', 'difference between Development and P

Files · 1

View on GitHub

SKILL.md

1	> ⚠️ PRE-FLIGHT CHECK: Before creating any project files, confirm that `.catalystrc` and
2	> `catalyst.json` exist in the project directory. If they don't:
3	> 1. Use MCP (`CatalystbyZoho_List_All_Organizations` → `CatalystbyZoho_List_All_Projects`) to get the org ID and project ID.
4	> 2. Run: `catalyst init --org <orgId> -p <projectId> -ni`
5	> 3. Never ask the user to run `catalyst init` interactively. Never create these files manually — they are CLI-generated and must come from the CLI.
6
7	## How It Works
8
9	1. 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.
10	2. New to Catalyst? — If the user is setting up Catalyst for the first time or asking "how do I start", load `references/quick-start.md` for the full walkthrough.
11	3. 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`.
12	4. Pre-flight — Confirm `.catalystrc` and `catalyst.json` exist. If missing, use MCP to get org/project IDs and run `catalyst init --org <orgId> -p <projectId> -ni`. Never use interactive `catalyst init`.
13	5. Project structure — Load `references/project-basics.md` for directory layout, `catalyst.json`, IDs, and dev-to-prod checklist.
14	6. CLI questions — Load `references/cli.md` for the exact command, flags, and safety rules.
15	7. Answer — Provide the specific ID path or CLI command needed. Never ask the user to manually look up IDs when MCP is connected.
16
17	## Triggers
18
19	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.
20
21	## 🔌 MCP Connection Check (Do This Before Anything Else)
22
23	Before reading `.catalystrc`, asking the user for IDs, or doing anything project-related — check whether Zoho MCP tools are available in your tool list.
24
25	Look for tools prefixed with `CatalystbyZoho_` (e.g., `CatalystbyZoho_List_All_Projects`, `CatalystbyZoho_List_All_Tables`).
26
27	If MCP tools ARE available:
28	- Use `CatalystbyZoho_List_All_Organizations` to get the org ID
29	- Use `CatalystbyZoho_List_All_Projects` to get the project ID
30	- Use MCP tools to fetch table names, bucket names, ZAIDs, and all other project details directly — do NOT ask the user to copy-paste IDs from the console
31
32	If MCP tools are NOT available:
33	- Prompt the user to connect Zoho MCP before proceeding
34	- Guide them to: VS Code → Settings → MCP (or Claude Desktop `claude_desktop_config.json`) and add the Catalyst MCP server
35	- Fall back to reading `.catalystrc` and `catalyst.json` from the local project directory only as a last resort
36
37	> Never 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.
38
39	## References
40
41	Load the relevant reference file for detailed information:
42
43	\| Reference \| Contents \|
44	\|-----------\|----------\|
45	\| `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 \|
46	\| `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 \|
47	\| `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.) \|
48	\| `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 \|
49	\| `references/architecture.md` \| Service selection guide — which Catalyst ser

People who liked this also viewed

6 picks

Type

catalyst-basics

72installs6forks

View on GitHub

How to install catalyst-basics?

catalystbyzoho/agent-skills/catalyst-basics

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	> ⚠️ PRE-FLIGHT CHECK: Before creating any project files, confirm that `.catalystrc` and
2	> `catalyst.json` exist in the project directory. If they don't:
3	> 1. Use MCP (`CatalystbyZoho_List_All_Organizations` → `CatalystbyZoho_List_All_Projects`) to get the org ID and project ID.
4	> 2. Run: `catalyst init --org <orgId> -p <projectId> -ni`
5	> 3. Never ask the user to run `catalyst init` interactively. Never create these files manually — they are CLI-generated and must come from the CLI.
6
7	## How It Works
8
9	1. 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.
10	2. New to Catalyst? — If the user is setting up Catalyst for the first time or asking "how do I start", load `references/quick-start.md` for the full walkthrough.
11	3. 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`.
12	4. Pre-flight — Confirm `.catalystrc` and `catalyst.json` exist. If missing, use MCP to get org/project IDs and run `catalyst init --org <orgId> -p <projectId> -ni`. Never use interactive `catalyst init`.
13	5. Project structure — Load `references/project-basics.md` for directory layout, `catalyst.json`, IDs, and dev-to-prod checklist.
14	6. CLI questions — Load `references/cli.md` for the exact command, flags, and safety rules.
15	7. Answer — Provide the specific ID path or CLI command needed. Never ask the user to manually look up IDs when MCP is connected.
16
17	## Triggers
18
19	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.
20
21	## 🔌 MCP Connection Check (Do This Before Anything Else)
22
23	Before reading `.catalystrc`, asking the user for IDs, or doing anything project-related — check whether Zoho MCP tools are available in your tool list.
24
25	Look for tools prefixed with `CatalystbyZoho_` (e.g., `CatalystbyZoho_List_All_Projects`, `CatalystbyZoho_List_All_Tables`).
26
27	If MCP tools ARE available:
28	- Use `CatalystbyZoho_List_All_Organizations` to get the org ID
29	- Use `CatalystbyZoho_List_All_Projects` to get the project ID
30	- Use MCP tools to fetch table names, bucket names, ZAIDs, and all other project details directly — do NOT ask the user to copy-paste IDs from the console
31
32	If MCP tools are NOT available:
33	- Prompt the user to connect Zoho MCP before proceeding
34	- Guide them to: VS Code → Settings → MCP (or Claude Desktop `claude_desktop_config.json`) and add the Catalyst MCP server
35	- Fall back to reading `.catalystrc` and `catalyst.json` from the local project directory only as a last resort
36
37	> Never 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.
38
39	## References
40
41	Load the relevant reference file for detailed information:
42
43	\| Reference \| Contents \|
44	\|-----------\|----------\|
45	\| `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 \|
46	\| `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 \|
47	\| `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.) \|
48	\| `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 \|
49	\| `references/architecture.md` \| Service selection guide — which Catalyst ser

People who liked this also viewed

6 picks

Type