integrate
Use to design an integration between two systems. Pattern selection (sync/async/event/batch), error handling, idempotency, observability. Output is a plan + scaffold.
What this skill does
# integrate Integration design. Pattern selection drives everything else. ## Pattern selection matrix | Pattern | When | Tools | |---|---|---| | Sync request-reply | UI need-to-know now; idempotent fast | HTTP | | Async fire-forget | Downstream slow; UI doesn't wait | queue / event | | Pub/sub | Many consumers; real-time | Kafka / Pub/Sub API | | Batch | Volume; off-hours | Bulk API / S3 / SFTP | | CDC | DB-to-DB low-latency | Debezium / CDC | | Streaming | Continuous events | gRPC stream / WebSocket | Pick first; the rest of the design flows from this. ## Method 1. **Source + sink.** What's emitting; what's consuming. 2. **Volume + latency requirements.** RPS, p95 latency budget. 3. **Failure tolerance.** Loss-tolerant? Once-and-only? At-least-once? 4. **Ordering.** Required? Per-key? Global? 5. **Pattern pick.** From the matrix. 6. **Design:** - Auth between source and sink - Idempotency strategy (key, dedup window) - Retry policy (backoff, max attempts, dead-letter) - Observability (correlation id, latency histogram, error rate) - Schema evolution (versioning of the message shape) 7. **Scaffold.** Producer + consumer code skeletons. 8. **Test.** Contract test + chaos test (downstream slow/down). ## Output shape ``` # Integration: <source> → <sink> ## Requirements - Volume: <RPS> - Latency p95: <ms> - Loss tolerance: <yes | no, exactly-once required> - Ordering: <none | per-key | global> ## Pattern <chosen> — because <reason> ## Design - Auth: <how> - Idempotency: <key, dedup window> - Retry: <policy> - Observability: - Correlation: X-Request-Id propagated - Metrics: latency histogram, error rate, queue depth - Logs: structured ndjson w/ ids - Schema versioning: <strategy> ## Failure modes | Mode | Detection | Recovery | |---|---|---| | Downstream down | <signal> | <action> | | Downstream slow | <signal> | <action> | | Bad message | <signal> | DLQ + alert | ## Scaffold - Producer: <path> - Consumer: <path> - Schema: <path> ## Test plan - Contract: <path> - Chaos: <path — uses /siftcoder:chaos> ## Memory Captured: <id> ``` ## Rules - **Pattern picked first.** Backwards engineering = wasted code. - **Failure-mode table mandatory.** "What happens if downstream is slow" must be answered upfront. - **Idempotency for at-least-once.** No exceptions. - **Observability not optional.** Correlation ids, metrics, structured logs. ## Anti-patterns - Sync request-reply where async would do (back-pressure pain) - Async without idempotency (duplicates inevitable) - "We'll add monitoring later" (you won't until incident) - Schema with no versioning strategy ## When NOT to use - Same-process function call — not an integration - Internal-only RPC inside a single deploy unit (lighter) - Salesforce-internal — `/siftcoder:salesforce-flow` may cover ## Subagent dispatch - `Plan` for the design - `chaos` skill for failure mode design - `api` skill if a new API is part of the integration ## Value over native CC CC will design integrations. CC won't naturally force pattern-pick upfront, require failure-mode tables, or mandate observability. The structure IS the value — keeps integrations from becoming silent failure machines.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.