mule-api-designDesign, author, revise, or assess consumer-facing MuleSoft HTTP API contracts in RAML 1.0 or OpenAPI 3.0 using explicit resource, method, URI, data, error, security, compatibility, and governance decisions. Use for API design workshops, URL and naming guidance, new RAML/OAS contracts, contract-first
mule-buildValidate, test, package, and locally run a MuleSoft Mule 4 application using its established repository commands and configured build tools, and prepare versions, hotfix qualifiers, and commits only when explicitly requested. Use for local build validation, static analysis, MUnit execution, deployab
mule-connectorsAnswer connector-specific behavior questions in Mule 4: which connection types and authentication flows a connector version supports, token and endpoint rules, the run-as identity, account or licence limits, subscription sources and replay, reconnect and token renewal, log signatures that are benign
mule-dependenciesLook up the current release, minimum Mule runtime, and Java support of Mule connectors, modules, MUnit, and the Mule Maven plugin, and check a project's dependencies for upgrades. Use when asked for the latest connector or plugin version, whether a connector works with a Mule runtime or Java version
mule-developmentCreate or modify MuleSoft Mule 4 production flows, DataWeave, APIKit routing, error handling, connectors, queues, batch jobs, and configuration using evidence-based project conventions and post-change validation. Use when implementing Mule application behavior or aligning implementation to an existi
mule-docsAnalyze MuleSoft Mule 4 repositories and create or update evidence-backed Markdown documentation with Mermaid diagrams. Use for project overviews, architecture and flow documentation, documenting existing API contracts, connector and DataWeave documentation, configuration guides, onboarding, deploym
mule-opsAssess MuleSoft runtime health across one or more applications from Anypoint logs, metrics, deployment state, audit history, and cross-system correlation, and plan, apply, and watch an authorized release, hotfix, rollback, or change to a running app (version, settings, secrets, runtime, integration
mule-reviewReview MuleSoft Mule 4 working changes, commit ranges, branches, pull requests, whole repositories, or release readiness and return prioritized evidence-backed findings with remediation options. Use for code review, PR review, project health audits, architecture and contract consistency checks, inci
mule-testingCreate, repair, and refactor behavior-focused MUnit tests for MuleSoft Mule 4 applications, including event setup, fixtures, mocks, spies, assertions, error expectations, and test-only build configuration. Use when adding missing MUnit coverage, diagnosing or fixing a failing MUnit test, preserving
mule-troubleshootingDiagnose MuleSoft incidents and produce evidence-backed root-cause assessments or fix plans for timeouts, connection failures, rate limits, concurrency, batch processing, queues, deployment transitions, platform-initiated restarts, lost or delayed events, memory pressure, and cross-application error