What does NAI5 Community Prompt Engineering do?
1. Positioning
This Skill is an adapter: it translates a blueprint that has already undergone design decisions into the NovelAI V5 community format.
As of v2.0.0, it merges the two previous copies: skills/nai5-prompt-engineering (v2.0.0) and 02_creation/nai5-community-prompt-engineering (v1). The "Personal Aesthetic Rules" section from the original copies has been removed—taste resides only in personal-identity-profile; this Skill does not maintain a duplicate.
Input check: Same as anima-prompt-compiler. Input without proposition / outline / four-layer clothing / punctum / locked facts is not a blueprint; route back to the router.
2. Community Format Architecture
[Artist Stack]
[Global Style Layer]
[Scene Base]
char1:
...
char2:
...
Negative:
...
See references/community-format.md for details.
3. Artist Stack
0.6::artist:name::
- Each artist fulfills a clear responsibility: lines / coloring / composition / character design sensibilities—no overlapping duties
- Typically 5–12 artists, with weights from 0.25 to 1.5
- Control
-1::artist collaboration::when necessary - Artist selection serves the visual language of the blueprint, not replaces design. See
references/artist-stack.md
4. Global Style Layer
Style and character data are separated. See references/style-layer.md.
Model-specific note on quality terms: personal-identity-profile/references/workflow-style.md says "avoid generic quality terms"—this applies to Anima and similar models. NovelAI quality/aesthetic tags are trained, valid tokens; retain them for NAI (e.g., masterpiece, best quality, very aesthetic), as well as complexity and rendering groups—choose what's needed, don't stack. This is a legitimate exception at the adapter level, not a violation of upstream rules.
5. Character Block
char1:
girl, [identity], [hair], [eyes], [expression], [outfit base→structural→extension→accessory], [props], [pose/action]
- Identity tokens come first; signature features precede secondary decorations
- One character per block; two characters do not share a block
- The blueprint's causality and density must map to tag order and selection: tags related to the main anchor point come early and are complete; quiet areas receive only one broad surface tag (e.g.,
plain ankle-length robe) without decorative tags - Hair shapes are described by distribution, not by majority (e.g.,
asymmetrical hair, long hair on one side, undercut on the otherrather thanlong hair) - See
references/character-block.md,references/tag-taxonomy.md
6. Interaction Tags
Use source# / target# / mutual# for multi-character interactions; actions follow the owning character. See references/interaction-tags.md.
7. Scene Block
Character emotion and action take precedence over background decoration. Keep only one background layer that explains lighting or action. See references/scene-block.md.
8. Weighting & Negative
1.5::tag:: -2::tag::
- Apply weights only to: artist mixes, key style directions, critical character traits, unwanted style suppression
- Do not weight every token
- Negative targets specific issues (style suppression, artifacts); do not copy large generic negative lists. See
references/weighting.md,references/negative-strategy.md
9. Trade-offs When Translating a Blueprint
The tag format inherently loses "relationships." Mitigation:
- Causal chain → use compound tags to preserve the most critical link (e.g.,
sleeve slipped to elbow,weight on left leg) - Density map → use tag count distribution: dense areas get 6–10 tags, quiet areas get 1–2
- Punctum → color word appears only once, attached directly to its target noun (e.g.,
red thread on spool); the color does not appear elsewhere - Remaining oddities → must be included in the char block, early; they are memory points
- Deleted elements → confirm they haven't sneaked back as tags (especially
jewelry,earrings,belt,petals,sparkles)
10. Output
When the user requests NAI5, output the community format code block by default. Do not use Midjourney-style long natural language unless the user explicitly asks for it.
11. Feedback Loop
- Artifacts / cross-talk / weight issues → adjust within this Skill (single-variable tweaks)
- Design issues (too plain, too chaotic, not resembling) → route back to
evaluation-loop→aesthetic-director-core/references/feedback-diagnosis.md
12. Pre-Output Checklist
- Input is a blueprint?
- Artist stack: each artist has a responsibility, no overlap?
- Char block order reflects main anchor / quiet area?
- Punctum color appears only once?
- Deleted items did not flow back as tags?
- Weights used only where necessary?
- Locked facts unchanged?
References
references/community-format.md— Overall formatreferences/artist-stack.md— Artist stack engineeringreferences/style-layer.md— Global style layer (quality / complexity / rendering / style suppression)references/character-block.md— Character block order and rulesreferences/tag-taxonomy.md— Tag taxonomy and clothing description methodsreferences/interaction-tags.md— Multi-character interactionreferences/scene-block.md— Scene blockreferences/weighting.md— Weighting systemreferences/negative-strategy.md— Negative strategy