integration-scaffolder
Install
Pick the surface you use. Plugins run inside Claude Code, which is available in the terminal CLI, the desktop app on Mac and Windows, the web app at claude.ai/code, and the VS Code and JetBrains extensions. The slash commands are identical on every surface.
From inside any Claude Code session — terminal, desktop app, web app, or IDE extension:
-
Add the RBA Skills marketplace (only needed once per machine):
/plugin marketplace add rbaconsulting/rba-skills-plugin -
Install integration-scaffolder:
/plugin install integration-scaffolder@rba-ai-hub -
Activate it without restarting:
/reload-plugins
Prefer to browse and click? Run /plugin inside Claude Code to open the interactive plugin manager. It looks the same in the desktop app, web app, terminal, and IDE extensions.
-
Open the plugin manager:
/plugin - Press Tab to reach Marketplaces, choose Add, then enter
rbaconsulting/rba-skills-plugin. - Press Tab again to Discover. Search for
integration-scaffolder, press Enter, and pick a scope (User, Project, or Local). - Run
/reload-pluginsto activate it.
If you have the Claude Code CLI installed and want to drive it from a normal shell prompt:
$ claude plugin marketplace add rbaconsulting/rba-skills-plugin
$ claude plugin install integration-scaffolder@rba-ai-hub The next Claude Code session loads it automatically.
Overview
Integration & API Scaffolder
Integration engineering represents ~85% of effort on any DXP program. This plugin turns that effort into a repeatable, auditable discipline — generating production-ready specs, client scaffolds, data contracts, resilience patterns, and monitoring baselines for the full CMS↔CRM↔commerce↔search↔CDP integration mesh common to every RBA engagement.
What's inside
| Artifact | What it does |
|---|---|
integration-api-spec skill |
Produces an OpenAPI 3.1 or AsyncAPI 3.0 spec for a new integration endpoint, including authentication, rate-limiting headers, error schemas, and pagination contracts. |
integration-data-mapping skill |
Authors a canonical data-mapping contract (source → canonical → target) with field-level transformation rules, null handling, and a JSON Schema or TypeScript type that both sides can reference. |
integration-client-scaffold skill |
Generates a typed API client (TypeScript or C#) wired to Azure API Management, including retry decorators, bearer-token refresh, and structured logging. |
integration-error-resilience skill |
Designs the full error-handling and resilience layer: HTTP status taxonomy, retry/back-off policies, circuit-breaker thresholds, dead-letter queue routing, and idempotency keys. |
integration-monitoring-observability skill |
Defines the observability baseline — Azure Application Insights queries, distributed trace propagation headers, alert thresholds, and a runbook template for on-call engineers. |
integration-reviewer agent |
Subagent that performs a structured code review on any integration PR: checks contract drift, least-privilege permissions, resilience coverage, and observability hooks. |
/scaffold-integration command |
Entry-point slash command — takes a one-line description of the integration and fans out to the relevant skills in the right order. |
When to use this plugin
Install it on any project where you need to connect two or more of:
- CMS: Sitecore XM Cloud, Optimizely CMS 12/SaaS, Umbraco 13+, WordPress
- CRM / ERP: Microsoft Dynamics 365, Salesforce, HubSpot
- Commerce: commercetools, Sitecore OrderCloud, Optimizely Configured Commerce
- Search: Coveo, Azure AI Search, Algolia
- CDP / Personalization: Sitecore CDP, Segment, mParticle, Adobe Target (via tag manager)
- iPaaS / Middleware: Azure Logic Apps, Azure Service Bus, Azure API Management, MuleSoft
It is platform-agnostic by design — each skill generates a canonical spec first, then a platform-specific adapter block. Swap adapters without re-authoring the contract.
How to install
claude plugin install integration-scaffolder@rba-ai-hub
Once installed, trigger any skill directly (/integration-api-spec, /integration-data-mapping, etc.) or use the entry-point command:
/scaffold-integration "Connect Sitecore XM Cloud content updates to Dynamics 365 contact enrichment via Azure Service Bus"
Permissions required
Each skill uses least-privilege tools scoped to:
Read,Write,Edit,Grep,Glob— file scaffoldingBash(git *)— branch status, diff inspectionWebFetch(domain:learn.microsoft.com),WebFetch(domain:spec.openapis.org),WebFetch(domain:www.asyncapi.com),WebFetch(domain:docs.coveo.com)— spec lookups- No shell execution of compiled code, no credential directories, no database mutations
Azure / Microsoft-first context
RBA's default integration stack is Azure-native:
- Azure API Management — gateway, rate limiting, JWT validation, developer portal
- Azure Service Bus — durable async messaging, dead-letter queues, sessions for ordering
- Azure Logic Apps (Standard) — low-code orchestration with the hybrid deployment model for on-premises connectors
- Azure Application Insights + OpenTelemetry — end-to-end distributed tracing
- Azure Key Vault — secret storage (never inline credentials)
Skills generate Azure-first output by default with adapter blocks for other clouds (AWS, GCP) or on-premises middleware.
Bundled artifacts
Skills
- integration-api-spec — Produces a complete OpenAPI 3.1 or AsyncAPI 3.0 specification for a new DXP integration endpoint — including authentication scheme, rate-limit headers, error schema, pagination contract, and example payloads. Use when starting a new integration between any two systems (CMS, CRM, commerce, CDP, search) and needing an agreed-upon contract before a single line of implementation code is written.
- integration-client-scaffold — Generates a typed, production-ready API client (TypeScript or C#) for an integration endpoint, wired to Azure API Management with retry decorators, bearer-token refresh via MSAL, structured logging, and OpenTelemetry trace propagation. Use after integration-api-spec has produced the contract and you need the implementation scaffold — not the logic, just the reliable plumbing every integration client needs.
- integration-data-mapping — Authors a canonical data-mapping contract (source schema → canonical model → target schema) with field-level transformation rules, null/missing handling, type coercions, and a machine-readable JSON Schema or TypeScript type that both integration sides can import. Use when two systems need to exchange data and the field shapes, naming conventions, or data types differ — which is always.
- integration-error-resilience — Designs the complete error-handling and resilience layer for a DXP integration: HTTP/event status taxonomy, retry and back-off policies, circuit-breaker thresholds, dead-letter queue routing, idempotency key strategy, and poison-message handling. Use after the API spec and client scaffold exist — this skill turns the "what happens when it breaks" question into concrete, testable code patterns.
- integration-monitoring-observability — Defines the observability baseline for a DXP integration: Azure Application Insights KQL queries, distributed trace propagation configuration, alert thresholds, a Kusto dashboard definition, and an on-call runbook template. Use after the client scaffold and resilience design are in place — observability is the last piece before a new integration goes to staging.
Agents
- integration-reviewer — Subagent that performs a structured code review on any integration PR or diff: checks API contract drift against the spec, verifies resilience patterns are complete, confirms observability hooks are in place, and flags least-privilege and credential hygiene issues. Invoke via the scaffold-integration command or directly on a PR branch.
Slash Commands
- /scaffold-integration — Entry-point slash command for the Integration & API Scaffolder plugin. Takes a one-line description of an integration and orchestrates the skills in the correct order: spec → data mapping → client scaffold → error resilience → monitoring. Run this first on any new integration before writing implementation code.
Technical details
- Homepage
- https://rba-skills.tylerschroeder.net/plugins/integration-scaffolder/
- License
- MIT
- Maturity
- experimental
- Security review
- No security review
- Owners
-
- engineering
- Disciplines
- engineering
- Lifecycle
- build
- Tags
- Last updated
- by Tyler Schroeder
- Source
plugins/integration-scaffolder/
Edit this plugin's README on GitHub — opens GitHub's web editor. No git knowledge needed.