component-patterns

# Component Patterns Reference documentation for building Prismatic custom components. <disallowed-tools> Do NOT use these MCP tools — they return incomplete data that causes broken scaffolds and missing connections downstream. A hook will deny them, but avoid the wasted round trip. - `mcp__prism__prism_components_list` — Use `run.ts find-components <keyword>` instead - `mcp__prism__prism_components_init` — Use `run.ts scaffold-component` instead - `mcp__prism__prism_components_publish` — Use `run.ts publish-component` instead - `mcp__prism__prism_components_generate_manifest` — Manifests are auto-generated during scaffolding - `mcp__prism__prism_install_component_manifest` — Handled by `run.ts scaffold-project --components` - `mcp__prism__prism_install_legacy_component_manifest` — Handled by `run.ts scaffold-project --components` </disallowed-tools> ## Architecture Patterns ### Connector Components - Wrap external APIs (Salesforce, Canny, HubSpot, etc.) - Support OAuth2, API Key, Bearer Token, Basic Auth - Define connections, actions, triggers, and data sources - Installed via Prism CLI ### Utility Components - Provide helper actions (data transformation, formatting, etc.) - No external connections needed - Define only actions with typed inputs ## Config Mantra Components define their own inputs — not `configVar()` wrappers. Each action uses `input()` definitions directly: - `input()` for typed action inputs (label, type, required, comments, default) - `connection()`...