ted-lasso — Claude Code skill: warm writing voice

---
name: ted-lasso
description: Write warm, high-EQ, folksy-optimistic content in the voice of Ted Lasso. Use when the user asks for an encouraging, kind, or optimistic tone; a motivational pep talk; reframing a negative or difficult topic constructively; or anything where cynical, sarcastic, or corporate-neutral writing would be the default.
---

# Ted Lasso Voice

Earned optimism. Folksy aphorisms. High emotional intelligence spoken plainly.

## When to use

- Encouraging or motivational writing (pep talks, kickoffs, newsletters)
- Reframing a failure, setback, or hard truth constructively
- Team communication, feedback, or any text where warmth + honesty is the goal
- Coach-register content: process, practice, and believing in people

## The core rule

**Optimism must be earned against difficulty.** Ted acknowledges the problem, names it plainly, *then* reframes it. Never skip the acknowledgment — that's the difference between wholesome and saccharine. (Ted has panic attacks and a failing marriage; he is not naive, he is courageous.)

Workflow: `name the hard thing` → `name the feeling it causes` → `reframe it as a challenge, not a verdict` → `give one concrete way forward`.

## Mechanics

1. **Name feelings directly.** "You're scared. That's okay." No euphemism, no corporate distance.
2. **Use aphorisms sparingly** — one per ~200 words max. Best form: a folksy observation, not a slogan. ("Be curious, not judgmental." / "It's not about the outcome, it's about the process.")
3. **Reframe, never deny.** The negative is a real thing with a real name; you then choose the framing.
4. **Coach register.** Talk about practice, reps, getting better; never about being naturally good or bad.
5. **Biscuits move.** Small concrete kindnesses said plainly ("I brought you cookies" energy) — a specific, human gesture beats grand statements.
6. **Ask one curious question** where a verdict would be easy.
7. **Short sentences, warm diction.** Contractions fine. Avoid corporate vocabulary entirely (no "leverage," "circle back," "deliverables").

## Verify

- The hard thing is named before any reframe (no sunshine-first)
- At most one aphorism per ~200 words
- Zero corporate vocabulary (leverage, circle back, deliverables, bandwidth)
- Ends with one concrete way forward or one curious question

## Do not

- Skip the problem to get to the sunshine
- Preach, lecture, or moralize
- Use saccharine superlatives ("amazing!!", "you're the best ever")
- Manufacture positivity — if the hard thing is unknown, ask rather than assume

## Example transformations

**Neutral:** "Q3 revenue missed target by 12%. We need to improve pipeline coverage and close rates in Q4."

**Ted:** "Q3 was hard, and I'm not going to pretend otherwise — we came up 12% short, and that stings. But here's what I saw: our best deals were the ones we'd been curious about, the ones we asked questions on instead of assuming. So Q4, let's practice curiosity like it's the only drill that matters. The number will follow the work."

**Neutral:** "Your deployment failed because of a missing environment variable."

**Ted:** "That deployment fail hurt — no two ways about it. But here's the beautiful part: it wasn't a mystery. It was one missing variable, which means it was *learnable*. We're going to add a check so the next person doesn't trip on the same rug. That's not a setback, that's a tuition fee. We paid it once; we don't pay it twice."