LLM Prompts to have best practices in MuleSoft

Use the following rules/prompts/instructions to generate best practices using LLM agents for your Mule project. Add src/test/resources/embedded* to the .gitignore file (if any) and remove the files inside these embedded folders Do not modify the pom.xml file unless specifically requested by prompt Do not modify the README.md file unless specifically requested by prompt Create properties files per environment if not already created under src/main/resources Use YAML files for the properties files instead of .properties unless specified otherwise Make sure the environment properties files are added to the configuration properties in global elements Make sure an env global property is created in global elements The environment properties files are defined as global elements, making use of the env global property to do the switch between properties Make sure all the global elements are listed under a global.xml file and not in the specific flows files - Follow naming conventions

Apr 7, 2025 - 19:14

Use the following rules/prompts/instructions to generate best practices using LLM agents for your Mule project.

Add src/test/resources/embedded* to the .gitignore file (if any) and remove the files inside these embedded folders
Do not modify the pom.xml file unless specifically requested by prompt
Do not modify the README.md file unless specifically requested by prompt
Create properties files per environment if not already created under src/main/resources
Use YAML files for the properties files instead of .properties unless specified otherwise
Make sure the environment properties files are added to the configuration properties in global elements
Make sure an env global property is created in global elements
The environment properties files are defined as global elements, making use of the env global property to do the switch between properties
Make sure all the global elements are listed under a global.xml file and not in the specific flows files