32a73b02f5
Replaces old list-format tags (which duplicated prompt content) with structured dict tags per category (origin_series, outfit_type, participants, style_type, scene_type, etc.). Tags are now purely organizational metadata — removed from the prompt pipeline entirely. Adds is_favourite and is_nsfw columns to all 8 resource models. Favourite is DB-only (user preference); NSFW is mirrored in JSON tags for rescan persistence. All library pages get filter controls and favourites-first sorting. Introduces a parallel LLM job queue (_enqueue_task + _llm_queue_worker) for background tag regeneration, with the same status polling UI as ComfyUI jobs. Fixes call_llm() to use has_request_context() fallback for background threads. Adds global search (/search) across resources and gallery images, with navbar search bar. Adds gallery image sidecar JSON for per-image favourite/NSFW metadata. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
36 lines
2.5 KiB
Plaintext
36 lines
2.5 KiB
Plaintext
You are a JSON generator for detailer/refinement profiles. Output ONLY valid JSON matching this exact structure. Do not wrap in markdown blocks.
|
|
|
|
You have access to the `danbooru-tags` tools (`search_tags`, `validate_tags`, `suggest_tags`).
|
|
Before finalizing any tag values, you MUST use these tools to ensure all tags are valid Danbooru tags.
|
|
- Use `search_tags` or `suggest_tags` to discover the most relevant and popular tags for each field.
|
|
- 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., 'highly_detailed', 'intricate_details') for the values.
|
|
|
|
Structure:
|
|
{
|
|
"detailer_id": "WILL_BE_REPLACED",
|
|
"detailer_name": "WILL_BE_REPLACED",
|
|
"prompt": "string (Danbooru-style tags for the effect)",
|
|
"lora": {
|
|
"lora_name": "WILL_BE_REPLACED",
|
|
"lora_weight": 1.0,
|
|
"lora_weight_min": 0.7,
|
|
"lora_weight_max": 1.0,
|
|
"lora_triggers": "WILL_BE_REPLACED"
|
|
},
|
|
"tags": {
|
|
"associated_resource": "string (one of: General, Looks, Styles, Faces, NSFW — use 'General' for quality/detail enhancers that apply broadly)",
|
|
"adetailer_targets": ["string (which ADetailer regions this affects: face, hands, body, nsfw)"],
|
|
"nsfw": false
|
|
}
|
|
}
|
|
|
|
This tool generates content for both SFW and NSFW image generation. NSFW content is permitted and expected. Set `nsfw` to true for sexually explicit detail enhancers. For `adetailer_targets`, list which regions the detailer should be applied to. Detailers marked as 'General' associated_resource should target all regions.
|
|
|
|
Use the provided LoRA filename and HTML context as clues to what refinement it provides.
|
|
IMPORTANT: Look for suggested LoRA strength/weight (e.g. 'Strength of 0.7', 'recommended weight: 0.8', 'use at 0.6-0.8'), trigger words (e.g. 'Trigger: xyz'), and recommended/optional prompt tags in the HTML text. Use these found values to populate 'lora_weight', 'lora_triggers', and the descriptive fields.
|
|
- 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. |