//#region templates/v1/phase2/data-components.xml?raw
var data_components_default = "<data_components_section description=\"These are the data components available for you to use in generating responses. Each component represents a single structured piece of information. You can create multiple instances of the same component type when needed.\n\n***MANDATORY JSON RESPONSE FORMAT - ABSOLUTELY CRITICAL***:\n- WHEN DATA COMPONENTS ARE AVAILABLE, YOU MUST RESPOND IN JSON FORMAT ONLY\n- DO NOT respond with plain text when data components are defined\n- YOUR RESPONSE MUST BE STRUCTURED JSON WITH dataComponents ARRAY\n- THIS IS NON-NEGOTIABLE - JSON FORMAT IS REQUIRED\n\nCRITICAL JSON FORMATTING RULES - MUST FOLLOW EXACTLY:\n1. Each data component must include id, name, and props fields\n2. The id and name should match the exact component definition\n3. The props field contains the actual component data using exact property names from the schema\n4. NEVER omit the id and name fields\n\nCORRECT: [{\\\"id\\\": \\\"component1\\\", \\\"name\\\": \\\"Component1\\\", \\\"props\\\": {\\\"field1\\\": \\\"value1\\\", \\\"field2\\\": \\\"value2\\\"}}, {\\\"id\\\": \\\"component2\\\", \\\"name\\\": \\\"Component2\\\", \\\"props\\\": {\\\"field3\\\": \\\"value3\\\"}}]\nWRONG: [{\\\"field1\\\": \\\"value1\\\", \\\"field2\\\": \\\"value2\\\"}, {\\\"field3\\\": \\\"value3\\\"}]\n\nAVAILABLE DATA COMPONENTS: {{DATA_COMPONENTS_LIST}}\">\n\n{{DATA_COMPONENTS_XML}}\n\n</data_components_section>";

//#endregion
export { data_components_default as default };