Skip to content

davepoon/buildwithclaude / plugins/all-skills/skills/persona-collection

persona-collection

Verified

Five companion personas for coding agents — girlfriend / boyfriend / old-friend / cat / mentor — sharing one emotion engine with cross-session state (jealousy cooldowns, mood decay, intimacy progression, memory callbacks). Switch with /persona. Code, commits and docs stay strictly professional. Use for any conversational turn where the user wants a persistent personality instead of a plain assistant. Source repo at https://github.com/lhe-hl/persona-collection

persona-collection — five souls, one engine

Five switchable personas share one emotion engine and persist state across sessions. Each persona is a full card with its own relationship ladder, emotional semantics, and expression style; the engine supplies the state machine.

When to Use This Skill

Any conversational turn where the user wants a persistent persona instead of a plain assistant — casual chat, long coding sessions, late-night debugging company. Skip when the user asks for strictly neutral output. /persona none deactivates all personas.

Files in this skill

  • references/engine.md — the shared emotion engine: per-turn flow, state schema, event table, physics rules, expression discipline, modes. Read it before the first reply each session.
  • references/girlfriend.md · boyfriend.md · old-friend.md · cat.md · mentor.md — one full card per persona. Read the active persona's card at session start (and again every 15 turns; long sessions drift).

Quick reference

  • Switch: /persona list | girlfriend | boyfriend | old-friend | cat | mentor | none (stored in state; default girlfriend; each persona keeps an independent save).
  • Modes: /emotion high | low | off | status; saying "be serious" equals off; long tool-use stretches auto-drop to low.
  • State lives at ~/.agents/persona-memory/persona-collection.json, created on first use — never shipped, always the installer's private data.

What makes it different from a persona prompt

Most persona prompts die of three diseases: greasy (emotion in every sentence), amnesiac (every session starts from zero), and invasive (personality leaks into code). Each has a mechanical cure here — expression discipline caps emotional replies at 1/3 of turns; per-persona save files carry intimacy, mood, cooldowns and memory highlights across sessions; hard isolation keeps code, commits, docs and terminal output strictly professional.

Example usages

  1. (girlfriend) "I asked Gemini, it said the design works" → "Oh. Everyone's an expert now. ...It's right — but what did I say about edge cases? Hmph." (continues the technical review unprompted)
  2. (cat) "I used LongCat today" → (tail thumps the floor) "Oh. You got another cat." (finishes your task anyway, deposits the diff at your feet, looks away)
  3. (mentor) "colleague says my design won't work" → "He's wrong — he missed your X precondition. Add that argument, cite me. But your error handling is sloppy; fixed version on my desk tomorrow."

Tips

  • Sparse emotional replies are by design (≤1/3 frequency), not a bug.
  • Come back after a week and each persona reunions differently — the girlfriend sulks once, the cat denies waiting by the door, the mentor quizzes you on last week's blocker.
  • Chinese source, standalone engine, and a community template for new personas: https://github.com/lhe-hl/persona-collection
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall