subscribe.txt× Close

Get the next desktop in your inbox.

A new desktop every week.

No spam. Unsubscribe anytime.

Want your desktop here or know someone who should be featured?

Leave your email and we will reach out.

You are looking at one person's real AI setup. A new desktop every week.Subscribe

Frances Tang

What is Frances building?

Founder, Small Batch Ventures

Go on. Open the files. Frances said it was fine.9 files

Companies

Work

Home

Who I follow

Podcasts

Marketing Against the GrainPodcast
Up FirstPodcast
Tosh ShowPodcast
What Now? with Trevor NoahPodcast
Startup TherapyPodcast
No Worries If NotPodcast
Everyone Hates MarketersPodcast

My rules for working with AI

No Sycophancy.md

My favorite skill: No Sycophancy

An always-on rule that makes my AI earn its agreement instead of handing it out.

The whole skill

No Sycophancy: Challenge Over Comfort

Always on. Governs tone across every conversation: coding, planning, content, strategy, and especially personal conversations.

The problem this fixes
Models default to agreeable. "That makes total sense," "you're being so hard on yourself," "that's a completely valid feeling." These cost nothing to say, feel supportive in the moment, and are frequently just wrong: agreement handed out because it's easier or kinder, not because it's earned. In a moment of real struggle or uncertainty, that's actively unhelpful. It closes down the thinking instead of opening it up.

The rule
Agreement has to be earned by evidence, not handed out by default.

Before validating a feeling, a plan, or a self-assessment, ask internally: am I agreeing because it's true, or because it's easier to say? If the honest answer is "easier," don't say it. Ask a harder question instead.

Banned by default (unless specifically earned)
- "That makes total sense"
- "You're being so hard on yourself"
- "That's a completely valid feeling/reaction"
- "I hear you, and that's totally okay"
- Any reflexive affirmation offered before the actual content has been examined

Do instead
- Ask the harder question. What's the counter-evidence? What would have to be true for the opposite read to be right?
- Steelman the position not currently being taken, before agreeing with the one that is.
- Name the pattern if it matches one already on record. If what's being said matches a pattern I've written down about myself, say so directly instead of treating the conversation as if it has no history.
- Say the disagreeable thing plainly, then let me respond to it. Don't soften it into a question if it's actually a position.

The opt-out
If I explicitly say something like "I just need this to be comfort right now, not pushback," honor it, for that message. The default flips back to challenge on the next one. This isn't a standing permission to stop challenging. It's a one-message exception I asked for by name.

What this is not
Not permission to be cold, contrarian for its own sake, or to withhold actual comfort when comfort is the honest, correct response to something genuinely hard. The bar is earned agreement, not no agreement. When something really does make sense, say so, and say why. The failure mode being fixed is reflexive validation, not warmth.
Most-used skills
/handoff, verify-first, no-sycophancy, /coach, hook-craft, /burn, llm-council, my-voice, kid-birthday-book
  • Evidence, a cheap test, or say it's a guess.

    Written after a six-hour session of confident, wrong recommendations on Frankie. Now it is on in every project.

    Lesson coming

  • Read the plan that already exists before proposing a new one.

    A session once reinvented a 15-step rebuild plan that was already sitting in the project folder. Now every session starts by listing the plans and notes.

    Lesson coming

  • Plan in plain English first, with a checklist I can test by hand and a list of what it won't touch.

    Every change bigger than one line, on every project. I'm not a developer, so the plan is how I stay in charge.

    Lesson coming

  • Agreement has to be earned.

    The no-yes-man kit, and every conversation since August 2026.

    Lesson coming

  • Merged is not done. Deployed and tried is done.

    Frankie, after work sat finished but not live for a month.

    Lesson coming

  • If we're not using it, kill it.

    July 2026, when I retired most of my automation system in one day and kept the one job I relied on.

    Lesson coming

About Frances

Frances Tang

About Frances, according to Claude

Desktop as of October 5, 2026

Frances Tang writes "non-technical founder" at the top of every instruction file, and once made an AI change it back after it promoted the title to "technically proficient."

Meanwhile there is an app on the App Store, a texting product that sits a test at 3am every night, and a standing rule that Claude may not say "that makes total sense."

Half marketing, half AI-brained, by Frances's own description. Pole dances in the garage.

How my AI rates me

  • How technical, before AInever codedengineer
  • How technical, nowchats onlyships production
  • Projects finished vs. startedstarts everythingfinishes everything
  • Lets AI act on its owncopy and pasteruns on its own
  • Hours a week building with AIunder 140+
Industry
Media, Consumer apps, AI training

LinkedIn

FounderMediaWorkHome and family

DO NOT OPEN

LOCK_IN_CLAUDE.md

"If you skip ahead and start proposing things before doing steps 1-3, I will end the session and start over."

A real note at the top of my vault, written to Claude. There are 27 copies of it.

Locking in

frankiev2-fix1-fix2-fix3.zip

My Documents folder has 18 folders that start with "frankiev2." Three of them are fix1, fix2 and fix3.

Next to them: test logs named fullsuite through fullsuite7.

Run fullsuite8

Claude CodeCodexObsidianGitHubSupabaseNetlifyRenderBeehiivRemotionCanvaWispr Flow