Cronus UI

List the installable Cronus UI components (registry items of type 'registry:ui'). Returns each component's name, a readable title, its npm and registry dependencies, and the `npx cronus-ui add <name>` command to install it.

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

List the installable Cronus UI blocks (registry items of type 'registry:block') — larger, composed sections such as hero, pricing, login, and dashboard. Returns each block's name, title, dependencies, and its `npx cronus-ui add <name>` install command.

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Return compact Hydra-ready cards for every component, block, variant, and template: name, short description, design style, palette, motion, intents, and the install command. No source files — cheap on tokens. Filter with `kind`. Use `match_catalog` to pick the best item for a prompt (login + smooth animation, etc.).

{
  "type": "object",
  "properties": {
    "kind": {
      "description": "Restrict to component, block, variant, or template cards.",
      "type": "string",
      "enum": [
        "component",
        "block",
        "variant",
        "template"
      ]
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Two-query catalog match for low-context agents. Pass a free-text `query` (e.g. 'login page with smooth animation') and/or structured filters (`intent`, `motion`, `style`, `palette`). Returns `pick` (the recommended combination), `intent` hits, `motion` hits, and ranked `matches`. Cards carry description, design style, palette, motion, and intents — not source. Fetch source with `get_component` only after picking a name.

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Natural-language request, e.g. 'login page with smooth animation'. Intent and motion are inferred from the text when those fields are omitted.",
      "type": "string"
    },
    "intent": {
      "description": "Use-case intent: login, signup, pricing, dashboard, chart, form, …",
      "type": "string"
    },
    "style": {
      "description": "Design style: default, editorial, operational, glass, brutalist.",
      "type": "string"
    },
    "palette": {
      "description": "Palette: semantic (follows theme), aurora, neutral, midnight, sunset, emerald.",
      "type": "string"
    },
    "motion": {
      "description": "Motion: none, snappy, smooth, cinematic.",
      "type": "string"
    },
    "kind": {
      "description": "Restrict to component, block, variant, or template.",
      "type": "string",
      "enum": [
        "component",
        "block",
        "variant",
        "template"
      ]
    },
    "limit": {
      "description": "Max hits per list. Default 8.",
      "type": "integer",
      "minimum": 1,
      "maximum": 24
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Fuzzy-search Cronus UI components and blocks by name (case-insensitive substring match). Use this to find the right item before fetching its source with `get_component`.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search text matched against component and block names, e.g. 'button' or 'card'."
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Return the Cronus UI visual taste file (DESIGN.md) for a theme × look. Use this before generating UI so the agent follows Aurora/Neutral dual identity, one primary CTA, hairline elevation, and look rules. compact fits a system prompt; extended is the repo file. Does not modify the project.

{
  "type": "object",
  "properties": {
    "theme": {
      "description": "Palette: aurora (generated product), neutral (docs chrome), midnight, sunset, emerald.",
      "type": "string",
      "enum": [
        "aurora",
        "neutral",
        "midnight",
        "sunset",
        "emerald"
      ]
    },
    "look": {
      "description": "Material: default, brutalist, or glass. Orthogonal to theme.",
      "type": "string",
      "enum": [
        "default",
        "brutalist",
        "glass"
      ]
    },
    "format": {
      "description": "compact (~prompt) or extended (full DESIGN.md). Default extended.",
      "type": "string",
      "enum": [
        "compact",
        "extended"
      ]
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Fetch the full detail for a single Cronus UI component or block by name: its source file(s) (path + content), its npm `dependencies`, its `registryDependencies` (other registry items it needs), and the `npx cronus-ui add <name>` install command. Works for both components and blocks.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "The exact registry item name, e.g. 'button', 'data-table', or 'pricing'."
    }
  },
  "required": [
    "name"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Build the `npx cronus-ui add ...` command for one or more components/blocks. The CLI resolves and installs each item's registry dependencies automatically. This only returns the command string — to actually install, use `install_component`.

{
  "type": "object",
  "properties": {
    "names": {
      "minItems": 1,
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "One or more registry item names to install, e.g. ['button', 'card', 'dialog']."
    }
  },
  "required": [
    "names"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}