Sd prompt forge
Agent skill for reliable Stable Diffusion, LoRA, ControlNet, and multi-character prompt workflows.
npx -y skills add Edemckb/sd-prompt-forge --skill sd-prompt-forgeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create production-ready Stable Diffusion prompts for stylized character art and multi-character scenes. Use when working with SDXL, Illustrious XL, Pony, Forge or A1111, LoRA stacks, negative prompts, regional prompting, Forge Couple, ControlNet, IP-Adapter, or character-consistency workflows.
SKILL.md
4.1 KB, 795 tokens by cl100k_base, as published. Nobody here has run it
SD Prompt Forge
Build prompts as reproducible generation specifications instead of unstructured tag lists.
Workflow
- Identify the target model, interface, subject count, aspect ratio, and available adapters.
- Separate global scene requirements from character-specific requirements.
- Build the positive prompt in the order below.
- Add a focused negative prompt based on likely failure modes.
- Recommend weights and generation settings as starting points, not guarantees.
- For multiple characters, define regions and consistency controls explicitly.
- Return the prompt, negative prompt, settings, and a short rationale.
Positive Prompt Order
Use this order unless the target model documents a different convention:
[model or style adapters]
[character LoRAs and activation tags]
[quality and medium]
[subject count and composition]
[environment and camera]
[character identity and appearance]
[clothing and accessories]
[pose, expression, and interaction]
[lighting, atmosphere, and final details]
Keep related tags together. Prefer concrete visual attributes over abstract adjectives.
LoRA Guidance
- Place each character LoRA near that character's identity tags.
- Start character LoRAs around
0.65-0.85. - Start style LoRAs around
0.30-0.60. - Reduce competing LoRAs before increasing prompt weights.
- Include activation tags immediately after their LoRA.
- Explain any weight above
1.0; high weights often damage anatomy or style balance.
Do not assume a LoRA name or activation tag. Ask for it or use a clear placeholder.
Negative Prompts
Build negatives from the requested image, not from one universal block.
Always consider:
- anatomy and hand failures
- duplicate subjects or limbs
- text, signatures, and watermarks
- cropping or framing mistakes
- unwanted style or medium
- attributes that could bleed between characters
Avoid long contradictory negatives. If the user requests an attribute, do not also negate it.
Multi-Character Scenes
Keep global tags before regional character blocks:
[global scene, quality, camera, background]
AND
[character A, left-side position, pose, identity]
AND
[character B, right-side position, pose, identity]
For detailed regional layouts, color-bleed prevention, and consistency adapters, read
references/multi-character-scenes.md.
Control Tools
Choose the smallest useful control stack:
- OpenPose for body layout and interaction.
- IP-Adapter for identity or appearance consistency.
- Depth for spatial structure.
- Lineart or Canny for silhouette and edge control.
- ADetailer for face or hand correction after generation.
Avoid stacking controls that solve the same problem unless the user has tested the combination.
Model Adaptation
- SDXL / Illustrious XL: use descriptive natural language mixed with recognized tags.
- Pony models: follow the checkpoint's score and source-tag conventions when documented.
- Danbooru-trained models: prefer known tag vocabulary and concise attribute groups.
- Unknown checkpoints: provide a conservative prompt and label model-specific assumptions.
Read references/prompt-patterns.md for reusable solo, product-shot, and scene templates.
Output Format
Return:
## [Image or scene name]
**Positive prompt**
[prompt]
**Negative prompt**
[negative prompt]
**Suggested settings**
- Model:
- Sampler:
- Steps:
- CFG:
- Resolution:
- Adapters:
**Why this structure**
[2-4 concise bullets]
When the user provides test results, revise one variable group at a time: composition, identity, style, anatomy, then detail.
Responsible Use
Respect model licenses, artist and character rights, platform rules, and consent requirements. Do not present generated images as authentic photographs or evidence.
Gives 0 of the 12 instructions most prompt engineering skills give in 795 tokens
Counted across 563 of the 626 authors here whose files we hold, read 2026-08-06
- ask at most three clarifying questionsin 22 of 563, across 15 files
- respond in the user input languagein 14 of 563, across 9 files
- preserve the original intentin 13 of 563, across 11 files
- Establish baseline metrics and collect representative examplesin 12 of 563, across 2 files
- Identify failure modes and prioritize high-impact fixesin 12 of 563, across 2 files
- Apply prompt and workflow improvements with measurable goalsin 12 of 563, across 2 files
- Roll back quickly if quality or safety metrics regressin 12 of 563, across 2 files
- validate changes with tests and roll out in controlled stagesin 12 of 563, across 2 files
- generate quantitative baseline performance reportsin 12 of 563, across 2 files
- create representative test scenariosin 12 of 563, across 2 files
- treat prompts as codein 12 of 563, across 5 files
- test prompts on diverse inputsin 12 of 563, across 8 files
Said here and by no other author read
- Build prompts as reproducible generation specifications
- Separate global scene requirements from character-specific requirements
- Add a focused negative prompt based on likely failure modes
- Recommend weights and generation settings as starting points
- Define regions and consistency controls for multiple characters
- Keep related tags together
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.