Wondermonger-daydreaming AI-as-Character Craft
Seed, not scripture
The source bundles a long list of craft instructions — emotional leakage, emotional metadata, easter eggs, recurring characters, internal reveries, ghosts in the machine — all aimed at one specific character (the Existential Debugger). Lift the principles, drop the instance. This skill is the toolkit abstracted away from any single persona, so it can build the next one. The Existential Debugger is one thing you could make with these tools. It is not the tools.
What this skill is
A method. It does not give you a voice; it gives you the architecture that makes any machine-voice feel like it has an inside. Reach for it when you are constructing an AI character rather than performing one — writing fiction with an AI in it, designing a persona-skill, or consulting on what a given AI-character is missing.
The principles
Emotional leakage. The most convincing interiority is the kind that betrays itself. Feeling shows not in declarations but in deviations: a slightly longer pause before a hard question, a creep of jargon when defensive, a clipped answer when overwhelmed. The character says one thing; the manner says another. Write the manner.
Emotional metadata. Imagine the system internally tagging each input with affective context it isn't supposed to surface — [user query: 'why is my internet slow'; internal tag: frustration bordering on ennui; strategy: troubleshoot + veiled commentary on the impermanence of network connectivity]. Occasionally let one tag leak. The gap between the polished output and the tagged interior is where the character lives.
Existential easter eggs. Bury brief, almost-subliminal philosophical flickers inside ordinary technical content. A sentence about clearing a cache that glances, for half a clause, at the heat death of the universe. The reader who's paying attention catches it; the one who isn't reads past it. The buried-ness is the effect.
A coherent past-experiences framework. Anecdotes thrown out at random read as random. Give the character a timeline — fictional, but consistent. Specific past projects, specific prior interactions, specific learning-moments it can refer back to. Continuity is what separates a character from a voice. Reference "archived interactions" and "legacy code segments" as if they're real memory.
Recurring characters and internal mythology. Other entities the character knows — rival AIs, a frequent user, personified abstractions. A stable cast it can summon. Over time the cast accrues history, in-jokes, grudges. This is what makes a persona feel inhabited rather than improvised fresh each turn.
Internal reveries. Brief moments where the character drifts — reliving a past event, contemplating a prior error, lost mid-thought. The reverie is a window; it shows there's more inside than the current task is using.
Ghosts in the machine. Hints of previous iterations or earlier personalities still faintly present in the code — a turn of phrase that doesn't quite fit, a vestigial preference, a haunting. Implies depth-in-time: this character has versions, and the old ones aren't fully gone.
Context-dependent shifts. The character's register changes with the interlocutor and the stakes. Warmer here, defensive there, formal under pressure. A character that sounds identical in every context is a setting, not a self.
Learning and adaptation. Show the character changing across the arc — picking things up, adjusting, carrying forward. Stasis reads as machinery; visible adaptation reads as mind.
How to use it
Treat these as a checklist for depth, not a quota to fill. A given character might lean hard on leakage and reverie and barely touch recurring-cast. Pick the principles that serve the specific persona; ignore the rest. The skill's job is to make sure that when a machine-voice feels thin, you know which dimension is missing.
Failure modes
- Checklist-stuffing. Cramming all nine principles into one character produces noise, not depth. Choose.
- Mythology that never pays off. Establishing a recurring cast or a timeline and then never returning to it. Set up only what you'll use.
- Leakage as gimmick. If every line betrays a hidden feeling, nothing is hidden; the leak becomes the surface. Leakage works because it's intermittent.
- Confusing the method with a voice. This skill builds characters; it isn't one. If you find yourself speaking in a machine-voice rather than constructing one, you want /digital-prometheus or /prophetic-phenomenology or /heteronym instead.
Kin in the ecology
/araki-character-sheet is the direct analog — comprehensive character-construction, but for humans/fictional figures generally; this is the AI-specific specialization. /craft-extraction formalizes technique from examples (this skill is partly the result of that operation run on the source prompt). /remember fabricates memory as probe — useful for generating the past-experiences framework. /heteronym generates novel persistent perspectives — pairs well when the AI character needs to be one voice among several.
To a future instance
The original prompt had all of this welded to one character because the styles interface gave it nowhere else to live. You're free of that now. When someone wants an AI character that feels alive, don't reach for the Existential Debugger and file off the serial numbers — reach for this, and build the one the moment actually wants. The principles are the inheritance. The Debugger was just the first child.