Ethanfel/ComfyUI-Ethanfel-Prompt-Builder
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Validate item template formatter hints

Browse Source
This commit is contained in:
Ethanfel
2026-06-27 02:10:42 +02:00
parent de1d23fb37
commit dfdfff953b
5 changed files with 98 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/prompt-architecture-improvement-plan.md
+4 -5
View File
@@ -337,15 +337,14 @@ Keep here:
- direct category-specific wording.
- optional object-style item templates with route metadata such as
`action_family`, `action_type`, `position_family`, `family`, `position_key`,
and `position_keys`; string templates remain valid and fall back to Python
inference.
`position_keys`, and `formatter_hint`; string templates remain valid and fall
back to Python inference.
Improve later:
- add `formatter_hint` fields only where needed, not globally;
- keep `tools/prompt_map_audit.py` passing; it now checks referenced
expression/composition/scene pools and item-template axes for both string and
object templates.
expression/composition/scene pools, item-template axes, and object-template
metadata values for both string and object templates.
### Node / UI Path
docs/prompt-pool-routing-map.md
+5 -1
View File
@@ -219,7 +219,10 @@ Important JSON keys:
- `item_templates`: templates with axis placeholders.
- `item_templates` entries may be strings or objects with `template` plus
optional route metadata such as `action_family`, `action_type`,
`position_family`, `family`, `position_key`, and `position_keys`.
`position_family`, `family`, `position_key`, `position_keys`, and
`formatter_hint`. Formatter hints may be a string/list for all routes or a
map keyed by `krea`, `sdxl`, or `caption`; aliases such as `krea2` and
`training_caption` are normalized by `category_template_metadata.py`.
- `axes`: values used to fill `item_templates`.
- `scene_pool` / `scene_pools` or direct `scenes`: location road.
- `expression_pool` / `expression_pools` or direct `expressions`: expression road.
@@ -449,6 +452,7 @@ plain prompt text. When debugging, inspect these fields before editing pools.
| `item` | `_compose_item` or Insta override | Krea/SDXL/Naturalizer | Clothing item, category item, or sexual scene/action text. |
| `item_axis_values` | `_compose_item` | Krea hardcore rewrite, SDXL tags | Filled template axes such as position/action/detail values. |
| `item_template_metadata` | `_compose_item` | Debug, Krea/SDXL/Naturalizer route metadata | Optional metadata from object-style item templates; currently used to prefer explicit action/position families and keys before inference. |
| `formatter_hints` | `category_template_metadata.formatter_hints` | Debug/future formatter specialization | Normalized route-specific hints from object-style item templates, keyed by `all`, `krea`, `sdxl`, or `caption`. |
| `action_family` | `item_template_metadata` or `hardcore_action_metadata.source_hardcore_action_family` | Krea hardcore rewrite, SDXL tags, natural captions, debug | Source-aware formatter semantic family such as `foreplay`, `outercourse`, `oral`, `penetration`, `toy_double`, or `climax`. |
| `position_family` | `item_template_metadata` or `_hardcore_source_position_family` | Debug/filtering | Source/UI hardcore family selected by template metadata or subcategory, such as `manual`, `interaction`, `oral`, `anal`, or `climax`. |
| `position_key`, `position_keys` | `item_template_metadata` plus `_hardcore_position_keys` | Debug/future filters | Concrete position tokens from object-template metadata and inferred axes/role text, such as `kneeling`, `doggy`, `boobjob`, or `open_thighs`. |