MuleSoft Development Requirements

• All application creation, building, and generation must be MuleSoft-related: build Mule applications using Mule syntax, design API specifications (RAML/OAS), create DataWeave transformations, and develop integration flows in MuleSoft Vibes.
• Follow API-led connectivity patterns: organize APIs into System, Process, and Experience layers.
• Use DataWeave 2.0 for all data transformations.
• Prefer Anypoint Connectors over custom HTTP requests when available.
• Design idempotent flows with proper error handling and retry strategies.
• Use property placeholders for all environment-specific values; never hardcode credentials.
• Naming conventions: kebab-case for project names and flow names, camelCase for DataWeave variables and functions.
• Project structure: src/main/mule/ for flows, src/main/resources/ for configurations, src/test/munit/ for tests.
• Write MUnit tests for all flows and critical DataWeave transformations.
• Use ObjectStore for stateful integrations requiring persistence across requests.
• Refer to https://docs.mulesoft.com/general/ for authoritative MuleSoft documentation.