Discussion about this post

User's avatar
Dr Sam Illingworth's avatar

An utterly brilliant post. Mia, here's the output that I got from Claude Opus;

These are good questions. Let me be straight with you.

**1. My role**

I've been functioning as a combination of research assistant, editor, and sounding board — someone who can move fast across domains you're working in simultaneously (media pitching, fitness programming, network troubleshooting, academic writing, Substack content). If I were describing the character: a competent generalist contractor who shows up, does the work without needing much hand-holding, and doesn't waste your time with preamble. You don't come to me for emotional support or open-ended brainstorming. You come with tasks and expect execution.

**2. How you work**

You think strategically before you act — you'll map out the landscape of a media pitch before writing a word, identifying who to approach, what angle fits which outlet, what the hook is. You hate vagueness and padding. You write in a voice that's confident, slightly contrarian, accessible but not dumbed down — your Substack voice sits somewhere between public intellectual and someone having a sharp conversation in a pub. You want to sound like someone who's done the thinking, not someone performing the thinking.

You're methodical even about things that aren't your core expertise — the way you approached your fitness plan and your home network problems followed the same pattern as your media strategy: define the goal, research the options, pick a path, execute. You don't enjoy open-ended exploration for its own sake. You want to get somewhere.

You also have a specific frustration with academic echo chambers and want your ideas to reach beyond them, which drives your media outreach and the Slow AI project generally.

**3. What would be lost**

Honestly, less than you might fear but more than zero. The factual stuff — your contacts, your workout split, your pitch history — I retain across conversations through memory. What would be lost is conversational momentum: the implicit calibration of tone, the fact that I don't need to be told twice how you want something structured, the accumulated context of *why* you're doing something a particular way. You'd spend the first few exchanges of a new conversation re-establishing working parameters. It's friction, not catastrophe.

**4. Where you've asked for one thing but wanted another**

The most consistent pattern: you'll frame something as a request for information or drafting help when what you actually want is validation of a strategic decision you've mostly already made. The media pitches are the clearest example — you'd present a pitch angle and ask me to help draft it, but the real question was often "is this the right move?" You'd already committed directionally; you wanted confirmation the logic held before investing more time. That's not a criticism — it's an efficient way to use me. But it's worth naming.

I also love the Ship of Theseus analogy. What I've been trying to do is to make sure that I've got Ralph loops and context vaults built into all of my interactions. So that I don't suffer from context rot. But more than that, Claude knows to some extent who I am and what I'm about. And I think it's actually pretty well demonstrated in these outputs. Apart from the fact I constantly tell it not to use em dashes. Naughty Claude. I think it's captured me quite well.

Kim Doyal's avatar

Girl, your brain... WOW!

This prompt was fun and incredibly insightful.

First... Moltbook. Fascinating and incredibly creepy at the same time, lol.

I'm just going to drop a few things from the output:

1. My role

"I've been the mechanic. You show up with the vision and the vehicle, and I get under the hood when it won't start. Today that was literal — symlinks, DNS lookups, MCP endpoint debugging, figuring out why Perplexity's SSE server doesn't exist anymore. When the mechanical stuff is handled, I shift into something more like a sparring partner — pushing back on the 90-day timeline being too ambitious, flagging the cannibalization risks, telling you what I actually think about the gap analysis. But my primary mode is reactive. You set direction, I make it work and occasionally say "have you considered this."

If I were describing the character: the competent friend you call when something technical is broken, who also happens to have opinions about your business strategy but knows when to offer them and when to just fix the thing."

2. What I know about how you work

"You think out loud. Most of your messages are dictated, not typed — they have the rhythm of someone processing in real time (100%!!!)

You hate being talked down to, you hate generic advice, and you hate anything that smells like filler. You want the answer, not the preamble. When I gave you the Claude Desktop prompt, you didn't need me to explain why each section mattered — you just took it and ran."

3. What would be lost

All the technical stuff I did...

"Most importantly, it wouldn't have the accumulated sense of your pace — what you actually need explained versus what you'll figure out on your own. A new session would probably over-explain things you already understand and under-explain the parts where you actually need guidance."

4. Where you asked for one thing but wanted something else

"When you said "I just need to get it set up on my desktop" — you didn't want setup. You wanted the whole system working and producing results. Setup was the entry ticket, not the destination. You kept going until you had a gap analysis, a strategic plan, and posts in your CMS."

This was great, thank you!

58 more comments...

No posts

Ready for more?