Explore
Browse and search prompts, skills, and rules from the community.
31 results
Property Placeholders for Environment Config
Use property placeholders and separate config files for each environment.
Implement Global Error Handling
Every Mule application must have a global error handler with proper exception strategy.
Circuit Breaker for External Calls
Apply circuit breaker pattern for all calls to external systems to prevent cascade failures.
Structured JSON Logging
Use structured JSON logging format for all log messages to enable proper observability.
Do NOT Search Exchange for Agents or MCP Servers
Agent Network components and MCP servers are external services, not Exchange assets.
Use Mule Domains for Shared Configurations
Use Mule Domains to share global configurations like error handlers, properties, and connection configs.
Use DataWeave 2.0 for All Transformations
Always use DataWeave 2.0 for data transformations instead of other methods.
Never Hardcode Credentials
Use property placeholders for all environment-specific values; never hardcode credentials or secrets.
Use GA Connector Versions Only
Always use General Availability connector versions; avoid BETA, SNAPSHOT, or experimental versions.
Target Mule Runtime 4.10+
Only use Mule Runtime Version 4.10.0 or later for all implementations.
Prefer Anypoint Connectors Over HTTP
Use platform-provided Anypoint Connectors instead of raw HTTP requests when a connector is available.
Use kebab-case for Projects and Flows
Follow MuleSoft naming conventions: kebab-case for project and flow names, camelCase for DataWeave.
Write MUnit Tests for All Flows
Every flow and critical DataWeave transformation must have corresponding MUnit tests.
Use ObjectStore for Stateful Integrations
Use ObjectStore for any integration that requires persistence across requests.
Follow API-Led Connectivity Pattern
Organize APIs into System, Process, and Experience layers following MuleSoft's recommended architecture.
MuleSoft General Rules (combined)
A set of generic rules that should be applied on every Mule development task
Target Mule Runtime 4.10+
Only use Mule Runtime Version 4.10.0 or later for all implementations.
Prefer Anypoint Connectors Over HTTP
Use platform-provided Anypoint Connectors instead of raw HTTP requests when a connector is available.
Use kebab-case for Projects and Flows
Follow MuleSoft naming conventions: kebab-case for project and flow names, camelCase for DataWeave.
Write MUnit Tests for All Flows
Every flow and critical DataWeave transformation must have corresponding MUnit tests.
Use ObjectStore for Stateful Integrations
Use ObjectStore for any integration that requires persistence across requests.
Property Placeholders for Environment Config
Use property placeholders and separate config files for each environment.
Implement Global Error Handling
Every Mule application must have a global error handler with proper exception strategy.
Circuit Breaker for External Calls
Apply circuit breaker pattern for all calls to external systems to prevent cascade failures.
Structured JSON Logging
Use structured JSON logging format for all log messages to enable proper observability.
Do NOT Search Exchange for Agents or MCP Servers
Agent Network components and MCP servers are external services, not Exchange assets.
Use Mule Domains for Shared Configurations
Use Mule Domains to share global configurations like error handlers, properties, and connection configs.
Follow API-Led Connectivity Pattern
Organize APIs into System, Process, and Experience layers following MuleSoft's recommended architecture.
Use DataWeave 2.0 for All Transformations
Always use DataWeave 2.0 for data transformations instead of other methods.
Never Hardcode Credentials
Use property placeholders for all environment-specific values; never hardcode credentials or secrets.
Use GA Connector Versions Only
Always use General Availability connector versions; avoid BETA, SNAPSHOT, or experimental versions.