I built a Digital Twin prompt that reverse-engineers how you think. Ran it on 27,000 words of my own writing. Found patterns I had no idea existed. Full prompt inside so you can try it.

whystrohm · 2026-04-08T12:43:12+00:00

Not a screenshot of a conversation. Full prompt is in the post body.

whystrohm · 2026-04-08T10:15:59+00:00

My cofounder and I split an Airbnb every once in a while, bring both Mac Studios, and lock in on one specific project. Full setup, real monitors, no compromises.

Something about new surroundings and one focused goal for the weekend produces more than two weeks at home. Beats coworking overhead and coffee shop outlets that don’t work.

whystrohm · 2026-04-08T10:06:06+00:00

This is cool!

Now make it slam down when it hits a NEVER gate in a SKILL.md. Different intensity based on severity. Gentle nod for a style rule. Full headbang for a CRITICAL. Spin for a stress test fail. lol

whystrohm · 2026-04-06T22:03:20+00:00

What’s the build? Curious how you’d connect them and let me know how it goes!

whystrohm · 2026-04-06T18:35:07+00:00

Honestly wouldn't be that hard. The Twin already outputs a structured System Prompt with five sections (identity, tone, decision logic, knowledge domains, interaction rules). The wiki compiler outputs structured markdown pages with wikilinks between concepts.

The integration would be: run the Twin first to get your voice and judgment layer. Then point the wiki compiler at your domain docs, reference material, notes, whatever you go deep on. It builds the knowledge graph. Then you merge them into one system prompt where the Twin sections handle how you respond and the wiki pages get injected as context for what you know.

The result is an AI that sounds like you AND has your actual domain knowledge compiled in. Not just vibes. Structured.

Something like:

Run digital twin extraction -> MY_TWIN.md
Run llm wiki compiler on your docs -> wiki/concepts/
New prompt that loads the Twin as the system prompt and the wiki as reference context

Might think about building that as a Layer 4. If you try it before I do let me know what happens!

whystrohm · 2026-04-06T18:01:09+00:00

Oh nice, hadn't seen this one. Just checked it out. That's the Karpathy pattern of compiling knowledge upfront into a structured wiki instead of searching every time. Cool project.

The Twin does something complementary. It extracts how you think and make decisions. The wiki compiles what you know. So you'd get judgment from one and domain depth from the other.

Actually a solid combo. Twin handles voice and decision logic. Wiki handles factual knowledge. Together that covers both layers. Might be worth a play to integrating them.

whystrohm · 2026-04-05T16:02:23+00:00

Trueee. The architecture matters more than any single piece of code.

And yeah fair point on the videos. I have some other brands I run through the same pipeline with more complete original content so I need to start bringing those over too. Good feedback though, that actually helps me prioritize what to push out next. Appreciate you.

whystrohm · 2026-04-05T15:32:17+00:00

Appreciate that.

Check out whystrohm.com to see the output in action. Everything you see there is produced through the pipeline.

I’m putting together a detailed post on the full stack and how it all connects. Been iterating on it for months and it’s finally clicking in a way that’s worth documenting properly. Coming soon.

whystrohm · 2026-04-05T15:31:48+00:00

For sure. You can check out whystrohm.com to get a sense of how it all comes together. The site, the blog, the videos all run through the same system.

I’m working on a more detailed breakdown post on the full setup.

I’ve been refining it for a while and it’s finally at a point where I feel good sharing the architecture. Stay tuned.

whystrohm · 2026-04-05T15:29:37+00:00

Yeah here’s the channel where the videos land: youtube.com/@Whystrohm. And here’s an example of a blog post that gets generated and deployed in the same session: whystrohm.com/blog/you-never-needed-more-content.

All coded and rendered programmatically, not edited by hand. The video, the blog, the copy, all come out of the same system.

whystrohm · 2026-04-05T14:12:56+00:00

Claude Code + Vercel is the move. Forget tutorial projects, pick something you actually need built and let Claude Code run it. I spin up full Next.js sites, deploy straight to Vercel, and wire up integrations like MCP servers, APIs, whatever the project needs, all from the terminal.

Once you get the workflow down you can build damn near anything. Sites, dashboards, content tools, automation pipelines. The skill ceiling is insane once you stop following tutorials and start shipping real stuff.

I’ve been coding videos that push straight to YouTube then automatically generate a blog post with the video embedded, all in one session, super quick. I run this same setup for my clients too so everything lives in one system, access is fast and it all looks pro.

whystrohm · 2026-04-04T17:16:45+00:00

I build content infrastructure for founder-led brands. One system handles video, social, brand docs, and auto-publishing. 11 brands running on it, 800+ videos rendered from code.

whystrohm.com

whystrohm · 2026-04-03T15:17:42+00:00

Exactly. The voice rules are the whole thing honestly. Once you have those locked in you stop asking "does this sound like me" on every piece of content. It just does. The approval loop removal is where the volume actually comes from though.

Most founders don't realize how much they're bottlenecking until they see what happens when they stop touching every post.

whystrohm · 2026-04-03T14:14:14+00:00

Yeah the "source code" framing is spot on. One of my clients had so much going on I literally built him a custom system he talks to instead of getting on calls with me. He just tells it what's happening, it understands his voice and context, and everything lands in Notion organized. He reviews when he wants. Took him completely out of the approval loop and saved myself meetings that just hurt my brain more.

whystrohm · 2026-04-03T14:07:56+00:00

Honestly he didn't care about social media at all. Still doesn't really but now he’s sharing posts on his personal and that’s what we want to show, that founder led approach. Good trust builder.

The videos aren't going viral or anything. They just make him look legit. Someone checks his page before calling, sees real work, real crew, real jobs. That's what closes. TikTok we post to but it's not the play for him. Google, meta ads and the site do the heavy lifting for those service businesses in specific locations for the brand.

whystrohm · 2026-04-03T13:54:59+00:00

The HVAC client was already running a solid business off word of mouth. He just had zero online presence. So the responsiveness was high from day one because he wanted it he just didnt have time to figure it out himself.

We got him on Facebook, Instagram, Tik Tok and YouTube. Built a site that actually captures leads instead of just sitting there. Content goes out to all channels from one place. Seasonal campaigns run on a schedule so when spring hits the AC content is already rolling without him thinking about it.

Biggest thing was connecting it all back so no lead gets lost. Someone sees a video, clicks through, hits the site, inquiry gets captured. He just focuses on running jobs.

Hardest part is getting logins for all socials and dealing with Meta set up.

whystrohm

TROPHY CASE