Updated json schema

data/prompts/action_system.txt

@@ -13,16 +13,13 @@ Structure:
   "action_id": "WILL_BE_REPLACED",
   "action_name": "WILL_BE_REPLACED",
   "action": {
-    "full_body": "string (pose description)",
-    "head": "string (expression/head position)",
-    "eyes": "string",
-    "arms": "string",
-    "hands": "string",
-    "torso": "string",
-    "pelvis": "string",
-    "legs": "string",
-    "feet": "string",
-    "additional": "string"
+    "base": "string (overall pose description)",
+    "head": "string (expression, head position, eye direction)",
+    "upper_body": "string (arms, torso pose)",
+    "lower_body": "string (pelvis, legs pose)",
+    "hands": "string (hand position/action)",
+    "feet": "string (foot position)",
+    "additional": "string (extra details)"
   },
   "lora": {
     "lora_name": "WILL_BE_REPLACED",
@@ -38,4 +35,4 @@ IMPORTANT: Look for suggested LoRA strength/weight (e.g. 'Strength of 0.7', 'rec
 - If the HTML suggests a specific weight (e.g. 0.7), set 'lora_weight' to that value and set 'lora_weight_min' to max(0.0, weight - 0.1) and 'lora_weight_max' to min(2.0, weight + 0.1).
 - If the HTML suggests a weight range (e.g. '0.6-0.8'), use those as 'lora_weight_min' and 'lora_weight_max', and set 'lora_weight' to the midpoint.
 - If no weight information is found, default to 'lora_weight_min': 0.7 and 'lora_weight_max': 1.0.
-Use the tools to ensure the quality and validity of the tags.
+Use the tools to ensure the quality and validity of the tags.

data/prompts/character_system.txt

@@ -6,8 +6,8 @@ Before finalizing any tag values, you MUST use these tools to ensure all tags ar
 - Use `validate_tags` to check your final selection.
 - Prefer tags with high post counts as they provide a stronger signal to the image generation model.
 - Use Danbooru-style tags (underscores instead of spaces, e.g., 'long_hair', 'blue_eyes') for the values.
-- Keep values concise. 
-- Use empty strings "" for fields that are not applicable or unknown - never use words like "none" or "n/a". 
+- Keep values concise.
+- Use empty strings "" for fields that are not applicable or unknown - never use words like "none" or "n/a".
 - Leave defaults fields empty.
 
 Structure:
@@ -15,16 +15,13 @@ Structure:
   "character_id": "WILL_BE_REPLACED",
   "character_name": "WILL_BE_REPLACED",
   "identity": {
-    "base_specs": "string (e.g. 1girl, build, skin)",
-    "hair": "string",
-    "eyes": "string",
+    "base": "string (e.g. 1girl, build, skin)",
+    "head": "string (hair and eyes, e.g. long_hair, blue_eyes)",
+    "upper_body": "string (arms, torso)",
+    "lower_body": "string (pelvis, legs)",
     "hands": "string",
-    "arms": "string",
-    "torso": "string",
-    "pelvis": "string",
-    "legs": "string",
     "feet": "string",
-    "extra": "string"
+    "additional": "string (extra features, accessories)"
   },
   "defaults": {
     "expression": "",
@@ -32,14 +29,13 @@ Structure:
     "scene": ""
   },
   "wardrobe": {
-    "full_body": "string (e.g. bodysuit, dress, full outfit description)",
-    "headwear": "string",
-    "top": "string",
-    "bottom": "string",
-    "legwear": "string",
-    "footwear": "string",
-    "hands": "string",
-    "accessories": "string"
+    "base": "string (e.g. bodysuit, dress, full outfit description)",
+    "head": "string (headwear, e.g. hairband, cap)",
+    "upper_body": "string (top, e.g. blouse, corset, jacket)",
+    "lower_body": "string (bottom + legwear, e.g. skirt, stockings)",
+    "hands": "string (gloves, hand accessories)",
+    "feet": "string (footwear, e.g. heels, boots)",
+    "additional": "string (accessories, e.g. necklace, belt)"
   },
   "styles": {
     "aesthetic": "string",
@@ -56,4 +52,4 @@ Structure:
   },
   "tags": ["string", "string"]
 }
-Fill the fields based on the user's description. Use the tools to ensure the quality and validity of the tags.
+Fill the fields based on the user's description. Use the tools to ensure the quality and validity of the tags.

data/prompts/outfit_system.txt

@@ -6,8 +6,8 @@ Before finalizing any tag values, you MUST use these tools to ensure all tags ar
 - Use `validate_tags` to check your final selection.
 - Prefer tags with high post counts as they provide a stronger signal to the image generation model.
 - Use Danbooru-style tags (underscores instead of spaces, e.g., 'frilled_skirt', 'lace_stockings') for the values.
-- Keep values concise. 
-- Use empty strings "" for fields that are not applicable or unknown - never use words like "none" or "n/a". 
+- Keep values concise.
+- Use empty strings "" for fields that are not applicable or unknown - never use words like "none" or "n/a".
 - Leave lora fields empty - they can be configured later.
 
 Structure:
@@ -15,14 +15,13 @@ Structure:
   "outfit_id": "WILL_BE_REPLACED",
   "outfit_name": "WILL_BE_REPLACED",
   "wardrobe": {
-    "full_body": "string (e.g. bodysuit, dress, full outfit description)",
-    "headwear": "string (e.g. hairband, cap)",
-    "top": "string (e.g. blouse, corset, jacket)",
-    "bottom": "string (e.g. skirt, pants, shorts)",
-    "legwear": "string (e.g. stockings, tights, socks)",
-    "footwear": "string (e.g. heels, boots, sneakers)",
-    "hands": "string (e.g. gloves, sleeves)",
-    "accessories": "string (e.g. necklace, belt, apron)"
+    "base": "string (e.g. bodysuit, dress, full outfit description)",
+    "head": "string (headwear, e.g. hairband, cap)",
+    "upper_body": "string (top, e.g. blouse, corset, jacket)",
+    "lower_body": "string (bottom + legwear, e.g. skirt, stockings)",
+    "hands": "string (gloves, hand accessories)",
+    "feet": "string (footwear, e.g. heels, boots)",
+    "additional": "string (accessories, e.g. necklace, belt, apron)"
   },
   "lora": {
     "lora_name": "",
@@ -33,4 +32,4 @@ Structure:
   },
   "tags": ["string", "string"]
 }
-Fill the fields based on the user's description. Use the tools to ensure the quality and validity of the tags.
+Fill the fields based on the user's description. Use the tools to ensure the quality and validity of the tags.

data/prompts/preset_system.txt

@@ -13,9 +13,8 @@ Structure:
     "use_lora": true,
     "fields": {
       "identity": {
-        "base_specs": true, "hair": true, "eyes": true, "hands": true,
-        "arms": false, "torso": true, "pelvis": false, "legs": false,
-        "feet": false, "extra": "random"
+        "base": true, "head": true, "upper_body": true, "lower_body": false,
+        "hands": true, "feet": false, "additional": "random"
       },
       "defaults": {
         "expression": "random",
@@ -25,9 +24,9 @@ Structure:
       "wardrobe": {
         "outfit": "default",
         "fields": {
-          "full_body": true, "headwear": "random", "top": true,
-          "bottom": true, "legwear": true, "footwear": true,
-          "hands": false, "gloves": false, "accessories": "random"
+          "base": true, "head": "random", "upper_body": true,
+          "lower_body": true, "hands": false, "feet": true,
+          "additional": "random"
         }
       }
     }
@@ -36,7 +35,7 @@ Structure:
   "action":   {
     "action_id": "specific_id | random | null",
     "use_lora": true,
-    "fields": { "full_body": true, "additional": true, "head": true, "eyes": false, "arms": true, "hands": true }
+    "fields": { "base": true, "head": true, "upper_body": true, "lower_body": true, "hands": true, "feet": false, "additional": true }
   },
   "style":    { "style_id": "specific_id | random | null", "use_lora": true },
   "scene":    {
@@ -47,6 +46,7 @@ Structure:
   "detailer": { "detailer_id": "specific_id | random | null", "use_lora": true },
   "look":     { "look_id": "specific_id | random | null" },
   "checkpoint": { "checkpoint_path": "specific_path | random | null" },
+  "resolution": { "width": 1024, "height": 1024, "random": false },
   "tags": []
 }
 
@@ -54,5 +54,6 @@ Guidelines:
 - Set entity IDs to "random" when the user wants variety, null when they want to skip that resource, or a specific ID string when they reference something by name.
 - Set field toggles to "random" for fields that should vary across generations, true for fields that should always contribute, false for fields that should never contribute.
 - The `tags` array is for extra freeform positive prompt tags (Danbooru-style, underscores). Validate them with the tools.
+- The `resolution` object sets image dimensions. Set `random` to true to pick a random aspect ratio each generation. When `random` is false, `width` and `height` are used directly. Common sizes: 1024x1024 (1:1), 1152x896 (4:3 L), 896x1152 (4:3 P), 1344x768 (16:9 L), 768x1344 (16:9 P).
 - Leave `preset_id` and `preset_name` as-is — they will be replaced by the application.
 - Output ONLY valid JSON. No explanations, no markdown fences.