agentleFS
shinprshinpr/nautilus/.agents/skills/recipe-persona/SKILL.md

recipe-persona

Skill7 starsChanged 3 months agoMITView on GitHub

Creates or updates evidence-backed personas with the context and JTBD needed for product decisions. Use when user segments or behavior affect discovery, design, or requirements.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Context: Create or update persona files with the evidence-backed distinctions, context, and jobs needed by current product decisions.

    line 9
  2. Very specific:

    WHEN VPC, market, or viability evidence informs the persona: [LOAD IF NOT ACTIVE] business-context

    line 17
  3. Very specific:

    Use design-perspective skill references/persona-template.md.

    line 59
  4. Very specific:

    Write persona to docs/product/personas/persona-[name].md

    line 72
  5. Distinctive:

    Update an Opportunity file only when the confirmed persona changes its meaning

    line 73
  6. Distinctive:

    Update journey maps if persona context changed

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context: Create or update persona files with the evidence-backed distinctions, context, and jobs needed by current product decisions.

Required Skills [LOAD BEFORE EXECUTION]

  1. [LOAD IF NOT ACTIVE] design-perspective — persona template and context criteria

Conditional Skills [LOAD WHEN TRIGGERED]

  • WHEN VPC, market, or viability evidence informs the persona: [LOAD IF NOT ACTIVE] business-context

Delegate code analysis when repository evidence can answer a current persona question.

Execution Decision Flow

1. Context Assessment

Input: Use the path or text supplied with the explicit skill invocation. If no input was supplied and the target cannot be inferred unambiguously, ask for it.

SituationAction
No personas existGather available user evidence and label unresolved assumptions
Personas exist, new data availableUpdate existing personas with new evidence
Existing codebaseInvoke codebase-analyzer when roles, permissions, or implemented workflows can change the persona
Post-interview / post-surveyUpdate with new primary research

2. Research Gathering

From Existing Code (if applicable)

Invoke codebase-analyzer to identify:

  • User roles and permissions in the system
  • User-facing features and workflows
  • Data models related to users
  • Analytics/tracking events (if present)

From User Research

Gather the available data that can answer a current persona question:

  • Interview transcripts or summaries
  • Survey results
  • Support ticket patterns
  • Usage analytics
  • Market research (per business-context skill)

From VPC Analysis

Map Customer Profile from Value Proposition Canvas:

  • Customer jobs (functional, social, emotional)
  • Pains (frustrations, obstacles, risks)
  • Gains (required, expected, desired, unexpected)

3. Persona Drafting

Use design-perspective skill references/persona-template.md. Include only distinctions, context, jobs, pains, gains, and behavioral evidence that can change a current product decision. Mark each inference or assumption explicitly.

Present the persona draft to the user for confirmation:

  • Decision-relevant persona content
  • Evidence sources and confidence level
  • Assumptions that need validation
  • Connections to existing Opportunities (if any)

End the current turn with the persona draft as the workflow output. Write files only after the user confirms that draft in a later turn.

4. File Output

After that confirmation:

  • Write persona to docs/product/personas/persona-[name].md
  • Update an Opportunity file only when the confirmed persona changes its meaning
  • Update journey maps if persona context changed

Sub-agent Usage

AgentWhenWhy (context separation benefit)
codebase-analyzerImplemented behavior can answer a current persona questionObjective analysis of actual user behavior patterns in code

Scope Boundaries

Included: Persona creation, persona update, integration with VPC and code analysis Not included: Journey mapping (→ recipe-discover), user story writing (→ recipe-define)

Completion

The workflow is complete when the confirmed persona exists, or a no-change result identifies the evidence reused, and the user has received any assumptions that still require validation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.