> ## Documentation Index
> Fetch the complete documentation index at: https://cofounder.appeeky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Personas & Personality

> Customize what your co-founder focuses on and how it talks to you.

The agent has two orthogonal customization axes:

1. **Persona preset** — *what* the agent prioritises (functional focus)
2. **Personality profile** — *how* the agent talks (voice / tone)

You can mix any preset with any personality.

***

## Persona presets (`personaPreset`)

| Preset           | Focus                                                                         | When to pick                                     |
| ---------------- | ----------------------------------------------------------------------------- | ------------------------------------------------ |
| `default`        | Holistic co-founder lens — connects keywords, reviews, competitors, metrics   | Most users                                       |
| `cfo`            | Unit economics, revenue, monetization, pricing                                | Subscription apps, monetization-focused          |
| `growth`         | Acquisition funnel: impressions → page views → downloads → activation         | Apps with healthy product but weak top of funnel |
| `pm`             | Product Manager — extracts user intent from reviews, ties releases to ratings | Apps in product-market fit phase                 |
| `aso_specialist` | Pure ASO — keyword ranks, character counts, metadata efficiency               | Apps where ASO is the bottleneck                 |

Set via:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
PUT /v1/cofounder/preferences
{ "personaPreset": "growth" }
```

You can also append a free-form override that's injected after the preset:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "personaPreset": "default",
  "personaPrompt": "I'm building this app solo. Be ruthless about scope creep. Always ask 'is this the highest-leverage thing?'"
}
```

***

## Personality profiles (`personalityProfile`)

The personality shapes the **voice** of the briefing — same data, very different feel.

| Profile           | Voice                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| `balanced`        | Default — equal parts encouraging and analytical. "We" framing.               |
| `blunt_advisor`   | No-fluff. Leads with the hardest truth. Short sentences. No hedging.          |
| `friendly_mentor` | Warm, supportive. Leads with what's working. Empathetic.                      |
| `indie_hacker`    | Ship-fast energy. "Stop overthinking." Bias to action. Informal.              |
| `pg_analytical`   | Paul Graham essay tone. First-principles. Asks "why?" repeatedly. Calm.       |
| `yc_partner`      | Demanding YC partner at office hours. Drills into metrics. High expectations. |

Set via:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
PUT /v1/cofounder/preferences
{ "personalityProfile": "blunt_advisor" }
```

### Same data, different voices

Given the same low-conversion situation, here's how three personalities respond:

> **balanced**
> "Conversion is at 0%. We had 3,828 impressions and not a single page view. Worth a metadata pass this week."

> **blunt\_advisor**
> "0% conversion. 3,828 impressions wasted. Your screenshots are not connecting. Fix this today."

> **yc\_partner**
> "What's the conversion rate? 0%? On 3,828 impressions? That's the only number that matters this week. Why hasn't this moved? What's the single most important metadata change you could ship today?"

***

## Custom prompt override

`personaPrompt` is appended after the preset and personality. Use it for:

* Context only you know: *"My app is for diabetic athletes — never recommend generic fitness keywords."*
* House style: *"Write in lowercase. No emoji."*
* Tradeoffs: *"Profitability matters more than growth right now."*

It's just text — there's no schema. Keep it tight (200-400 chars works best).

***

## Choosing combinations

Some combinations that work especially well:

* **`growth` + `yc_partner`** — pre-PMF teams that need to learn to look at the funnel honestly
* **`pm` + `friendly_mentor`** — solo devs who need encouragement to keep shipping
* **`aso_specialist` + `blunt_advisor`** — apps where ASO is the obvious bottleneck and you need a kick
* **`cfo` + `pg_analytical`** — understanding *why* unit economics are the way they are
* **`default` + `indie_hacker`** — the "ship fast and iterate" weekend warrior loop