integration-patternslisted

# Integration Patterns Reference documentation for building Prismatic Code Native Integrations (CNI). <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 ### Standard Integration Pattern - Components accessed via manifests and componentRegistry - Standard connection configuration - Any component/manifest combination ## Component Manifest Pattern All components are accessed via manifests: 1. Install: `npx cni-component-manifest <component-key>` 2. Register in componentRegistry.ts with `componentManifests()` 3. Import actions and call `.perform()`: `import slackActions from "./manifests/slack/actions"; await slackActions.postMessage.perform({...})` - See `references/manifest-pattern.md` ## Config Mantra Every config element MUST use w