ClaudeSuperPower
SubmitLog in

catalyst-basics

Skill

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 Production', or any C

0Automation

Install

git clone https://github.com/catalystbyzoho/claude-plugin.git ~/.claude/skills/catalyst-basics

What is catalyst-basics?

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 Production', or any Catalyst ID or CLI question.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~82 tokens of context used while enabled, before you invoke anything

Documentation

README · ~4 min read

⚠️ PRE-FLIGHT CHECK: Before creating any project files, confirm that .catalystrc and catalyst.json exist in the project directory. If they don't:

  1. Use MCP (CatalystbyZoho_List_All_Organizations → CatalystbyZoho_List_All_Projects) to list orgs/projects.
  2. 🔒 Never assume the org/project. If there is no project initialized, or the project is ambiguous, STOP and ask the user which project (and org) to work in — a single project in the list is not permission to auto-select it; confirm first. Never infer the project from the directory name or a past session. (Full rule: references/preflight.md → Golden Rule.)
  3. Only after the project is resolved and confirmed run: catalyst init --org <orgId> -p <projectId> -ni
  4. Never ask the user to run catalyst init interactively. Never create these files manually — they are CLI-generated and must come from the CLI.

Always run the catalyst CLI in non-interactive mode. Every command takes a -ni / --non-interactive flag (or set ZCATALYST_NON_INTERACTIVE=1; requires CLI v1.27.0+) and accepts its inputs as flags, so the CLI never prompts. Interactive menus exist for humans only — agents must never rely on them. The one exception is catalyst login, whose browser OAuth step needs the user. See the required flags per command in references/cli.md.

How It Works

  1. Pre-flight first — Establish and verify org/project context per the canonical sequence in references/preflight.md (read .catalystrc for org/project, confirm parity with MCP, or resolve via MCP if .catalystrc is absent). Use MCP for all other resource IDs instead of asking the user.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.