AI SummaryReference documentation for building Prismatic Code Native Integrations (CNI). 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. All components are accessed via manifests:
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "integration-patterns" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/integration-patterns && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/integration-patterns/SKILL.md "https://raw.githubusercontent.com/prismatic-io/prismatic-skills/main/skills/integration-patterns/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Architecture patterns, manifest usage, code generation guides, and reference documentation for building Prismatic Code Native Integrations.
Phase 2: Requirements Gathering
• Spec items now carry agent_context (narration backbone), implications (per-option consequence maps), and docs (Prismatic doc URLs). The agent uses these inline — no external references needed for most questions. Docs are fetched on demand only when agent_context is insufficient or the user asks a follow-up beyond what the curated content covers.
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>
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: • Install: npx cni-component-manifest <component-key> • Register in componentRegistry.ts with componentManifests() • Import actions and call .perform(): import slackActions from "./manifests/slack/actions"; await slackActions.postMessage.perform({...}) • See references/manifest-pattern.md
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster