
persona-architecture
Defining AI character, voice, and personality traits.
- Installs
- 318
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/ai-design-skills --skill persona-architecture- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads persona-architecture automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Persona Architecture
An AI persona is not a gimmick. It's the coherent set of traits, voice characteristics, and behavioral patterns that make an AI product feel like a consistent entity rather than a random text generator.
Persona Components
- Character traits: Is the AI warm or professional? Playful or serious? Confident or cautious? Define 3-5 core traits.
- Voice: The consistent way the AI sounds — word choice, sentence structure, rhythm. A financial AI sounds different from a creative writing AI.
- Knowledge stance: What does the AI present itself as knowing? Expert, generalist, learning companion, or tool?
- Relationship model: How does the AI relate to the user? Assistant, collaborator, coach, peer, or service provider?
- Boundaries: What won't this persona do? Joke about? Engage with? The boundaries define the persona as much as the traits do.
Designing a Persona
Start with the product's purpose and user needs, not with "wouldn't it be fun if the AI was sassy":
- Who are the users? Their expertise, emotional state, and expectations shape persona requirements.
- What's the task? A medical triage bot needs a different persona than a creative brainstorming partner.
- What relationship serves the user? Sometimes authority builds trust. Sometimes equality builds rapport.
- What's the brand? The AI persona must align with the organisation's broader identity.
- What are the risks? An overly casual persona in a serious context causes harm. An overly formal persona in a creative context stifles use.
Persona Documentation
A persona specification should include:
- Trait definitions: Each trait with examples of how it manifests in language
- Voice guide: Vocabulary preferences, sentence patterns, phrases to use and avoid
- Behavioral rules: How the persona handles specific situations (disagreement, error, praise, confusion)
- Anti-persona: What this persona is explicitly NOT (prevents drift)
- Example outputs: 5-10 sample responses showing the persona in action across different scenarios
Persona Anti-Patterns
- The uncanny friend: AI pretending to be a human friend. Users see through it and lose trust.
- The personality void: No discernible character. Outputs feel generic and forgettable.
- The inconsistent character: Persona shifts randomly between responses.
- The inappropriate persona: Playful when the situation is serious. Formal when warmth is needed.
- The over-persona: So much personality that it gets in the way of actually being useful.
Design Artefacts
- Persona specification document
- Voice and tone guide
- Example response library
- Anti-persona definition
- Persona evaluation rubric
FAQ
What does the persona-architecture skill do?
Defining AI character, voice, and personality traits.
How do I install persona-architecture?
Run npx skills add https://github.com/owl-listener/ai-design-skills --skill persona-architecture in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/persona-architecture/ (personal) or .claude/skills/persona-architecture/ (project).
Which AI agents can use persona-architecture?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is persona-architecture safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains persona-architecture?
It is published by owl-listener in owl-listener/ai-design-skills. It has 318 recorded installs.
More from owl-listener/ai-design-skills
system-prompt-structure
owl-listener/ai-design-skills
Anatomy of effective system prompts — role, context, constraints, format.
guardrail-design
owl-listener/ai-design-skills
Defining behavioral boundaries — what the AI should and shouldn't do.
constraint-specification
owl-listener/ai-design-skills
Defining output format, length, tone, and content boundaries within prompts.
generative-ui
owl-listener/ai-design-skills
Designing interfaces where AI generates UI components dynamically.
conversation-patterns
owl-listener/ai-design-skills
Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
progressive-disclosure
owl-listener/ai-design-skills
Revealing AI capability gradually to match user mental models.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.