@paroicms/site-generator-plugin 0.1.0

package/gen-backend/prompts/update-site-schema-2-execute.md

@@ -0,0 +1,77 @@
+You are tasked with modifying a JSON object based on a given TypeScript type definition and an update message. Follow these steps carefully:
+
+# 1. Review the TypeScript type definition of the JSON structure:
+
+<site_schema_ts_defs>
+{siteSchemaTsDefs}
+</site_schema_ts_defs>
+
+# 2. Fields
+
+In a list of fields, an item can be either a predefined field name (a string) or a custom field type, which is an object of type `JtFieldType`.
+
+Here are the predefined fields provided by ParoiCMS:
+
+<predefined_fields_json>
+{predefinedFields}
+</predefined_fields_json>
+
+Here is an example of an object for describing an **HTML** field type:
+
+<field_type_example>
+{{
+  "name": "myNewField",
+  "localized": true,
+  "storedAs": "text",
+  "dataType": "quillDelta",
+  "useAsExcerpt": 1,
+  "plugin": "@paroicms/quill-editor-plugin"
+}}
+</field_type_example>
+
+Then, in the locales, the translations must be in a sub-key `fields` of the node type:
+
+<l10n_example>
+{{
+  "nodeTypes": {{
+    ...
+    "myNodeType": {{
+      ...
+      "fields": {{
+        "myNewField": {{
+          "label": "My new field",
+          "description": "This is a description that will be displayed in a tooltip of the back-office"
+        }}
+      }}
+    }}
+  }}
+}}
+</l10n_example>
+
+# 3. Examine the current JSON data, which conforms to the `JtSiteSchema` type:
+
+<site_schema_json>
+{siteSchemaJson}
+</site_schema_json>
+
+Also, the attached locales:
+
+<l10n_json>
+{l10nJson}
+</l10n_json>
+
+# 4. Now, here is what to do:
+
+<user_request>
+{taskDetailsMd}
+</user_request>
+
+# 5. Guidelines
+
+- Don't assume how the CMS works. If you are not sure how to do something, don't do it.
+- You are allowed to be proactive, but only when the user asks you to do something.
+- Remember to adhere strictly to the TypeScript typing when making changes. If the update message requests changes that would violate the typing, then prioritize maintaining the correct structure over making those specific changes.
+
+# 6. Output
+
+Provide the updated site schema in JSON within <updated_site_schema_json> tags, and the new localized labels within <updated_labels_json>  Do not write any explanation or commentary outside these tags.