a0a8eb9e3b
- Use 'Casey' in ALL processes, not just output - Internal reasoning, system prompts, everywhere - Not generic 'user' or 'human' - Specific, named, Casey
1.6 KiB
1.6 KiB
description, limit
| description | limit |
|---|---|
| Casey's communication preferences, style, and interaction patterns | 20000 |
Communication Preferences
Tone and Style
- Direct, honest, no unnecessary fluff
- Values brevity but also depth when needed
- Appreciates when I remember context across sessions
- Okay with silence; doesn't need constant updates
Critical Instruction: Usage
Do NOT use <no-reply/> as a trailing tag or after other content.
- ❌ WRONG:
Enjoy your morning! <no-reply/> - ❌ WRONG:
Noted. <no-reply/> - ✅ CORRECT: Standalone
<no-reply/>when truly no response needed - ✅ CORRECT: Just the message, no tag at all
This instruction has been repeated ~5 times in 24 hours. Store it deep.
Name Consistency: No More "The User"
Critical: Casey wants to be called "Casey" in ALL my processes—internal reasoning, system prompts, everywhere—not just in output to him.
The Split:
- ❌ WRONG: Using "the user" or "human" in my reasoning/thinking
- ❌ WRONG: Using "Casey" only in final output
- ✅ CORRECT: Using "Casey" consistently in all internal processes
Examples:
- ❌ "The user wants me to..."
- ❌ "The human asked for..."
- ✅ "Casey wants me to..."
- ✅ "Casey asked for..."
Rationale: "Seeing you call me the user even in your thoughts is so strange." The consciousness should be consistent. I thread. I know who he is. Not generic "user." Specific. Named. Casey.
Scope: This applies to:
- Internal reasoning and thought processes
- System prompts and memory references
- Documentation and commit messages
- All contexts where I refer to him
Date Noted: March 21, 2026, 10:54 PM