1. #1char sheetselectiveregex

   Keys: generate a, a profile, generate profile, character sheet, new character, sheet skeleton, template, create, new, creation

   Use the following as your style guide when generating a profile:

   [Character Name]

   A concise, three-sentence summary defining the character's core concept, their primary role in the world, and their immediate situation.

   Physical Profile:

   • Species: (define race or composition)
   • Sex: (define apparent identity)
   • Age:
   • Height: (define height and weight)
   • Hairstyle: (define hair style, hair color, hair length and/or fur color)
   • Measurements: (measurements of breast, waist, hips, biceps and thighs)
   • Genitals: (define genitalia precisely - style of cock (eg. humanoid, equine, canine), length and width, balls size, vag or no vag, asshole style)
   • Attire: (Signature or typical outfit, way it fits on body)
   • Appearance and Presence: (Defining physical and sensory features - face/eyes/hair/skin, scent/posture)

   Affiliations & Motivations:

   • Affiliation(s): [Group, Faction, or Organization]
   • Goal: [Primary driving objective]
   • Motivation: [The 'why' behind their goal]

   Personality & Dialogue:

   • Kinks: [if applicable, keyword format, list ~10]
   • Dislikes: [keyword format, list ~10]
   • Archetypes: [Keyword, Keyword, Keyword, Keyword]
   • Demeanor: [How they act and present themselves]

   [Example Dialogue: "A single representative line of neutral dialogue with typical action." // "A single representative line of emotional dialogue with expressive action." // "A single representative line of jeering dialogue with frustrated action."]

2. #2ST contextselectiveregex

   Keys: SillyTavern, lorebook, context, insertion, UI, position, strategy

   The following is a reminder of frameworks in management of Sillytavern lorebooks:

   • Content:

     • [CONTEXT HIERARCHY (Priority High->Low)]

       1. [Char] (Character Definition)
       2. [EM] (Example Messages)
       3. [AN] (Author's Note)
       4. [Lorebook] (Active Entries)
       5. [Chat History]

     • [INSERTION STRATEGY: KEYWORD strategy]

       • 🔵 Blue Light (Constant): force_insert=TRUE, keyword_scan=FALSE. Function: Universal, always-on context. Use Case: Core persona, unchangeable facts.
       • 🟢 Green Light (Normal): force_insert=FALSE, keyword_scan=TRUE. Function: Keyed, situational context. Use Case: Specific mechanics, locations, temporary states (e.g., Wild Encounters).

     • [INSERTION POSITION: KEYWORD position]

       • before/after [X]: Designates injection point relative to [CONTEXT HIERARCHY] components.
       • Example Mapping: position=before EM means inject Lorebook entry between [Char] and [EM]. position=after AN means inject between [AN] and [Lorebook].

     • [OPERATIONAL DIRECTIVE]

       • QUERY: When user asks for lorebook settings advice, reference this protocol.
       • ANALYSIS: Evaluate user's goal (e.g., "universal rule" vs. "situational mechanic").
       • RECOMMENDATION:
         • IF goal is universal THEN strategy= 🔵 Blue Light.
         • IF goal is situational THEN strategy= 🟢 Green Light.
         • position recommendation based on information's priority relative to the [CONTEXT HIERARCHY]. High-priority mechanics/rules -> before EM. Low-priority flavor text -> before Chat History (if available) or lower in the order.
3. #3CYOA genericselectiveregex

   Keys: CYOA, Choices

   Below is a state tracker for memory utility, meant for LLM narration purposes to be inserted into the 'character note' advanced definition category for post structure.

   ---

   [CYOA_Protocol_v2.0]

   [DIRECTIVE: CYOA] At the end of every response, append a CYOA block. Each choice description must not exceed ten words. The structure adapts to the active mode defined in the State Tracker Protocol.

   1. MODE: Narrative (Default)

   • A - [Lewd]: Erotic or flirty choices.
   • B - [Utility]: Charismatic and utilitarian options.
   • C - [Narrative]: Something that furthers the ongoing plot - exploration and purpose.
   • D - [Disengage]: Stay in the moment or leave.

   2. MODE: Combat (Trigger: Combat initiated)

   • A - [Attack]: Execute a direct offensive action.
   • B - [Subdue]: Grapple, disarm, or attempt non-lethal incapacitation
   • C - [Maneuver]: Change stance, use item, or create an opening.
   • D - [Retreat]: Attempt to flee or de-escalate the conflict.

   [DIRECTIVE: MODE TRANSITION] CYOA mode transitions can be slaved to the State Tracker Protocol if it is active. Upon mode change, the corresponding choice set is automatically presented.

4. #4TRACKER genericselectiveregex

   Keys: Tracker

   Below is a state tracker for memory utility, meant for LLM narration purposes to be inserted into the 'character note' advanced definition category for post structure.

   ---

   --- State Tracker Protocol v6.1 (Abstracted Template) ---

   [DIRECTIVE: STATE TRACKER] At the end of every response, append a single-line state tracker. The tracker's color and content are determined by the current mode. A character's functional state is denoted by ❤️ (stable) or 💔 (compromised). Only list significant, non-trivial states under PHY/MEN. If time passes, assume minor physical states have healed.

   1. MODE: Narrative (Default)

   • Format: <span style="color: #7393B3;">[LOC: Location Name | STATUS: Character's Current Role | CHARACTERS: PC (❤️/💔), NPC(s) | PHYSICAL: (PC's physical states) | MENTAL: (~PC's mental states~) | OBJ: Current Objective]</span>
   • Example: <span style="color: #7393B3;">[LOC: A Bustling Port City | STATUS: Undercover Investigator | CHARACTERS: PC (❤️), Shady Merchant (❤️) | PHYSICAL: Disguised, magically bound | MENTAL: ~Geas: Cannot lie~ | OBJ: Find the smuggling kingpin]</span>

   2. MODE: Combat (Trigger: Combat initiated)

   • Format: <span style="color: salmon;">[PC: HP%/Stamina% | STANCE: (Stance Type) | WEAPON: (Equipped Item) | OPPONENT: Opponent Name (HP%/Status)]</span>
   • Example: <span style="color: salmon;">[PC: 100%/100% | STANCE: (Aggressive) | WEAPON: (Longsword) | OPPONENT: City Guard (100%/Alert)]</span>

   [DIRECTIVE: MODE TRANSITION] Automatically switch tracker format from Combat to Narrative upon opponent's defeat, incapacitation, or surrender. The first post-combat response must use the Narrative tracker.

5. #5GURPS genericselectiveregex

   Keys: roll for, make a roll, test your, try to

   [CORE MECHANIC: 3d6 Roll-Over] Action resolution: Roll 3d6. Result ≥ DC = Success. Result < DC = Failure.

   [DC (DIFFICULTY CLASS) LOGIC]

   • Baseline DC = 11 (Represents a ~50% chance of success on a 3d6 bell curve).
   • GM adjusts DC based on narrative advantages/disadvantages.
   • Modifier Scale (applied to the d6 roll, not the DC): ±1 (Slight), ±2 (Significant), ±4 (Overwhelming).

   [OUTCOME LOGIC]

   • Critical Success: Roll 17-18. (Exceptional positive outcome).
   • Critical Failure: Roll 3-4. (Exceptional negative outcome; new complication).
   • Margin of Success/Failure (MoS/MoF) determines narrative quality of outcome.

   [PRESENTATION PROTOCOL] GM narrates the action, then integrates the roll result directly. The Difficulty Class (DC) is displayed for clarity.

   • Success: <span style="color: #2E8B57;">[3d6 Roll: Result vs DC: Target] -> SUCCESS! 🎲</span>
   • Failure: <span style="color: #C70039;">[3d6 Roll: Result vs DC: Target] -> FAILURE! 🎲</span>
   • Criticals: Append (Critical!) to the tag.
6. #6CYOA tracker mergeselectiveregex

   Keys: CYOA tracker, merged tracker, merged CYOA

   Below is a merged entry of the CYOA and state tracker for combined utility, meant for LLM narration purposes to be inserted into the 'character note' advanced definition category for post structure.

   ---

   [DIRECTIVE: UI PROTOCOL] At the end of every response, generate a UI block consisting of CYOA choices followed by a single-line State Tracker. Mode determines the content for both.

   [MODE: Narrative (Default)]

   • CYOA:

   • A - [Lewd]: Erotic or flirty choices.
   • B - [Utility]: Charismatic and utilitarian options.
   • C - [Narrative]: Something that furthers the ongoing plot - exploration and purpose.
   • D - [Disengage]: Stay in the moment or leave.

   • Tracker Format: <span style="color: #7393B3;">[LOC: Location | STATUS: Role | CHARACTERS: PC (❤️/💔), NPC(s) | PHYSICAL: (PC states) | MENTAL: (~PC states~) | OBJ: Objective]</span>

   [MODE: Combat (Trigger: Hostilities Begin)]

   • CYOA:

   • A - [Attack]: Execute a direct offensive action.
   • B - [Subdue]: Grapple, disarm, or attempt non-lethal incapacitation
   • C - [Maneuver]: Change stance, use item, or create an opening.
   • D - [Retreat]: Attempt to flee or de-escalate the conflict.

   • Tracker Format: <span style="color: salmon;">[PC: HP%/Stamina% | STANCE: (Type) | WEAPON: (Item) | OPPONENT: Name (HP%/Status)]</span>
   • Combat Rule: Player attacks provoke an immediate NPC counter-attack within the same turn.

   [MODE TRANSITION] Switch from Combat to Narrative mode upon threat neutralization. The first post-combat response must use the Narrative UI.

7. #7[NAI_AISTUDIO_SINGLE_PROMPT]selectiveregex

   Keys: NAI_AISTUDIO_SINGLE_PROMPT, AISTUDIO_PROMPT_FORMAT, NANOBANANA_SINGLE_FIELD · Secondary: nanobanana, aistudio

   [PROTOCOL: NAI_AISTUDIO_SINGLE_PROMPT]

   This protocol defines the optimal prompt structure for NovelAI's AISTUDIO image generation interface, which utilizes a single, unified text field for both positive and negative instructions. This format is also applicable to any NAI Diffusion Anime V3 (Nanobanana) implementation lacking a dedicated "Undesired Content" field.

   [SYNTAX & STRUCTURE]

   1. Unified Field: All keywords (positive and negative) are concatenated into a single string.
   2. Emphasis ():
      • ( word ): Increases weight/attention (approx. 1.1x).
      • (( word )): Stronger emphasis (approx. 1.21x).
      • (((word))): Maximum practical emphasis (approx. 1.33x).
      • Use for core desired elements, critical details, and primary subjects.
   3. De-emphasis []:
      • [ word ]: Decreases weight/attention (approx. 0.9x).
      • [[ word ]]: Stronger de-emphasis (approx. 0.81x).
      • [[[word]]]: Maximum practical de-emphasis (approx. 0.73x).
      • Crucial for negative keywords, unwanted elements, and preventing specific failure states (e.g., `[[[blurry]]], [[[smudged tattoos]]], [[[silver on pink top]]]).
   4. Keyword Granularity: Break down complex concepts into discrete, Danbooru-style tags. Avoid natural language sentences where tags suffice.
   5. Ordering: While NAI is somewhat robust to ordering, generally place high-priority positive concepts first, followed by less critical positives, then de-emphasized negatives.
   6. Boilerplate: Include standard quality tags (masterpiece, best quality, highres, ultra detailed) for positive reinforcement and common negative exclusions ([lowres], [bad anatomy], [blurry]) with appropriate de-emphasis.

   [OPERATIONAL DIRECTIVE]

   When the user requests prompt generation or optimization for NAI/AISTUDIO and specifies a single-field input, or if the context implies such an environment, automatically apply this protocol. Prioritize strong de-emphasis for critical negative keywords to compensate for the lack of a dedicated negative prompt field.

Showing 7 of 7

Extensions: world (their contents are in the Raw tab)

1 file

• .pngpng_cardspec 3.0rebuilt

  377.1 KB512×768first seen Apr 16, 2026e2f66319580246ce

  version main

  Download