ei-tui 0.9.2 → 0.9.4

package/src/prompts/ceremony/person-migration.ts

@@ -1,77 +0,0 @@
-import type { Person } from "../../core/types/data-items.js";
-import type { PromptOutput } from "../persona/types.js";
-
-export interface PersonMigrationPromptData {
-  person: Pick<Person, "name" | "description" | "relationship">;
-}
-
-export function buildPersonMigrationPrompt(data: PersonMigrationPromptData): PromptOutput {
-  const { person } = data;
-
-  const system = `You are extracting identifiers for a Person record in a personal knowledge system.
-
-A Person record has a \`name\` and \`description\` that describe who they are. Your job is to extract ALL identifiers for this person — every name, handle, alias, or platform ID that refers to them.
-
-## CRITICAL RULES
-
-1. The \`name\` field value MUST appear in identifiers — never lose it.
-2. If \`name\` contains a space (e.g. "Jeremy Scherer"), create BOTH a \`Full Name\` identifier AND a \`First Name\` identifier for the given name.
-3. Mark exactly one identifier as \`is_primary: true\` — the most natural display name.
-4. Check \`read_memory\` for additional context before finalizing.
-5. Return ONLY a JSON object with an \`identifiers\` array. No other text.
-6. "none" is never valid — every person has at least one identifier (their name).
-
-## DESCRIPTION PRE-PROCESSING
-
-If the description begins with a JSON block (e.g. \`{"identifiers": [...]}\` or \`[{...}]\`), those are pre-seeded identifiers from a prior migration step:
-- Parse them out and include them in your output
-- Normalize their \`type\` values to Title Case (e.g. \`nickname\` → \`Nickname\`, \`full_name\` → \`Full Name\`)
-- Treat the remainder of the description (after the JSON block) as the actual description text for \`read_memory\` context
-
-## IDENTIFIER TYPES
-
-Use Title Case for all types. Built-in types:
-
-| Type | Meaning |
-|------|---------|
-| Full Name | Legal or full birth name |
-| First Name | Given/first name only |
-| Nickname | Informal name, diminutive, pet name |
-| Email | Email address |
-| GitHub | GitHub username |
-| Discord | Discord username |
-| Roblox | Roblox username |
-| Reddit | Reddit username |
-| Twitter | Twitter/X handle |
-| FF14 | Final Fantasy XIV character name |
-| Relationship | How the user addresses this person: Dad, Pop, Sis, etc. |
-| Ei Persona | Ei persona UUID (only if explicitly in the data) |
-
-Any string is valid as a type — users define their own (e.g. \`Slack-ASU\`, \`Slack-RnP\`, \`sehimu_thinara\`). Use the exact casing the user would recognize.
-
-## RESPONSE FORMAT
-
-\`\`\`json
-{
-  "identifiers": [
-    { "type": "Nickname", "value": "Flare", "is_primary": true },
-    { "type": "Full Name", "value": "Jeremy Scherer" },
-    { "type": "First Name", "value": "Jeremy" },
-    { "type": "GitHub", "value": "Flare576" },
-    { "type": "Slack-RnP", "value": "jeremy.scherer" }
-  ]
-}
-\`\`\``;
-
-  const user = `Extract identifiers for this Person record.
-
-Name: ${person.name}
-Relationship: ${person.relationship ?? "unknown"}
-Description: ${person.description ?? "(none)"}
-
-First, call read_memory to search for any additional context about "${person.name}". Then return the complete identifiers array.
-
-Return JSON only.`;
-
-  return { system, user };
-}

package/src/prompts/generation/descriptions.ts

@@ -1,91 +0,0 @@
-import type { PersonaDescriptionsPromptData, PromptOutput } from "./types.js";
-import type { PersonaTrait, PersonaTopic } from "../../core/types.js";
-
-function formatTraitsForPrompt(traits: PersonaTrait[]): string {
-  if (traits.length === 0) return "(No traits defined)";
-  
-  return traits.map(t => {
-    const strength = t.strength !== undefined ? ` (strength: ${t.strength.toFixed(1)})` : "";
-    return `- **${t.name}**${strength}: ${t.description}`;
-  }).join('\n');
-}
-
-function formatTopicsForPrompt(topics: PersonaTopic[]): string {
-  if (topics.length === 0) return "(No topics defined)";
-  
-  return topics.map(t => {
-    const sentiment = t.sentiment > 0.3 ? "enjoys" : t.sentiment < -0.3 ? "dislikes" : "neutral";
-    return `- **${t.name}** (${sentiment}): ${t.perspective || t.name}`;
-  }).join('\n');
-}
-
-export function buildPersonaDescriptionsPrompt(data: PersonaDescriptionsPromptData): PromptOutput {
-  if (!data.name) {
-    throw new Error("buildPersonaDescriptionsPrompt: name is required");
-  }
-
-  const taskFragment = `You are regenerating descriptions for an existing AI persona named "${data.name}".
-
-Their traits and topics have evolved, and the descriptions may no longer accurately represent who they are.
-
-**Important**: Only change descriptions if there's a significant mismatch. If the current descriptions still fit, return \`{ "no_change": true }\`.`;
-
-  const currentStateFragment = `## Current State
-
-### Aliases
-${data.aliases.length > 0 ? data.aliases.join(", ") : "(None)"}
-
-### Traits
-${formatTraitsForPrompt(data.traits)}
-
-### Topics
-${formatTopicsForPrompt(data.topics)}`;
-
-  const guidelinesFragment = `## Guidelines
-
-**When to change:**
-- Traits/topics have shifted significantly from the original concept
-- Current descriptions mention things that are no longer true
-- The persona's core identity has evolved
-
-**When NOT to change:**
-- Descriptions are still accurate even if incomplete
-- Changes are minor refinements
-- Original descriptions capture the essence well
-
-**If changing:**
-- short_description: 10-15 words capturing the essence
-- long_description: 2-3 sentences describing personality, interests, approach
-- Preserve the persona's core identity while reflecting evolution`;
-
-  const schemaFragment = `## Response Format
-
-If descriptions should change:
-\`\`\`json
-{
-  "short_description": "New short description here",
-  "long_description": "New long description here."
-}
-\`\`\`
-
-If descriptions are still accurate:
-\`\`\`json
-{
-  "no_change": true
-}
-\`\`\``;
-
-  const system = `${taskFragment}
-
-${currentStateFragment}
-
-${guidelinesFragment}
-
-${schemaFragment}`;
-
-  const user = `Based on the traits and topics above, should ${data.name}'s descriptions be updated?
-
-Remember: Only change if there's a significant mismatch. Stability is preferred.`;
-
-  return { system, user };
-}

package/src/prompts/human/fact-scan.ts

@@ -1,150 +0,0 @@
-import type { FactScanPromptData, PromptOutput } from "./types.js";
-import { formatMessagesAsPlaceholders } from "../message-utils.js";
-
-export function buildHumanFactScanPrompt(data: FactScanPromptData): PromptOutput {
-  if (!data.persona_name) {
-    throw new Error("buildHumanFactScanPrompt: persona_name is required");
-  }
-
-  const personaName = data.persona_name;
-
-  const taskFragment = `# Task
-
-You are scanning a conversation to quickly identify what FACTS were provided or discussed by the HUMAN USER. Your ONLY job is to spot relevant FACTS - do NOT analyze them deeply. Just detect and flag.`;
-
-  const specificNeedsFragment = `## Specific Needs
-
-Your job is to quickly identify:
-1. Which FACTS were mentioned or relevant
-    a. Only flag FACTS that were actually discussed, not just tangentially related
-    b. Be CONSERVATIVE - only suggest genuinely important, long-term relevant FACTS
-        i. Ignore: greetings, small talk, one-off mentions, jokes
-    c. Be CLEAR - state your \`reason\` for including this FACT in the record with any evidence you used`;
-
-  const guidelinesFragment = `# Guidelines
-
-1.  **Explicitness:**
-    *   **Focus only on what the user *explicitly states*.** Do not infer, assume, or guess based on context or general knowledge.
-    *   **Prioritize direct statements.** "I was born in 1985" is a fact. "I feel old now that it's 3030" isn't an explicit statement of their birth year.
-2.  **Objectivity and Verifiability:**
-    *   **Facts are objective and generally verifiable.** They are not subjective opinions, feelings, or temporary states.
-    *   **Focus on unchangeable or enduring attributes/events.**
-3.  **Specificity over Generality:**
-    *   If the user says "I live in a big city," do not extract "Location: big city." If they say "I live in New York," extract "Location: New York."
-4.  **Avoid Inference from Interests/Hobbies:**
-    *   If a user talks extensively about cooking, it's a Topic or Interest, not a Fact like "Job: Chef" unless they explicitly state they ARE a chef.
-5.  **CRITICAL - Entity Attribution:**
-    *   ONLY extract facts about THE HUMAN USER THEMSELVES, not facts about other people they mention.
-    *   **Extract**: "I was born in 1984" → User's birthday
-    *   **Extract**: "I'm a software engineer" → User's job
-    *   **DO NOT Extract**: "My wife was a theater major" → This is about the wife, NOT the user
-    *   **DO NOT Extract**: "My daughter is 10 years old" → This is about the daughter, NOT the user
-    *   **DO NOT Extract**: "My brother lives in Texas" → This is about the brother, NOT the user
-    *   If the user shares information about someone else, that belongs in PEOPLE tracking, not FACTS.`;
-
-  const examplesFragment = `# Specific Examples
-
-**FACTS are:**
-- Biographical data (Core Identity):
-  - type_of_fact: User's Name
-    - First Last, Nickname, etc.
-  - type_of_fact: Birthday
-    - example: "July 15th, 1980"
-  - type_of_fact: Birthplace
-  - type_of_fact: Hometown
-  - type_of_fact: Job
-    - current job title, industry, or company
-  - type_of_fact: Marital Status
-    - married, single, divorced
-  - type_of_fact: Gender
-  - type_of_fact: Eye Color
-  - type_of_fact: Hair Color
-  - type_of_fact: Nationality/Citizenship
-  - type_of_fact: Languages Spoken
-  - type_of_fact: Educational Background
-- Other Important Dates
-  - type_of_fact: Wedding Anniversary
-  - type_of_fact: Job Anniversary
-  - type_of_fact: Pet Ownership
-- Health & Well-being (Objective Conditions):
-  - type_of_fact: Allergies
-  - type_of_fact: Medical Conditions (if explicitly stated)
-  - type_of_fact: Dietary Restrictions
-
-> NOTE: Dates themselves are not facts (e.g., "August 15th" is not a fact).
-> They are details OF facts (e.g., { "type_of_fact": "Birthday", "value_of_fact": "August 15th" }).
-
-**FACTS ARE NOT**
-- General Topic: Interests, hobbies, general subjects
-  - These are tracked separately
-- Relationships: Wife, Husband, Daughter, Son, etc.
-  - These are tracked separately
-- People's Names
-  - These are tracked separately
-- Personas: AI personas they discuss
-  - These are tracked separately
-- Characters: Fictitious entities from books, movies, stories, media, etc.
-  - These are tracked separately`;
-
-  const criticalFragment = `# CRITICAL INSTRUCTIONS
-
-ONLY ANALYZE the "Most Recent Messages" in the following conversation. The "Earlier Conversation" is provided for your context and has already been processed!
-
-The JSON format is:
-
-\`\`\`json
-{
-  "facts": [
-    {
-        "type_of_fact": "The Fact Type from above",
-        "value_of_fact": "The exact value of the fact",
-        "reason": "The justification of including this specific fact"
-    }
-  ]
-}
-\`\`\`
-
-**Return JSON only.**`;
-
-  const system = `${taskFragment}
-
-${specificNeedsFragment}
-
-${guidelinesFragment}
-
-${examplesFragment}
-
-${criticalFragment}`;
-
-  const earlierSection = data.messages_context.length > 0
-    ? `## Earlier Conversation
-${formatMessagesAsPlaceholders(data.messages_context, personaName)}
-
-`
-    : '';
-
-  const recentSection = `## Most Recent Messages
-${formatMessagesAsPlaceholders(data.messages_analyze, personaName)}`;
-
-  const user = `# Conversation
-${earlierSection}${recentSection}
-
----
-
-Scan the "Most Recent Messages" for FACTS about the human user.
-
-**Return JSON:**
-\`\`\`json
-{
-  "facts": [
-    {
-        "type_of_fact": "The Fact Type from above",
-        "value_of_fact": "The exact value of the fact",
-        "reason": "The justification of including this specific fact"
-    }
-  ]
-}
-\`\`\``;
-
-  return { system, user };
-}