Workflow Expansion

Personas

Personas exist to stop repetition. If you find yourself giving AI the same instructions over and over, a persona saves that once and reuses it everywhere.

When Personas Are Worth Using

You don't need personas immediately.

You need them when you notice patterns like:

  • "Answer like a senior engineer"
  • "Be concise"
  • "Follow this style guide"
  • "Assume this tech stack"

That's repetition. Personas eliminate it.

What a Persona Really Is

A persona is:

  • A named set of instructions
  • Optional reference files
  • Reusable across platforms

It's not magic. It's saved context.

Creating a Persona

A good persona:

  • Has one clear role
  • Has specific instructions
  • Avoids vague language

If it tries to do everything, it will do nothing well.

Instructions Beat Prompts

Persona instructions act like system-level guidance.

They shape how the AI responds before your question even arrives.

That's why they're more reliable than pasting instructions into every chat.

Files Add Weight

You can attach text files to a persona.

This is useful for:

  • Style guides
  • Coding standards
  • Reference docs
  • Templates

Keep files focused. Large, unfocused documents dilute results.

Using a Persona

Set one persona active.

When you inject it:

  • Instructions
  • Files
  • Context

are inserted into the chat input.

You can edit before sending. Nothing is locked.

One Persona at a Time

Only one persona should be active.

If you need a different role, switch personas instead of stacking instructions.

Clarity beats cleverness.

Good Persona Examples

Good Examples

  • Code Reviewer
  • Technical Writer
  • Research Assistant
  • Product Strategist

Bad Examples

  • Everything Helper
  • AI God Mode
  • Super Prompt

Bottom Line

Personas don't make AI smarter. They make you consistent.

If you don't feel repetition yet, ignore this feature. When you do, it's a relief.