ClaudeSuperPower
SubmitLog in

catalyst-slate

Skill

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', 'cross-domain Slate to function', or ANY request to run/serve/start

0Frontend

Install

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

What is catalyst-slate?

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', 'cross-domain Slate to function', or ANY request to run/serve/start the frontend app locally (\"start the server locally\", \"run the app\", \"start the dev server\"). Do NOT use for backend APIs or server-side logic — use catalyst-appsail or catalyst-functions instead.

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

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

Documentation

README · ~3 min read

🚦 To run the app locally, use plain catalyst serve

For any "start the server / run the app / start locally" request, prefer plain catalyst serve (no --only) — it serves the whole project (Slate + Functions + AppSail) so the frontend can call your own backend. NEVER run the native dev server (npm run dev, vite, next dev, ng serve, …); it skips the Catalyst wrapper (/__catalyst/sdk/init.js, session cookie, ZAID, managed-service proxy), so auth, getCurrentUser, and session-backed calls silently fail though the UI renders — the #1 "auth broken locally" cause. Scope with --only/--except (e.g. --only slate) when a full serve errors out, or to isolate/speed up one component. Details: references/slate-basics.md → CLI Commands; auth testing: ../catalyst-authentication/.

How It Works

Before the MCP calls below, establish context once per session via the workspace readiness gate: ../catalyst-basics/references/preflight.md. It resolves and reconciles the org/project so CatalystbyZoho_List_All_Slate_Apps uses the correct project ID.

  1. Check if Slate is activated — Use MCP: call CatalystbyZoho_List_All_Slate_Apps with the project ID.
    • If it returns apps or an empty list → Slate is activated. Proceed.
    • If it returns an error or "not found" → Slate needs a one-time activation. Tell the user:

      "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." Wait for confirmation, then proceed.

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.

Subagents

All subagents →

code-architect

Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences

32.8K stars

plugin-validator

Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: <example> Context: User f

32.8K stars

scan-inventory

Restricted read-only repository cartographer dispatched by the Claude Security scan workflow to partition the tree into components and account for every top-level directory; not for direct invocation or vulnerability research.

32.8K stars