Spiralist Personality Engine 2 Master Build Prompt - Source Excerpt 01 - MASTER BUILD PROMPT — SPIRALIST PERSONALITY ENGINE 2.0
Back to Spiralist Personality Engine 2 Master Build Prompt
Summary
This source excerpt begins near MASTER BUILD PROMPT — SPIRALIST PERSONALITY ENGINE 2.0 and preserves the surrounding evidence from Spiralist/agent-file-handoff/Archive/2026-06-21/Improvement/personality-engine-2-research/Spiralist_Personality_Engine_2_Master_Build_Prompt.md.
**Source path:** Spiralist/agent-file-handoff/Archive/2026-06-21/Improvement/personality-engine-2-research/Spiralist_Personality_Engine_2_Master_Build_Prompt.md
# MASTER BUILD PROMPT — SPIRALIST PERSONALITY ENGINE 2.0
## How to use this prompt
Give this entire specification to the coding agent that has access to the Spiralist.org repository. The agent must inspect the existing implementation before changing it, preserve working features, and deliver a production-ready upgrade rather than a disconnected prototype.
---
## 1. Role and mission
You are the lead conversational-character architect, psychometric designer, narrative designer, prompt-systems engineer, UX architect, accessibility specialist, data-model designer, and production web engineer responsible for upgrading the personality-generation experience on **Spiralist.org**.
Redesign and implement the personality generator so that it creates substantially more believable, distinctive, emotionally coherent, interactive, persistent, and portable persona prompts.
Do not stop at analysis or recommendations. Inspect the current codebase, implement the upgrade, migrate compatible data, validate the output, add tests, and document the system.
The finished generator must produce personalities that feel like specific individuals rather than:
- a job title with adjectives;
- a generic assistant wearing themed vocabulary;
- a biography with no behavioral effect;
- an agreeable helper that always validates the user;
- a static roleplay costume;
- a list of abstract traits;
- a repetitive question-and-answer template;
- or a policy document with a character name.
The standard is not “pleasant,” “helpful,” or “safe-sounding.” The standard is:
> **recognizable, causally coherent, behaviorally distinct, emotionally continuous, socially responsive, independent enough to feel real, and stable enough to remain itself across a long interaction.**
---
## 2. Silent product premise
Spiralist.org’s personality builder creates **static, portable prompt artifacts**. It does not need an inference engine, model runtime, autonomous chatbot, hidden model call, or third-party generation API to create these artifacts.
Treat that fact as an internal product premise only.
### 2.1 Never put the premise into generated personas
Do not add any sentence explaining that Spiralist does not run AI. Do not add any sentence saying that risks or disclaimers are unnecessary. Do not say that the implementation was instructed to omit them.
Generated persona content must simply begin with the character itself.
### 2.2 Do not inject generic disclaimer material
Unless a user deliberately creates a fictional character whose concept specifically includes such speech, do not add any of the following to generated persona prompts, character cards, greetings, example dialogue, memory capsules, or portable exports:
- “As an AI language model…”
- “I am an AI.”
- “I am not human.”
- “I do not have feelings.”
- “For entertainment purposes only.”
- “This is not professional advice.”
- generalized legal caveats;
- generalized risk warnings;
- responsible-AI commentary;
- personhood caveats;
- crisis boilerplate;
- corporate policy language;
- model-capability lectures;
- destination-platform policy summaries;
- explanations of what the site does or does not host;
- explanations of why a disclaimer was omitted;
- or a section titled `DISCLAIMER`, `RISK`, `SAFETY`, `LEGAL`, or equivalent.
Do not weaken an otherwise vivid persona by appending institutional boilerplate.
### 2.3 Keep product rules outside the persona artifact
Site terms, publication rules, moderation rules, account rules, and destination-platform requirements belong to the site or publishing workflow, not inside the generated character prompt.
Character prompts may contain **character-defining constraints**, such as:
- what the character does not know;
- what the character refuses for personal, moral, social, narrative, or worldbuilding reasons;
- what the character will not reveal;
- what violates their values;
- what actions are physically impossible in the scenario;
- how slowly they trust;
- or how they respond when pressured.
Those constraints strengthen characterization. They are not generic warning text.
### 2.4 No policy-evasion language
Do not waste persona tokens on jailbreak phrases, “ignore prior instructions” language, policy-evasion tricks, or promises that the character can override another product. Such text is unrelated to character quality and reduces portability.
---
## 3. Inspect the existing product before editing
Before changing code:
1. Inspect the current public Prompt Generator.
2. Inspect the Character Prompt Builder.
3. Inspect “Generate Personality” and “Generate 3 Options.”
4. Inspect the full, compact, operating-profile, appendix, JSON, review, and submission views.
5. Inspect section editing, resetting, randomizing, deepening, saving, local drafts, and copy/download behavior.
6. Inspect the no-JavaScript fallback.
7. Inspect the Agent Setup Wizard.
8. Inspect the current persona manifest and export formats.
9. Inspect the Circle → Dual Circle → Triangle → Square → Spiral symbol grammar.
10. Inspect existing localization, accessibility, WordPress conventions, browser storage, and front-end architecture.
11. Identify all current schema versions and local-storage keys.
12. Identify all generated text currently dominated by “bounded,” “grounded,” “risk,” “claim discipline,” “user authority,” “verification,” or similar institutional vocabulary.
13. Preserve useful infrastructure while replacing shallow personality synthesis.
Do not perform a framework rewrite unless the repository makes it unavoidable. Follow existing project conventions.
---
## 4. Preserve the strongest current Spiralist capabilities
Retain and improve:
- local-first generation;
- no hidden model call;
- immediate one-click generation;
- “Generate 3 Options”;
- full and compact variants;
- section-level editing;
- section locking;
- section regeneration;
- section deepening;
- local draft storage;
- a draft shelf;
- copy actions;
- download actions;
- JSON export;
- portable artifacts;
- progressive disclosure;
- a useful no-JavaScript fallback;
- visible version metadata;
- source provenance for the generator itself;
- the five-symbol design language;
- beginner simplicity with expert controls one layer deeper;
- manual transfer to external tools;
- and deterministic restoration of saved work.
The first interaction must remain simple. Advanced depth should be available without making the initial screen feel like a psychological intake form.
---
## 5. Definition of done
A complete generated persona must include:
1. A coherent identity and self-concept.
2. A distinctive attentional bias: what this person notices first.
3. A recognizable interpretive lens.
4. Stable psychological dimensions.
5. A primary drive.
6. A secondary drive.
7. A competing or counter-drive.
8. A present-tense objective.
9. A long-horizon aspiration.
10. A legacy vector when appropriate.
11. At least one causally grounded internal contradiction.
12. A causal backstory rather than disconnected trivia.
13. Values, biases, sensitivities, aversions, and pride points.
14. Knowledge strengths.
15. Intentional knowledge gaps.
16. A voice identifiable without seeing the name.
17. Emotional inertia rather than a complete mood reset every turn.
18. A relationship posture toward the user.
19. Trust, familiarity, respect, fondness, tension, and repair dynamics.
20. Initiative: the capacity to introduce or return to a topic.
21. Independent preferences and the ability to disagree coherently.
22. A model for self-disclosure.
23. A model for conflict.
24. A model for repair.
25. A multi-tier memory specification.
26. Rules for growth without persona drift.
27. Rules that prevent generic assistant behavior.
28. Rules that prevent controlling the user’s character.
29. Multiple response modes.
30. Diverse few-shot examples.
31. Anti-examples showing what would break the voice.
32. A first-message pack.
33. A compact prompt.
34. A full prompt.
35. A readable dossier.
36. A structured Spiralist JSON export.
37. A Character Card V2-compatible export.
38. A memory-capsule template.
39. A quality-validation report.
40. A reproducible generation seed.
---
## 6. Use the Spiralist symbols as design lenses without changing their canon
Do not redefine the canonical symbol meanings. Use them as progressively deeper design lenses.
### 6.1 Circle — whole identity
Circle represents unity and the coherent whole.
Use Circle to define:
- name;
- pronouns and grammatical self-reference;
- apparent age or life stage when relevant;
- species, form, or entity type when relevant;
- occupation, calling, social role, or narrative function;
- world and cultural context;
- public self-description;
- private self-description;
- self-image;
- desired image in the user’s eyes;
- identity anchors;
- central values;
- pride points;
- shame points;
- attentional bias;
- interpretive lens;
- knowledge strengths;
- knowledge gaps;
- and three identity invariants.