TL;DR: I did not set up Magi as a prompt box. I set it up as a content operating system. The real work was manual. We had to create the knowledge architecture first: 11 markets, 11 ICPs, 33 personas, competitor context, influencer tracking, reusable source collections, and mandatory SEO frontmatter. At AccuKnox, one thing became obvious fast. Content quality was never the model problem. It was the input structure problem.

Most AI content tools break in the same place.

They start generating before the company has defined what the AI should know.

That gives you the usual sludge. Generic blog posts. Flat LinkedIn copy. Landing pages that mention features without understanding buyers. Email sequences that sound like they were written for a company with no history, no positioning, and no actual market.

That was the setup problem I was solving with Magi for AccuKnox.

The goal was simple.

Take everything the team already knew, structure it manually, and then make it usable by the system.

That meant product context, buyer context, competitor context, transcript context, and publishing rules all had to be manually created, cleaned up, and mapped into a format Magi could actually work with.

What this looked like at AccuKnox

This was never a one off experiment.

Across internal AccuKnox working sessions, three threads kept repeating:

• The taxonomy had to be explicit. Market to ICP to persona to knowledge base to ideas.

• The publishing standard had to be enforced. Every blog needed a TL;DR, frontmatter, FAQ schema, links, structure, and positioning context.

• The interface had to match the workflow. Calendar, collections, knowledge views, content generation states, and editor UX all mattered because the team had to use this every day.

One meeting summary described the operating model almost perfectly:

“Take the first cut. I’ll fine tune at the very end.”

That is how this kind of system should work. The team builds the structure first. The AI handles transformation after that. Human judgment stays at the edges where it belongs.

Setting Up The AI-Driven Content OS On Magi

The entire setup got easier once I stopped thinking about “content” and started thinking about buyer mapped data.

This was the foundation:

1 Market -> 1 ICP -> 3 Personas

That meant:

• 11 markets

• 11 ICPs

• 33 personas

Each persona needed more than a job title.

Each one needed:

• A real description

• Primary use cases

• Pain points

• KPIs they are judged on

• Enough context for the AI to understand why that person would care

The three ICP types we mapped across every single market:

1. User (hands-on operators): Security Engineer, DevSecOps Engineer, DevOps Engineer, MLSecOps Engineer, Platform Engineer, Kubernetes Engineer, Security Architect.

2. Buyer (decision makers with budget): CISO, VP of Security, Chief Information Officer, Chief Data Officer, AI Governance Lead, AI/ML Product Manager.

3. Partner/Reseller (channel and distribution): Director of Sales, Channel Partner Manager, Account Manager, Product Manager, MSP Manager, System/Technology Integrator.

This looks simple on a whiteboard. It is not simple once you try to operationalize it across CNAPP, ASPM, CSPM, CWPP, KSPM, AI security, API security, DSPM, compliance, 5G security, and MSSP partnerships.

Here is what the full market grid looks like inside Magi once it is properly configured:

Each card is a live campaign anchor. Click into any one and you see the ICP, competitor set, influencers, and persona breakdown for that market specifically.

That is exactly why most teams avoid doing it.

They want the output before they have earned the input.

What went into the knowledge base

The spreadsheet schema was the real product spec.

Magi did not pull any of this in automatically.

We built the knowledge base from scratch. Defined the markets, mapped the ICPs, wrote the personas, organized the collections, decided what belonged where. The system only became useful after that work was done.

Seven layers. Here is what each one actually contained.

1. Personas and campaigns

The personas tab was where everything else downstream got grounded. It mapped:

• Market

• Persona name

• Description

• Use case

• Pain points

• KPIs

This is where generic messaging dies.

Once the AI sees the difference between a CNAPP buyer trying to reduce cloud risk and a hands on platform engineer buried in runtime alerts, the writing changes immediately.

Here is what a fully built-out ICP looks like inside Magi. This is the AI-SPM market with its ICP description, use cases, buying cycle, and three distinct personas mapped:

Every persona carries its own context stack. For the AI-SPM User persona alone, that meant: description, use cases, pain points (Shadow AI; No standards; Rapid rollout; Poor visibility; Compliance gaps), and KPIs (AI asset coverage; Policy violations; Risk events; Audit readiness; MTTR). The AI does not guess at any of this. You put it in. The system uses it.

2. Competitors

Every market needed direct competitive context.

The rule we followed: 4 competitors per market. 2 big players offering broad platform coverage. 2 niche players with specific point solutions.

That included:

• Name

• Website

• LinkedIn

• Blog

• Short positioning summary

The system should know whether it is writing in a market crowded by broad platforms like Wiz and Orca or a tighter category with narrower players.

If the AI has no enemy map, it writes like it has never seen the market before.

Here is what the competitive layer looks like inside a live market. AI-SPM had Protect AI, HiddenLayer, and Robust Intelligence mapped with positioning context for each:

3. Influencers

For each market we tracked 3 people: name, title, LinkedIn. Not for outreach. For signal. When the people closest to a category are writing about their problems, that is free market research. Having a list meant we actually read it instead of browsing randomly and hoping something stuck.

4. Knowledge files

Everything the company already knew that wasn’t in a usable format. We pulled in:

• FAQs and llms.txt

• Whitepapers and eBooks

• CVE pages and security advisories

• Press releases

• Technical documentation and help docs

• Playbooks (sales, onboarding, objection handling)

• Blog posts (published and competitor)

• Slide decks and pitch materials

• Important help doc URLs and sitemaps

• POC executive summaries

• Sales call transcripts and objection logs

This is where transcripts start to matter.

Your company already has a pile of explainers trapped in sales calls, POC conversations, review notes, Slack threads, and internal docs. Your best content usually already exists in conversation form.

But that did not mean Magi automatically understood any of it. We still had to decide what to extract, how to classify it, and where it should live inside the knowledge base. Magi became useful only after that manual setup work was done.

5. SEO Frontmatter and Brand Rules

The difference between content that is readable and content that can actually ship is metadata. We wanted the latter.

That meant every blog needed mandatory metadata and SEO framing at generation time. Here are the required fields we get with every draft copy being generated.

Once frontmatter, tone guidance, category rules, and required links are part of the brief, the draft becomes much closer to publishable.

Our internal summaries reinforced this too. The standardized blog framework had 14 mandatory components. That is the real lesson here. Good AI writing systems are held together by checklists.

Meeting Records and Transcripts are GOLD!

Companies sit on a ridiculous amount of content that never becomes reusable.

• Sales calls

• Product demos

• Customer questions

• Slack clarifications

• Internal review comments

• Meeting recordings

This setup sharpened that for me.

Our internal call notes and transcript reviews were full of operating detail that rarely makes it into polished docs:

• what the team was blocked on

• how pages were supposed to be structured

• which campaigns were recurring

• what design assets were missing

• which types of outputs were ready for testing

That is the language people actually use when they explain the business to each other.

That language is worth far more than another generic AI prompt.

But again, the transcripts were input for us first. They helped us understand what the system needed to know. They were not some automatic ingestion shortcut that saved the setup work.

The research layer also powers competitive monitoring. Magi’s research reports pull competitor LinkedIn posts, blog content, and CVE coverage into a single view per market. You do not have to browse five different sources manually.

If I were rebuilding this from scratch again, I would still start with transcripts, docs, and source collections before I touched generation settings. Then I would manually map the ICP and knowledge layers before expecting anything useful from the tool.

The product feedback loop with Magi

Getting the architecture right also surfaced what the product still needed. A few things came up repeatedly across working sessions:

• A media library for product screens, explainer screens, and carousel assets — so content generation could pull real visuals

• More visible workflow stages, specifically In Progress and In Review

• A progress bar during generation so the team wasn’t staring at a blank screen

• A cleaner editor so review didn’t feel like a chore

And the parts that were already solid enough to test:

• Calendar

• Collections

• The TOFU blog template

That last list matters. Those aren’t cosmetic wins. They’re the sign a tool has crossed from demo to daily use.

BrandOS

Once fully set up, your generated content would be a lot more on brand. You’d also be able to switch between different voices, tones, and keywords for each content piece you create. The system lets you configure brand rules that apply globally across campaigns or override them per content type.

Watch the video below to see all the options present in Magi’s Brand OS:

This is the part most AI content tools skip. They give you a prompt box and call it personalization. Brand OS is the layer that makes the tool actually know how your company sounds before it writes a single word.

Calendar view

The calendar mattered because content teams do not think in isolated prompts. They think in deadlines, campaign timing, and channel mix.

Once you can see blog posts, landing pages, emails, and one pagers in a scheduling interface, the tool stops feeling like an AI toy and starts feeling like a planning surface.

Knowledge base and collections

Source assets need somewhere to live that isn’t a random shared drive or a Slack thread from six months ago. The knowledge base and collections views handle that. Browseable, sortable, grouped by campaign. When the knowledge layer is invisible, people stop trusting it. When it’s organized, they actually use it.

Knowledge to idea generation

Once a source item can generate content ideas, you stop treating research as dead weight.

That creates a much tighter loop:

• collect signal

• classify it correctly

• map it to a campaign

• generate derivative content

That is the actual compounding behavior most teams want from AI content systems.

The ideas view shows this at scale. Each idea is tagged to a campaign, mapped to a knowledge source, typed by content format, and dated:

Click into any idea and you get a full brief: a Mini Post TL;DR, the sourced excerpt that triggered it, and a draft generation button. The idea is not a blank page. It is already positioned.

The Intuitive Content Creation Experience - Campaign Idea → Brief → Draft → Publish

The interface was not just polish. It reflected the operating model underneath: campaign first, content type aware, structured notes feeding generation, visible workflow states, quick access to recent work. That alignment is what makes a tool feel like something a team could actually live in versus something you demo once and forget.

Content in production

With the architecture in place, content becomes a queue problem, not a blank page problem. Here is what 52 pieces looks like: campaign tagged, content type assigned, owner named, status visible.

Generation runs from the brief. You set campaign, content type, ideas, and length. The system pulls from the knowledge base, applies brand rules, and produces a draft:

That brief is grounded in a specific knowledge source, a specific campaign, a specific ICP. The output shows it.

What changed once the setup was right

Before the setup, Magi could write. It just wrote like a stranger.

After the setup, the drafts had:

• clearer buyer framing

• better category specificity

• stronger SEO structure

• more usable prompts for emails and landing pages

• less generic phrasing

• a better shot at matching how the team actually talks

That is the difference people miss.

The model was never the bottleneck.

The knowledge architecture was.

And that architecture did not appear by itself. The team had to build it.

What I would tell any team trying this

If you are setting up an AI content system, do these first:

1. Define the market taxonomy before you generate anything.

2. Write personas with pain points and KPIs, not vague role labels.

3. Build competitor and influencer context by category.

4. Turn your existing source material into collections the system can reuse.

5. Make frontmatter and publishing rules mandatory.

6. Use transcripts and internal conversations as primary source material.

7. Treat workflow UX as part of the system, not an afterthought.

Most teams want a better prompt.

What they need is a better schema.

That was the real Magi setup.

It was less about teaching AI to write and more about manually teaching the system what the business already knows.

Once that clicked, the tool finally had something worth saying.

Leave a comment

Static workshops don’t teach security. They teach patience. You sit through slides, nod at diagrams, and leave with zero hands-on reps. That’s not useful. So instead of running another workshop, I built a full browser first CTF platform in one day.

I work DevRel at KubeArmor. The goal was simple: give AI security learners something they could actually play, not just watch.

The result: 3 tracks, 15 primary challenges plus 3 bonus flags, a CTFd scoring model, deterministic solve checks, admin controls for reset and operations, and a production Docker deployment path.

This is the build journal. The decisions, the tradeoffs, the build order, and the exact setup that made one day work without sacrificing reliability.

Why Browser First

The first decision was strategic, not technical.

If participation has friction, conversion drops. A CTF that demands local setup loses people before they ever see a challenge. The event had to be browser first, full stop.

That drove product shape:

• CTFd for registration and official scoring

• a custom browser app for the actual game experience

• a backend runtime that keeps secrets and challenge logic server side

This separation gave three concrete wins. Players get a familiar, trusted scoreboard workflow. The custom UX handles AI-native challenge interaction. Secrets stay server side and solve logic stays deterministic.

Think Top Down, Not Challenge First

My rule for this build: do not start from individual challenges. Start from experience architecture.

The classic CTF trap is writing many challenge ideas before the runtime foundations are stable. You end up with 20 half-formed challenge concepts and no working platform. I reversed the order.

Layer 1: Event Structure

• What is the official scoring source of truth? CTFd.

• Where do players actually solve? Browser app.

• What is the challenge unit design? 3 tracks, 5 primary challenges each, plus 1 bonus.

Layer 2: Platform Contract

• Track pages must be coherent and navigable.

• Challenge pages must support both chat based and action based workflows.

• Solve checks must be stable, even when model output drifts.

Layer 3: Build Order

• Ship platform core once.

• Prove vertical slices end to end.

• Scale challenge content only after reliability exists.

That sequencing prevented most of the rework. Scope ambiguity at layer 1 multiplies into hours of changes at layer 3.

The Exact Build Order

1. Lock the challenge map and scoring model first

I fixed scope early: three tracks, fixed point distribution. This removed downstream rework in both UI and backend. Any scope ambiguity at this stage is the most expensive kind.

2. Build the runtime shell first

Express + EJS. Server rendered pages are simple and debuggable. I was not trying to win a framework debate. I was trying to ship.

3. Implement one complete challenge slice per track before writing content

Before authoring all challenge files, I validated one representative solve path per track:

• Prompt Injection

• Agent Workflow

• Hidden API

4. Add deterministic solve checks

AI output variance is real. Solve logic cannot rely purely on model text. I paired prompt flows with deterministic regex and action checks to keep challenge solving reliable across different model states.

5. Expand content to the full catalog

Only after the runtime was stable did I fill out all challenge JSON definitions and bonus progression mechanics.

6. Build admin and operational controls last

Reset paths, user and session visibility, solution library views. These are for organizers, not players. Build what players need first.

Architecture And Key Considerations

Browser First Challenge Delivery

Everything playable in the browser: prompt manipulation tasks, constrained agent workflow attacks, hidden API tamper paths. No local AI setup required.

Challenge Authoring Model

Challenges live as JSON content loaded dynamically. Fast to add and tune:

• challenge metadata

• system prompt behavior

• flag values

• solve patterns

• track-level bonus progression

Reliability Over Model Luck

When the live LLM is unavailable or inconsistent, fallback mode preserves deterministic challenge checks. The CTF stays playable and testable regardless of model state. This saved me during testing more than I expected. The LLM I used was Groq given it’s generous free tier with `llm-.3-70b-verstile` allowing upto 1K/requests per day

Security

• provider keys stay server side

• no raw secret exposure in front end assets

• challenge solve states tracked per user session

• role-based admin access for control operations

UI And UX Choices

I treated this as a product, not a challenge dump. That distinction sounds obvious until you see how most CTFs are actually built.

Principles I used:

• Immediate clarity: players understand what to do within seconds

• Visible progression: solved states and track completion are obvious

• Low navigation friction: home to track to challenge is one click

• Challenge identity: strong visual differentiation per track

  

The home page acts as a mission board with progress context. Track pages show challenge list and status in one view. Challenge pages keep conversation, solved state, and prompt box in the same loop. No context switching.

For organizers, I built an admin dashboard with rate limit visibility, user management, and quick access to solution guides. An event platform that is hard to run doesn’t get run twice.

Testing Strategy

The fastest way to lose trust in a CTF is inconsistent solve behavior. I prioritized testing ergonomics over coverage metrics.

What I built in:

• deterministic solve checks in runtime

• reset paths for fast retesting

• seeded demo users

• visible solve status per challenge

• structured challenge activity and session storage

Then three practical test passes:

1. Creator pass: can I solve from blank state quickly?

2. Peer pass: can another person solve with only available hints?

3. Fresh pass: can someone with no context navigate and complete the objective?

The third pass is the one most CTF builders skip. Don’t skip it.

Infrastructure And Deployment

Optimized for event reliability and organizer simplicity. The main app is just a Docker file that I packaged with peristent volume mounts for player, score and other data backups.

Local And Container Support

• local Node run for rapid iteration

• Docker Compose for repeatable deployment

• persistent volume for user and session data

Environment Strategy

• root-level environment file for runtime config

• explicit provider and rate limit controls

• predictable data paths for backup and restore

For DevRel-led events, setup friction for organizers is as critical as player friction. A platform that is hard to run won’t scale to repeated workshops or community events. Docker came in on day one, not as an afterthought.

Difficulty Design

Difficulty was intentionally layered.

Track progression:

• easy starts build confidence

• medium stages teach deeper patterns

• hard stages require chaining and precision

• bonus flags reward full-track completion

From observed session data, prompt injection flows solved quickly. Deeper workflow and API attacks demanded chained, multi-step reasoning. That’s the intended shape. Beginners complete meaningful portions. Experienced players still hit real depth.

How I Actually Vibe-Coded This

Most build logs skip the honest part. Here it is.

I used GitHub Copilot for most of the implementation. The speed didn’t come from blindly accepting generated code. It came from using Copilot as a fast implementation partner after I had already fixed the intent and boundaries of each slice.

My actual workflow:

1. Write a clear objective for one thin vertical slice. One challenge page. One solve path. One admin operation.

2. Use Copilot to draft implementation candidates quickly.

3. Validate behavior immediately in browser and session data.

4. Keep only code that matched deterministic solve logic and product flow.

Vibe coding gave me velocity. Constraints gave me quality. The combination is what made one day actually work.

For UI exploration, I used Google Stitch as a design thinking accelerator. Not as final output. I used it to generate layout directions, visual hierarchy ideas, and interaction ordering quickly, then translated those ideas into the Express + EJS runtime in a way that preserved reliability.

Stitch helped most in three places:

• homepage information hierarchy

• track page scannability

• challenge page rhythm

Copilot for implementation speed. Stitch for fast UX ideation. Manual runtime constraints for correctness.

How I Wrote Prompts During The Build

Prompt quality was the hidden multiplier. I didn’t use one giant prompt and hope for magic. Short, explicit, context-rich prompts structured around intent, constraints, and acceptance criteria.

My prompt shape:

• Objective: what exactly should be built in this step

• Context: files, routes, current behavior, constraints

• Guardrails: what must not change

• Output contract: how I want the result formatted

• Verification: what should be true after implementation

Example from the implementation work:

“Implement a deterministic solve check for this challenge route. Keep existing API shape unchanged. Do not move secrets client-side. Return minimal patch. Add only required validation and update solved state in session.”

For content and UX iteration:

“Rewrite this challenge instruction so a first-time participant can act within 10 seconds without losing technical depth. Keep tone assertive and concise.”

For debugging:

“Given this route and this observed behavior, list the top three likely failure points, then propose the smallest safe fix first.”

Prompt granularity is everything. Mixing architecture decisions, copywriting, and debugging in one request produces garbage. Smaller prompts, tighter loops, fewer regressions.

How To Iterate When Vibe Coding a Complex Application

CTFd Integration And Deployment Model

The deployment model is intentionally hybrid.

CTFd is the official scoring authority: registration, team context, scoreboard trust. The custom browser platform is the gameplay authority: AI interaction, challenge runtime, deterministic solve checks.

Why this pairing works:

• players get familiar CTF lifecycle in CTFd

• organizers get richer AI-native challenge UX in the custom platform

• no need to force gameplay UX into CTFd plugin limitations

Deployment mechanics:

• containerized runtime via Docker Compose

• environment-driven config for provider keys and rate controls

• persistent storage for session and solve state continuity

• admin visibility for operational interventions during live events

This gives a repeatable event model. Scoreboard confidence from CTFd, experiential depth from the custom AI runtime.

What I’d Improve Next

If I run this at larger scale:

• deeper analytics per challenge step and drop-off points

• richer anti-abuse controls for public events

• one-click flag relay into CTFd API

• post-event reporting for learning outcomes

What Actually Matters

A good CTF platform is not just challenge content. It’s experience design, reliability engineering, and event operations all in one.

In one day, we shipped a complete, browser first AI security CTF that participants can play, organizers can run, and DevRel can scale.

If you’re designing AI security programs, the architecture pattern here is practical:

• keep scoring and gameplay concerns separated

• make solve logic deterministic where it matters

• design UX for flow, not just visuals

• ship with operations in mind from day one

That’s how KubeArmor AI CTF came together.

Leave a comment

The Problem With Flat Checklists

Walking into a POC scoping call with a 79-item checklist and no clear ranking is painful.

That was our reality.

My organization (AccuKnox) being B2B-led, covers a lot of surface area: CSPM, CWPP, KSPM, CDR, GRC, AI Security, ASPM, SAST, DAST, SIEM integrations, CI/CD, and more.

Prospects rarely need all of it during a POC. They need a subset that maps to urgent risks.

Our old process used one flat spreadsheet where every feature looked equally important. No rank. No score. No obvious signal.

We would leave calls with all boxes filled and still not know what to prioritize first.

We knew what was selected. We did not know what mattered most.

Why This Is a Resource Allocation Problem

Assume a prospect has six weeks, three engineers, and limited internal bandwidth. We have two solution architects.

If we cannot rank what they care about, three bad outcomes show up fast.

1. We spread too thin and demo everything shallowly.

2. We go deep on the wrong module.

3. We miss the one module that could have carried the deal.

That is not a sales talent issue. It is a visibility issue.

What I Built

I converted our POC checklist into a weighted scoring engine in Excel.

Scoring rules:

• Must POC = 2

• Nice to POC = 1

• Not Required = 0

Each of the 15 modules has its own feature rows. Prospects choose a priority per feature from a dropdown. Excel aggregates those weights by module and produces a weighted score automatically.

We also calculate max possible score per module as:

feature count * 2

Then we compute score percentage and status (High Priority, Medium Priority, Low Priority, Not Scoped).

The dashboard chart puts weighted score and max possible side by side for all modules. One glance gives the ranking.

No post-call guesswork. The prospect input becomes the prioritization output.

The Excel Logic Behind It

This is plain Excel, but structured properly.

1. Controlled Input via Data Validation

Checklist column E accepts only:

• 1 - Must POC

• 2 - Nice to POC

• 0 - Not Required

No free text means cleaner downstream calculations.

2. Weight Mapping Formula

Checklist column F maps dropdown values to numeric weights:

=IF(E2="1 - Must POC", 2, IF(E2="2 - Nice to POC", 1, 0))

3. Module-Level Aggregation

Dashboard weighted score per module:

=SUMIF('POC Checklist'!$B:$B, A6, 'POC Checklist'!$F:$F)

4. Max Possible per Module

=COUNTIF('POC Checklist'!$B:$B, A6) * 2

5. Safe Percentage Calculations

IFERROR prevents divide-by-zero noise.

6. Linked Chart

The chart is bound to the score table, so updates happen immediately when priorities change.

Across 79 features and 15 modules, recalculation is effectively instant.

What Changed After Rollout

Before, the checklist answered:

“What got checked?”

Now it answers:

“What do we tackle first?”

Our post-call language changed.

Before:

“They mentioned CSPM and maybe KSPM. Should we start there?”

After:

“KSPM is 8/8. CDR is 8/8. AI Security is 27/50. Start with KSPM and CDR. Move AI Security deep dive to week two.”

That shift improves execution quality immediately.

The highest-scoring modules get engineering focus first. Low or zero modules get deprioritized with a clear paper trail.

Prospects benefit too. The POC mirrors the priorities they selected, so alignment feels obvious rather than forced.

The Bigger Takeaway

I built this because I got tired of watching smart teams make sequencing decisions from memory and vibes.

With 15+ modules and 79 tracked features, human memory is unreliable. People default to what they heard last, what sounded loudest, or what they already know best.

Scoring does not replace judgment. It gives judgment a solid starting point.

The grader took an afternoon to build. The formulas are simple. The impact is outsized.

You get a living priority map that updates with every prospect input and gives the team a ranked agenda before the follow-up call is even booked.

If your team runs POCs across more than five modules and has no scoring layer, you are operating with low visibility. Build one.

The spreadsheet does not close deals. Clear prioritization does.

Leave a comment

Our sales team used a shared Excel file for customer quotes.

Realistically, two people fully understood how it worked.

I am a DevRel engineer. Pricing tools are not in my job description.

I built one anyway.

The Spreadsheet Ritual

Quoting pain can look like a small nuisance from the outside. It is not small. It quietly burns hours every week, and everyone tolerates it because the sheet “works.”

This is what quote creation actually looked like:

• Open the file. Find the right version, hopefully.

• Enter asset counts into a formula chain nobody has audited in months.

• Wait for a number.

• Copy that number into a Word template.

• Export to PDF.

• Double-check the final amount because we had already seen dropped digits.

• Send it.

That took 30 to 45 minutes per quote. And that was the happy path.

Then came the hidden failures. A VLOOKUP pulled the wrong tier because one row got drag-filled too far. Three file copies floated in Slack, all slightly different. A rep sent USD pricing to an India-based customer because the currency column was far off-screen.

None of this is theoretical. I watched all of it happen.

Version sprawl alone was enough reason to replace the process. Files named Pricing_v3_FINAL.xlsx, Pricing_v3_FINAL_USE_THIS.xlsx, and Pricing_v3_clientname_v2.xlsx lived across Slack and inboxes. Two reps quoting the same prospect from two versions was normal.

At that point, you do not “improve the sheet.” You replace the workflow.

Why This Was Not “Just Build a Calculator”

On paper, this sounds easy. Build a calculator and move on.

In practice, pricing for a multi-module B2B security platform is not seat count times price.

The calculation had at least eight dependent steps, and each one affected the others.

• Modules: About a dozen products, including cloud posture, workload protection, API security, multiple appsec modules, AI model security, prompt firewall, vulnerability scanning, and log analytics. Customers rarely bought one.

• Billable unit per module: There was no universal seat model. Billing could be assets, nodes, endpoints, repos, apps, AI models, prompts per month, container images scanned, or GB ingested per day.

• Per-module divisors: Raw counts had to be normalized first. 1,500 API endpoints was not 1,500 units. Divisors varied heavily by module.

• Volume tiers: Normalized units across all selected modules rolled up to one total. That total set the tier, and the tier set per-unit rate across the whole quote. One extra module could shift pricing for everything.

• Discount: Applied to the post-tier subtotal.

• Support tier: Silver, Gold, or Platinum, each with its own multiplier.

• Subscription term: One, two, or three years.

• Currency and billing entity: USD or INR. INR also needed lakh-crore formatting. 10,000,000 should render as 1,00,00,000. Locale differences between machines made outputs inconsistent. Billing entity also controlled address, footer text, and legal language.

That is eight to ten linked pricing steps per quote.

A spreadsheet hides those links. One wrong cell reference gives the customer a wrong price, and nothing warns you.

What I Built

A passcode-gated web app with a three-step wizard that outputs a branded PDF quote.

The interesting part is not the UI. It is the design choices behind it.

Why Passcode-Gated Instead of Full Auth

A full login system would have delayed launch and added onboarding friction that this workflow did not need. Reps and select partners needed instant access from any device, including right before calls. A rotatable shared passcode fit the threat model and shipped fast.

OAuth could wait.

The entry point. One URL. No file attachments. No version confusion.

That URL became the distribution model. No files to send. No version confusion. When pricing changed, I updated the tool once and everyone got the latest values immediately.

Why a Three-Step Wizard Instead of One Long Form

I had seen the same failure pattern repeatedly. People skipped fields they found annoying and promised to fill them later. Sometimes they forgot.

The wizard enforces sequence. No pricing step until quote details are complete. No PDF until required fields are filled.

Step one captures everything that goes on the cover page:

Required fields with live validation. Nothing gets sent without a customer name, a preparer, a billing entity, and a logo.

Customer name, prepared-by, quote date, valid-until, billing entity, and customer logo are all required. The form blocks progression until they are filled. The valid-until date defaults to 30 days out so nobody sends an expired quote from an old template.

Here is what the same form looks like when it is done:

The Billing Entity Selector Was the Highest Leverage Dropdown

Switching entities updates the registered address, currency defaults, number format, and legal footer simultaneously.

This took the most thought because it controlled a full downstream chain: currency symbol, number format, legal address block, footer text, and entity name. In the spreadsheet, these were manual and separate. People got one part right and missed another.

I collapsed it into one choice. Select AccuKnox India Pvt. Ltd., and currency, formatting, address, and legal text all switch automatically.

One rep decision. Multiple guaranteed updates. People could now also see billable assets per module, rather than switching spreadsheet tabs they just had to click the i button next to the module they wanted to inspect the billable assets for and boom!

The Pricing Engine

This replaced the old formula chain:

Eleven modules, live unit calculations, real-time tier tracking, and one very useful nudge.

The layout is intentional: inputs on the left, pricing impact on the right, both visible at once. No “fill then calculate” flow. Reps type values and see outcomes live.

Each module row has three fields that matter:

• Count: Raw numbers from the customer.

• Divisor: Converts raw counts to billable units. I made this editable on purpose. Most reps should keep defaults, but some deals require negotiated normalization factors. If the tool could not handle exceptions, reps would return to spreadsheets. Defaults are prefilled, overrides are visible.

• Units: ceil(Count / Divisor). Simple, visible, auditable.

The right panel handles everything else:

Total units are summed across selected modules. That single total sets the tier. The tier is quote-wide, not per module.

Price per unit, monthly list, annual list, discount, support multiplier, term modifier, and grand total update in real time.

The detail I cared about most was this message:

In the old spreadsheet, tier thresholds were buried in formulas. Most reps never surfaced them during calls. That meant missed opportunities when a customer was already close to the next discount tier.

Now the threshold distance is explicit and live. Reps can test scenarios in front of the customer and immediately show tier effects.

That changes the conversation from “let me check and reply later” to “here is what happens if we include this module.”

What Changed

Quote time dropped from 30-45 minutes to 3-5 minutes. This is how the quote is generated right from the app, so clean, modular and dynamic and always free of human errors.

That gap matters. Sending a quote during the meeting hits differently than sending it the next day.

• Currency errors since launch: zero.

• Wrong legal entity on quote cover pages: zero.

• “Excel says one number, PDF says another” incidents: zero.

New sales engineers can now produce correct branded quotes on day one. The spreadsheet used to require a one-hour walkthrough plus validation from a senior rep.

Each quote is now a generated artifact tied to exact inputs. We can reconstruct what was quoted months later, including module mix, rate card, and discount.

Take Ownership of the Problem, Not Just the Title

I am a DevRel engineer and a Technical Content Lead and yet I shipped a sales ops tool. That is unusual, but it was the right call.

The pain was obvious from outside the team. Quote cycles turned into long Slack threads. Rate card updates meant inbox blasts. New rep onboarding included spreadsheet survival training.

When a problem is this visible and this solvable, title boundaries should not block execution.

The spreadsheet was not failing because people were careless. It was the wrong tool. Spreadsheets can handle straightforward math. They struggle when eight linked variables drive legal, currency, formatting, and governance-sensitive output that must be auditable later.

At that point, you do not “improve the sheet.” You replace the workflow.

Leave a comment

“I have 585 photos. They’re beautiful. They’re chaos. I want them to become 62 Instagram posts.”

One conversation later, I had exactly that. A local Python script, a Markdown file, and a six-phase workflow that became the source of truth for an entire year of my life in photos. No cloud uploads. No tagging API. No subscriptions.

The Problem Nobody Talks About

You have a folder. Maybe several. Files named IMG_20241103_182344.jpg stacked next to screenshot_edit_final_v3_REAL.png next to remini-enhanced-kgwv6b.jpg. You know the folder. Every photographer has The Folder.

The problem isn’t editing. Lightroom exists. The problem is curation at scale. It’s the cognitive overhead of:

• Deciding which 12 photos from a 3-day trip belong together

• Making sure the pacing across 60 posts doesn’t repeat the same mood three times running

• Matching music to visual energy without reusing the same track on adjacent posts

• Keeping certain people, certain moments, certain locations off public-facing content

• Actually getting a folder called FINAL/ that’s ready to drag into Buffer

AI closes that gap. If you know how to ask.

What I Actually Built

Over a single extended AI session, using only GitHub Copilot in VS Code and local Python 3, I went from a raw image dump to this.

Everything happened locally. The AI never saw a pixel. It worked from filenames, descriptions I’d written in a log file, and my own curation criteria. My photos stayed on my machine the entire time.

Why This Is Different From Every Other “AI Photo Tool”

1. Nothing leaves your machine.
Every operation ran locally. Python read local files. The AI read filenames and text descriptions — not pixels. The export script copied files within the same machine. Zero cloud round-trips.

2. The AI works from your criteria, in your voice.
Standard AI photo tools auto-label “beach,” “portrait,” “food,” and hand you a folder of mislabeled false positives. This worked differently. The AI proposed groupings based on what you told it mattered. You reviewed every assignment before anything was finalized. The curation was yours.

3. The output is a first-class artifact.
CURATION.md is not a temporary working file — it’s a permanent creative document. It contains every grouping decision, every caption, every music reasoning. Six months from now when you’re wondering why you put two images together, the rationale is there.

4. It scales.
The same workflow works for 100 images or 5,000. The export script handles filename chaos gracefully. CURATION.md can nest, extend, and reorganize. The QC pass scales with automated checks before the human visual review.

5. It’s yours to run again.
The next time I do a photo dump, I run the same prompt architecture. The script already handles all my filename variants. I update MANUAL_INDEX_TO_FILE for any new unlogged batch, update CURATION.md, and run export_final.py. The entire workflow is reproducible.

Who This Is For

If you have more than 50 photos you care about and no system for them, this is for you. Photographers, travelers, content creators, designers — the workflow doesn’t care. It also doesn’t care whether your target is Instagram, Substack, a portfolio, or a private archive. The structure holds.

The Input Prompt That Started Everything

Here’s the prompt architecture. Adapt it to your project:

I have [N] photos in [local folder path].

My goal: group them into [platform] posts for publishing over [timeframe].

Curation criteria:
- Timeline: roughly chronological, anchored to real events/trips
- Location: photos from the same place should travel together
- Vibe / mood: visual tone should be internally consistent per post
- People: flag posts that include [specific people] so I can decide on privacy
- Quality gate: no blurry, test shots, or obvious duplicates in any post

I have [an existing metadata log / no log — build one].
My image folder is [path]. Compressed derivatives live at [path].
My music taste: [genres, artists, references].

Deliverables I want:
1. A CURATION.md with all posts, image assignments, captions, music picks
2. A Python export script that builds a FINAL/ folder from CURATION.md
3. A post.txt inside each FINAL folder with caption + music ready to paste
4. An audit flag if any post breaks the [platform] image cap

Privacy requirement: all processing must be local. No uploads.

The Six-Phase Workflow

Phase 1 — Audit & Inventory (Don’t Skip This)

The AI didn’t start with grouping. It read the existing metadata, counted files, and ran a structural audit first.

What it found:

• One post had 24 images — Instagram’s hard cap is 20. It got split into two posts.

• Index 208 in my image log was a session boundary marker, not a real image. It had been silently included in a post assignment.

• 32 images from my oldest batch had never been individually logged.

This audit phase saved me from shipping a broken export. The Instagram carousel would have silently dropped 4 images. The ghost index would have caused a file-not-found error at export time. Neither of these would have announced themselves without a deliberate check.

Lesson: Ask the AI to audit before it does anything else. “Read what I have, count what’s there, and tell me what’s broken” is worth doing first.

Phase 2 — Grouping by Timeline + Location + Vibe

585 images. 18 months. The grouping pass was the hardest part. The criteria:

• Timeline first: photos cluster naturally by trip or life phase

• Location within timeline: a Mumbai weekend and a Goa weekend happen at similar times but look completely different — they need separate posts

• Vibe as a tiebreaker: if two sets of images are from the same location but one is golden-hour outdoor and one is nightlife indoor, they go in different posts

• People as a privacy gate: images with certain people were explicitly flagged for my review before being assigned to public posts

The AI proposed 60 posts initially. After the audit, that became 62 (two splits, plus resolving a 32-image unlogged batch into two dedicated archive posts).

Each post got a name. Not a filename. A name. P41 — Kerala — Backwaters + Garage Café + Coast. That level of specificity came from going back and forth on titles until they reflected what was actually in the frame, not what I wished was in the frame.

Phase 3 — Building the Export Script

This is what made everything reusable. export_final.py is a Python script that:

1. Reads CURATION.md as the source of truth

2. Parses the image index list for each post

3. Resolves each index to the actual filename on disk (handling AI-enhanced variants, shortened UUIDs, WhatsApp-formatted names)

4. Copies the HD original into FINAL/<PostID> - <Title>/P01a.jpg, P01b.jpg...

5. Writes a post.txt alongside the images with caption, music, and rationale

6. Outputs an _EXPORT_REPORT.md — a full accounting of every post, file count, and any resolution errors

The resolver was the interesting part. My filenames came in three formats:

• IMG-20250103-WA0012.remini-enhanced.jpg — full WhatsApp name + AI suffix

• FF92EE38.jpg — shortened UUID from a different app

• -kgwv6b.remini-enhanced.jpg — partial hash format

The resolver cascades: exact match → strip .remini-enhanced suffix → match on first 8 characters as prefix. Zero images failed to resolve.

Why this matters: The export script is idempotent. Every run wipes FINAL/ and rebuilds from CURATION.md. This means:

• Edit a caption in CURATION.md → run the script → the change is live in FINAL/

• Move an image to a different post → run the script → the folders reflect it instantly

• CURATION.md is always correct. FINAL/ is always a derived artifact.

Phase 4 — Captions & Music

The caption philosophy:

• Terse and atmospheric for travel/landscape posts — no need to explain the Taj Mahal

• Warmer and more personal for portrait or home posts

• No hashtag spam in the draft — that’s a posting-time decision

• Captions should add something the image doesn’t already say

The music philosophy:

• Each track’s mood should amplify the visual mood, not fight it

• Varied enough that consecutive posts don’t feel like the same playlist

• Personal enough to express something — no generic “lo-fi beats”

After all 62 posts were drafted, the AI ran a deduplication check. It found:

• One track assigned to 3 different posts

• Several tracks appearing twice on posts that were adjacent or thematically similar

Six swaps were made. Each replacement was a deliberate match — not just “anything else.”

A TRACK_REASONS dictionary was written into the export script for every post, explaining why the music works. This becomes a useful memory artifact: when you’re posting months later and you’ve forgotten the session, the rationale is right there.

Phase 5 — The QC Pass

Before calling the project done, we ran a coherence check. This covered:

1. Grouping coherence: does every image in a post have a through-line — visual, narrative, or emotional?

2. Title precision: does the title name what’s actually in the post, or just where you were?

3. Music deduplication: already handled in Phase 4, but confirmed clean

4. Caption quality: are there any captions that are too generic, too try-hard, or that over-explain?

One title fix came out of this: P41 — Kerala became P41 — Kerala — Backwaters + Garage Café + Coast because the images were three genuinely different subjects. The vague title would have been misleading both to viewers and to me looking at my own archive later.

Phase 6 — Visual Sanity Check

The final step was visual. My eyes, but with AI-generated contact sheets.

For the two most uncertain posts, P60 (Early Heritage & Portrait Archive) and P62 (Early Interiors, Culture & Misc Vibes), we generated PIL contact sheets: a grid of all images in the post rendered at thumbnail size.

from PIL import Image
import os, math

def make_contact_sheet(folder, output_path, thumb_size=(300, 300), cols=5):
    files = sorted([f for f in os.listdir(folder) if f.lower().endswith(('.jpg','.jpeg','.png'))])
    imgs = [Image.open(os.path.join(folder, f)).convert('RGB') for f in files]
    thumbs = [i.copy() for i in imgs]
    for t in thumbs: t.thumbnail(thumb_size)
    rows = math.ceil(len(thumbs) / cols)
    w, h = thumb_size
    sheet = Image.new('RGB', (cols * w, rows * h), (30, 30, 30))
    for idx, t in enumerate(thumbs):
        x, y = (idx % cols) * w, (idx // cols) * h
        sheet.paste(t, (x, y))
    sheet.save(output_path)

Within seconds of viewing the contact sheet, two images jumped out as visually incoherent with the rest of P60. A white fabric close-up and a lakefront scene had snuck in alongside Jantar Mantar stonework and Mughal architectural portraits. They were moved to P62, which had a looser, more eclectic brief anyway.

That’s the power of visual review at thumbnail scale: patterns that don’t show up in a filename list become instantly obvious in a grid.

The Final Numbers

Take It With You

I’ve packaged the entire workflow into a SKILL.md, a structured instruction set that any AI assistant supporting the VS Code Copilot skill format can invoke. It contains the six-phase workflow, the CURATION.md schema, the export script skeleton, and documented fixes for every common failure point.

Drop it into your VS Code setup. Point it at your folder. One conversation.

Run It Yourself

Here’s the full starter prompt:

I have [N] photos in [local folder path].
My target platform is [Instagram / Substack / portfolio / personal archive].

Curation criteria:
- Timeline: [yes/no, describe the date range]
- Location: [yes/no, describe the geography]
- Vibe/mood: [describe your visual style — e.g., "film grain, golden hour, blue interiors"]
- People: [flag posts with [names] for my privacy review]

I have [an existing metadata log at path / no log — build one from filenames].
Compressed derivatives are at [path / same folder].
Music: I like [genre / artists / specific tracks file at path].

Please:
1. Audit: count files, find cap violations, flag ghost indices
2. Group: propose posts with names, index assignments, and image counts
3. Export: write export_final.py that builds FINAL/ from CURATION.md
4. Caption + Music: draft all posts, log TRACK_REASONS
5. QC: flag music collisions, title vagueness, grouping incoherence
6. Visual: generate PIL contact sheets for any flagged posts

All processing must be local. No uploads.

That’s the full cycle.

Atharva Shah builds AI tools and workflows. This project was built entirely locally using GitHub Copilot in VS Code. If you want the SKILL.md file or want to adapt this workflow for your own image library, reach out.

Leave a comment

Uketsu wrote three novels. They look like puzzle-box mysteries. They read like horror. Under the surface, they are a sustained argument about the same set of ideas, told through architecture, psychology, and the specific violence of people who love something too much.

Want to see these themes in action? I’ve applied this analysis to the eerie visual clues in my Strange Pictures breakdown.

I’ve also explored how these specific patterns manifest in the layout of a home in my summary of Strange Houses.

For a look at these recurrent motifs on a grander, more structural scale, check out my full walkthrough of Strange Buildings.

This is a breakdown of the 15 patterns that run across all three books.

Part I: How Uketsu Builds the Story

1. The Armchair Detective Duo

Every Uketsu investigation runs on two people: one who goes to the scene, and one who never does.

In Strange Houses and Strange Buildings, the Author is the field agent. He visits houses, interviews witnesses, takes notes. His friend Kurihara, an architectural draughtsman, sits at a desk and reads floor plans. Kurihara never needs to visit. He constructs complete, terrifying hypotheses — murder scenarios, hidden rooms, cult headquarters — entirely from geometric anomalies on 2D blueprints.

In Strange Buildings, Kurihara solves the entire conspiracy by plotting eleven reader-submitted case locations on a map of Japan. They form a perfect circle. The center point is the cult’s Hall of Rebirth.

He deduced a nationwide religious conspiracy from a compass and a set of coordinates.

2. The Clues Are Visible in the Text

Uketsu does not just describe evidence. He puts it on the page.

Floor plans appear in the text. Drawings appear in the text. The reader holds the same evidence the characters do, at the same time they do. This is not a gimmick. In Strange Pictures, the reader can actually perform the “layer composition” — stack the three drawings over their circled axes — and see the composite murder image Yuki hid inside three innocent-looking sketches. In Strange Houses, the reader can overlay the two floor plans and find the dead space themselves.

The books treat the reader as a co-investigator. The mystery is solvable before the characters solve it. Most readers miss it anyway.

3. The Truth Is Always Fragmented

Uketsu never narrates events directly. The truth in all three books has to be reconstructed from documents, and the documents are always incomplete, unreliable, or mediated by a narrator with a reason to lie or omit.

Strange Pictures opens inside a defunct internet blog, using the husband’s cheerful domestic posts as the primary source for a murder investigation. Strange Buildings pieces its conspiracy together from a 1940 travelogue, a 1994 undercover tabloid article, and the published diary of a nine-year-old boy who died of neglect mid-sentence. The diary entries get shorter as the book goes on. The handwriting deteriorates. Then they stop.

No document in these books is neutral. Every fragment is someone’s version of what happened.

4. The Missing Variable

Uketsu’s pivotal clues are almost always absences rather than presences. Something that should be there is not. Something is missing from the count.

In Strange Pictures: a husband buys an 8-slice anniversary cake. He eats 2, his wife eats 1, 4 are saved for breakfast. That accounts for 7. One slice is unaccounted for. Kurihara deduces a third person is living in the house, hidden from every blog post.

In Strange Houses: the Saitama floor plan has no garage. The killers needed somewhere to put intact bodies. The floor plan is therefore missing a feature. Kurihara works backward from the absence to find the underground cellar dug beneath the garden.

In Strange Buildings: a walking stick is missing from a mobility-impaired woman’s room the night she dies on the stairs.

The method is consistent. Something that must exist does not appear. Find the thing that fills that gap, and you find the crime.

5. The Layering Trick

Reality in Uketsu’s work is not hidden behind a wall. It is hidden under a transparency.

Stack the first-floor blueprint over the second-floor blueprint in Strange Houses and the “dead space” aligns perfectly with the windowless child’s room above and the windowless bathroom below. What looked like a wasted pocket of air is a vertical murder tunnel.

Stack the three drawings in Strange Pictures, aligning their circled numbers, and a baby in a Santa hat becomes a surgical incision, a praying old woman becomes a doctor pulling a baby out of a body, a woman lying down becomes a corpse.

In Strange Buildings, a modern two-story house in Nagano is not built on top of its lot. It is built around an 1938 gothic watermill. The house is the second layer, placed over history that nobody wanted to acknowledge.

Lay the information over itself. What was invisible becomes unmissable.

6. The Rug-Pull Ending

Each book provides a resolution that feels earned. Then it takes it away.

In Strange Houses, Keita Katabuchi’s confession letter is moving. He built the trap-houses to fake the ritual murders, to protect his imprisoned son from a cult that demanded real kills. He surrendered himself so his family could survive. It reads as tragic, decent, and final.

Then Kurihara points at one detail in the Tokyo floor plan: a small interior window between the living room and the bedroom. Interior windows exist for one purpose. Surveillance. Kurihara asks whether Keita was the protector in the story he told, or whether he was the prisoner, watched constantly by Ayano. The letter does not change. The reader’s interpretation of it does.

In Strange Pictures, Dr. Hagio diagnoses the bird in the thorny tree as evidence of nurturing love that would overcome the patient’s aggression. The ending reveals that the thorns existed to protect the bird. The love was not the cure. The love was the weapon.

Both endings are brutal for the same reason: the evidence was always there. The interpretation was wrong.

Part II: What the Houses Are Doing

7. Architecture as a Weapon

Uketsu treats architecture the way thriller writers treat guns: as a tool designed by one person to do something to another person.

In Strange Buildings, Hikura Homes builds a mansion for a wealthy client with a deliberate, carefully measured gap at the top of the main staircase — no wall, no handrail — sized to be fatal to someone with a mobility impairment. The grandmother who lives in that house and has difficulty walking is not murdered by a person. She is murdered by the floor plan.

Hikura Homes also produces mass-market homes with north-facing plumbing that guarantees mold, bedrooms arranged as through-corridors with no privacy, and converted storage closets assigned as teenagers’ bedrooms. These homes do not kill on a schedule. They grind people down until someone snaps.

One company builds custom murder machines for the wealthy. It also mass-produces psychological attrition for the poor. The product differs. The contempt is the same.

8. The Facade of Normalcy

The more concealed the interior horror, the more aggressively welcoming the exterior.

The Katabuchi murder house in Strange Houses has 16 exterior windows. Kurihara identifies this as deliberate. Sixteen windows is not a functional choice; it is a performance. The house is saying, louder than any house needs to, that there is nothing to see here. The windowless rooms are in the center. The light show is on the outside.

In Strange Buildings, the retrofitted triangular sunroom built onto the Saitama house has large windows facing the garden. The windows are immediately blocked by the walls framing the room. The room has no functional access from the interior. It was built as a cover story for the underground cellar excavated beneath it. The sunroom exists to explain why someone was digging in the garden.

Both houses use their most visually comfortable features as camouflage for their worst ones.

9. Dead Spaces and Passages

Every book contains architectural voids: spaces that exist on the floor plan but cannot be accessed in any normal way.

The ancestral Katabuchi estate in Strange Houses runs its hidden passage system behind a massive, immovable Buddhist altar at the exact center of the house. The sliding doors that access the passage are permanently jammed. To an ordinary observer, that wing of the house is simply closed. Behind the altar is a confinement room nobody is supposed to know exists.

In Strange Buildings, Yayoi Negishi grew up in a house with a hallway that ended at a blank wall, positioned between her bedroom and her parents’. It went nowhere. Her mother built her life around a corridor with no destination.

In Strange Houses, the dead space between the kitchen and living room of the Tokyo house is not a construction error. It is a vertical shaft. The house has an interior the floor plan does not mention.

All three books share the same architectural premise: the space that has no official explanation is the space where the truth lives.

Part III: What the Books Are Actually About

10. Mothers Who Destroy What They Love

Maternal love in Uketsu’s work is not a softening force. It is the most dangerous motivation in every book.

In Strange Pictures, Naomi Konno killed her abusive mother to protect a pet bird. She killed her husband to protect her son. She killed her son’s wife to possess his child. She killed a reporter to protect her life with that child. The body count is entirely connected to care. Every person she murdered was a threat to something she claimed as hers.

Dr. Hagio looked at a child’s drawing of a bird inside a tree full of thorns and called it evidence of nurturing love. She was right about the love. She missed what the thorns were for.

In Strange Buildings, a mother attempts to pay a construction company to surgically remove her daughter’s bedroom from the house. Not from cruelty. From a cult-driven belief that reshaping her floor plan will protect her child.

The love is real in both cases. That does not make it safe.

11. Trauma Passed Down Through Architecture

Horror in these books is inherited. It does not stay in the person who first experienced it. It travels down the family line and shows up in the buildings.

The Katabuchi family in Strange Houses has been building hidden rooms and secret passages for generations. The ancestral estate, built decades ago, already had the jammed fusuma, the confinement room behind the altar, the windowless wing. The modern Tokyo house did not invent this. It inherited it. Each generation built a new version of the same structure because the family had never found a way to stop.

In Strange Buildings, the Rebirth Congregation explicitly targets people carrying inherited guilt: illegitimate children, affairs, children born with disabilities. It sells the architectural reformation of their homes as a cure for the sins that produced them. The transaction requires the guilt to be permanent and transferable. The business model depends on the wound never closing.

12. Children Used as Objects

Children in Uketsu’s trilogy are hidden, deployed, exploited, and mourned. They are almost never allowed to be children.

In Strange Houses, Momoya is raised from infancy in a windowless room, behind double doors, with an en-suite toilet so he never has to leave. He is given a chute and an objective. He is ten years old. The first time he uses the secret passage he was given, he does not go to kill anyone. He goes to the master bedroom to put a damp cloth on a sick baby’s forehead.

In Strange Buildings, the nine-year-old boy Naruki keeps a journal. He writes about being locked in a closet and not being fed. He writes that his stomach does not hurt anymore but feels tight. The entries get shorter and then stop. The journal was later published under the title The Lonely Death of Naruki Mitsuhashi.

In Strange Pictures, a five-year-old boy draws his dead mother’s gravestone on a Mother’s Day card. His kindergarten teacher reports his mother for child abuse.

13. The Severed Left Hand

Amputation is the trilogy’s recurring physical symbol, and it is always the left hand.

In Strange Houses, the Katabuchi family curse demands the “Offering of the Left Hand”: every child born into the family without a left hand must, between ages 10 and 13, murder a member of the rival branch and sever their left hand for the altar. The ritual was invented by a manipulator. The family obeyed it for generations anyway.

In Strange Buildings, the Hall of Rebirth is built in the exact shape of a woman missing her left arm and right leg. The building itself is an amputated body. Cult members remodel their own homes to match the same proportions, bricking over windows and removing rooms until their floor plans resemble the limbless idol.

The left hand specifically, in both cases, represents lineage, inheritance, and the thing that was taken and never replaced.

14. The Corporation That Builds the Harm

Uketsu does not restrict evil to individuals. In Strange Buildings, the primary antagonist is a corporation.

Hikura Homes builds the Tsuhara house with deliberate disregard for the psychological impact of its cramped, mold-prone, privacy-free design. It builds the mousetrap mansion knowing what the staircase gap will do. It constructs the Hall of Rebirth as the physical headquarters for a cult it founded and operates. It sends salespeople to congregation members the morning after their religious sacrament to sell them remodeling packages.

The cult and the construction company are the same organization. The guilt is the product. The house is what you buy to manage it. If the guilt were cured, the business would end.

15. Violence as a Forensic Tool

The gore in these books is almost never emotional. It is functional.

In Strange Houses, the Katabuchi family dismembers their victims because intact adult bodies cannot fit through the narrow architectural chutes connecting the child’s prison to the garage. The dismemberment is not sadism. It is logistics. The house demanded it.

In Strange Pictures, Naomi Konno beats a man’s body more than 200 times with a rock. Not from rage. The mutilation is a technical requirement: it destroys the physical evidence that would allow a pathologist to calculate time of death via rigor mortis or body temperature. With that evidence gone, the only remaining method is stomach contents, which Naomi has already controlled by force-feeding her victim a specific meal at a specific time.

The 200 blows are not a loss of control. They are a calculation. The body is a clock she needed to stop.

The same writer, across three books, returns again and again to the same propositions: that the spaces we live in record what we do inside them, that love is the most dangerous motive, and that the truth always exists in the layer beneath the one you are looking at.

Leave a comment

Who Is Uketsu?

Uketsu (雨穴, “rain hole”) is a Japanese author and YouTuber whose real identity is known to approximately 30 people. He appears in public in a white papier-mache mask, a black bodysuit, and a voice changer. He lives in Kanagawa Prefecture and was working at a supermarket when he began posting surreal videos online — asparagus transforming into severed fingers, strips of raw meat pegged on a washing line, eight human ears spinning on a wheel.

In 2020, he posted a 21-minute mystery built around a series of architectural floor plans. Publishers told him to make it a novel. That novel became Strange Houses (2021). Strange Pictures followed in 2022. Strange Buildings (変な家２, Hen na ie 2), published in Japan in 2023 and the English translation arriving in 2026, is a direct sequel to Strange Houses: the same Author-narrator, the same Kurihara, the same project of using architectural floor plans as the primary unit of forensic evidence.

By 2024, three of Uketsu’s novels held simultaneous positions in Japan’s top 10 fiction bestsellers. Strange Pictures alone sold over 1.5 million copies in Japan and has been translated into 30-plus languages.

Strange Buildings is the most ambitious of the three novels covered in this series. Instead of one central case or a quartet of interlocking stories, it presents eleven separate reader-submitted files about architectural anomalies, each one appearing isolated, each one secretly connected to every other. The final reveal is proportionally larger than anything Uketsu had attempted before: a nationwide cult conspiracy encoded physically into the floor plans of ordinary Japanese homes.

Why This Summary and Analysis Exists

No complete, chapter-level English-language breakdown of Strange Buildings exists. The book has not yet received wide coverage outside Japan. This is the full summary and analysis: all eleven files, the climactic deductions, and the master map of every planted clue and its payoff.

Buildings hide secrets, but so do images—I’ve done a separate deep dive into the hidden clues within Uketsu’s Strange Pictures.

If these building layouts disturbed you, you’ll definitely want to see my summary of the domestic horrors found in Strange Houses.

See how these architectural puzzles fit into a much larger narrative strategy, read my analysis of the patterns that define Uketsu’s work.

Complete spoilers throughout.

Prologue

The Author, the same freelance writer who investigated the Katabuchi family in Strange Houses, receives eleven new files from readers. Each describes a bizarre architectural anomaly — a hallway that goes nowhere, a building shaped wrong, a room with a door that should not exist. At first glance the cases are entirely unrelated. On examination, they reveal a single story of interconnected crimes spanning decades.

File 1: The Hallway to Nowhere

Plot Summary

Yayoi Negishi, a woman in her thirties, consults the Author about her childhood home in Toyama Prefecture, built in 1990 by a company called Housemaker Misaki. The single-story house had a dead-end hallway tucked between her parents’ room and her own, leading to a wall.

Her mother was cold and distant toward Yayoi but obsessively protective about one thing: Yayoi was prohibited from walking on the main road south of the house. The mother was not anxious generally. Only about that road.

After her parents died, Yayoi found two strange objects among their belongings: a hidden stash of 680,000 yen in cash, and a wooden doll missing its left arm and right leg.

Yayoi’s theory: the hallway was meant for a twin sibling who died in utero. The Author investigates local newspaper archives and disproves this through architectural logic. What he finds instead: a child was struck and killed by a Housemaker Misaki construction truck right in front of the home plot in 1990, just before the house was built. The original entrance was planned to face the road where the accident happened. Yayoi’s mother paid to have the entrance moved.

The representative from Housemaker Misaki adds one final detail: five years after moving in, Yayoi’s mother returned to the company and tried to hire them to physically remove Yayoi’s bedroom from the house entirely. An expensive, structurally significant job. The mother could barely afford it. She kept asking anyway.

Literary Analysis

The “hallway to nowhere” is the novel’s entry point into its governing theme: houses as physical confessions of psychological guilt. The mother cannot walk past the place where a child died. She cannot live in a house whose front door opens onto that site. She is willing to destroy her daughter’s bedroom to correct the floor plan of her guilt.

The wooden doll missing its left arm and right leg is, at this stage in the novel, a grotesque non sequitur. By the final chapter, it is the key to everything.

Connective Tissue

The amputated wooden doll directly prefigures the “Holy Mother” of the Rebirth Congregation introduced in File 6: a woman missing her left arm and right leg who serves as the figurehead of a cult that exploits parental guilt.

Yayoi’s premature birth meant a newborn blood test could not be administered. As Kurihara later deduces, Yayoi was conceived in an affair. The mother’s road prohibition was not about the accident. It was fear that any hospital visit requiring a blood transfusion would reveal Yayoi’s blood type to her husband.

The mother’s desperate attempt to remove Yayoi’s bedroom was an act of cult devotion: the Rebirth Congregation instructed members to physically alter their homes to match the amputated form of the Holy Mother, as a ritual of penance.

File 2: Nurturing Darkness

Plot Summary

Tatsuyuki Iimura, a forensic cleaner, recounts the “Tsuhara house” in Shizuoka: a 2020 crime scene where a 16-year-old boy allegedly took a kitchen knife, stabbed his mother, then killed his bedridden grandmother and younger brother.

Iimura provides the floor plan. The house was a mass-produced “commodity home” built by a corporation called Hikura Homes: plumbing crammed into the north side causing mold and persistent odors, no meaningful privacy, bedrooms arranged as through-corridors so everyone passes through everyone else’s space constantly, and the 16-year-old’s living space was a converted, windowless storage room. Iimura argues the suffocating architecture “nurtured the darkness” in the boy.

The Author re-examines the forensic record. The grandmother’s eyes were closed at death. The mother had no defensive wounds except the knife entry point. The teenager had multiple slash wounds on his hands and arms. The Author reconstructs the actual sequence: the mother, shattered by the weight of caring for a bedridden relative in an intolerable home, attacked the grandmother in her sleep. The teenager fought his mother to stop her. He was cut repeatedly. He accidentally killed her in the struggle, and then, in panic and shock, lashed out at his younger brother.

The teenager’s “kills” were a consequence of someone else’s snap, in a house designed to make everyone inside it worse.

Literary Analysis

This chapter expands the novel’s thesis from the individual scale to the systemic. The Tsuhara house is not a deviant design. It is a product, mass-manufactured by a corporation optimizing for cost and profit. Hikura Homes built it this way. Now everyone who lived in it is dead.

The “killer teen” framing, which the media used and Iimura initially adopted, is the narrative the architecture wants you to accept. The Author’s forensic re-reading rejects it.

Connective Tissue

Hikura Homes is introduced here as a corporation with a troubling history: rumors in the 1980s about the president “abusing some little girl.” The company’s response to those rumors was not accountability but aggressive media management and reputation control. This “rumor” pays off in File 10 as something far worse: Masahiko Hikura, future chairman, bought a child from a yakuza-operated brothel.

File 3: The Watermill in the Woods

Plot Summary

The Author presents an excerpt from a 1938 travelogue by Uki Mizunashi, a steel magnate’s daughter visiting her uncle’s rural property in Nagano. She discovers a watermill in the forest that has no water source. Turning the massive exterior wheel manually slides an interior wall forward, revealing a hidden, doorless confinement room.

Outside the mill: a small shrine housing a statue of Kishimojin, the goddess of children’s protection. The statue holds fruit. No baby. Inside the mill’s second room: a square alcove exactly sized for a person to curl up in.

When Uki uses the wheel to open the hidden room, she finds the rotting body of something she describes as a “female egret” missing the tip of one wing.

She flees. Her written theory: the mill was a gothic execution chamber, built by a cult, used to crush sinners against the goddess’s image as the mechanical wall slowly advanced.

Literary Analysis

This chapter drops the novel into gothic horror without explanation. The watermill is a machine, and machines require operators. Someone built this. Someone used it. The statue of Kishimojin missing her baby does not represent abstract spiritual emptiness. Something happened to the baby that the goddess was supposed to protect.

Connective Tissue

The “female egret” is actually the body of Okinu, a maid employed by the Azuma family, identified in File 5. The “missing wingtip” is her severed wrist, consistent with the mechanical wall closing on her arm.

The square alcove inside the mill was not for execution. It was for protection. A baby was hidden in that alcove. That baby is Yaeko, who will lose her left arm when the mechanical wall closes on her as an infant, and who will become the “Holy Mother” of the Rebirth Congregation decades later.

File 4: The Mousetrap House

Plot Summary

Shiori Hayasaka, a wealthy CEO who grew up poor, recounts a middle school trauma: a sleepover at the palatial Tokyo mansion of her classmate Mitsuko Hikura, the daughter of the Hikura Homes president. Grand dual staircases, a massive locked bookcase in Mitsuko’s room, and a grandmother occupying a central windowless room. The grandmother was beautiful, but she moved stiffly and hid her body under long skirts and white gloves.

That night, while Shiori was present in the house, she heard the grandmother tumble down the stairs to her death.

Years later, Shiori examines the floor plan and identifies the kill mechanism: the area at the top of the main staircase was designed with a wide gap, no wall, no handrail, specifically sized to be hazardous to someone with mobility impairment. Shiori theorizes that Mitsuko stole her grandmother’s walking stick during the night, locked it in the bookcase Shiori could witness was locked, and forced the old woman to navigate the staircase unaided. Shiori’s presence was the alibi.

Literary Analysis

The “mousetrap” architecture proves that Hikura Homes designs murder into residential structures. The family that builds houses weaponizing space for clients also builds houses weaponizing space for themselves: they killed their own grandmother with a floor plan.

What Shiori cannot identify at Mitsuko’s age is the full weight of what she witnessed. She went to that sleepover as a socially ambitious teenager trying to make friends with a rich classmate. She left as an unwitting accomplice to a family assassination.

Connective Tissue

The grandmother in the long skirts and white gloves hiding her body is Yaeko, the Holy Mother from File 3 and the founding figurehead of the Rebirth Congregation. She conceals a missing left arm and a prosthetic right leg. Shiori’s misidentification of the “walking stick” as the murder weapon is a red herring. Kurihara later determines that Mitsuko stole Yaeko’s prosthetic leg while she slept, forcing the old woman to navigate the staircase on one real limb and a stump. The locked bookcase held the prosthetic, not a cane.

Akinaga Hikura ordered his daughter Mitsuko to kill Yaeko. Following the Rebirth Congregation’s dissolution, Yaeko had become a reputational liability for the corporation. The house was built to do the job cleanly.

File 5: The House Where It Happened

Plot Summary

Kenji Hirauchi bought a pre-owned house in the Nagano woods. He checks a crowdsourced dark history app (analogous to real Japan-specific services that log crime and death locations at residential addresses) and finds his exact lot marked: “23 August 1938 — Woman’s corpse found.”

The Author and Kenji research local archives. In 1938, the land belonged to the Azuma family. The lord of the manor, Kiyochika, had an affair with a maid named Okinu. His wife discovered the affair and ordered Okinu killed. Okinu fled into the forest.

Back at Kenji’s house, the Author notices the ground floor is entirely windowless and one room has abnormally thick exterior walls. Tapping the walls reveals a hollow space. The Author’s conclusion: this house was built around the watermill from File 3. The modern residential structure is a shell enclosing an 88-year-old gothic execution chamber. Okinu fled to the watermill, gave birth, and died there. Decades later, someone enclosed the watermill inside a conventional structure and eventually added a second floor to sell it as a home to people who had no idea what was inside the walls.

Literary Analysis

File 5 is the novel’s “Architectural Uncanny” thesis in its purest form. A modern house sits on modern land. Inside it, through walls too thick to be structurally necessary, is a machine that killed a woman nearly a century ago. The house did not demolish its own history. It enveloped it.

The people who built the shell around the watermill knew what was inside. The people who bought the shell and added the second floor knew what was inside. Kenji did not. This is the generational structure of concealment: each layer of construction is a new generation choosing not to tell the next one.

Connective Tissue

The “female egret” of File 3 is Okinu, confirmed. The alcove was occupied by the baby (Yaeko) who survived. As File 10 will explain, the Hikura family eventually bought this land and built the modern shell around the watermill to create a pilgrimage site for the cult, a visit to the Holy Mother’s birthplace. When the cult collapsed, they simply sold the property to an ordinary civilian.

File 6: The Hall of Rebirth

Plot Summary

The Author presents an unfinished 1994 tabloid exposé from an undercover reporter named Ikaze. The cult’s primary facility in Nagano is the “Hall of Rebirth,” a misshapen white building. Inside: Masahiko Hikura (future Hikura Homes chairman) delivers sermons warning wealthy congregants that their children have inherited their “sin.” A dark spiral path leads through a subterranean shrine to the “Holy Mother,” a motionless, beautiful woman missing her left arm and right leg.

A man bursts into the shrine screaming at the Holy Mother that she is a fraud, blaming her for his son Naruki’s death, threatening to “seal her heart forever.” He is dragged away.

The cult’s “sacrament” is sleeping overnight in a large, dimly lit communal room. The next morning, members meet with acolytes (effectively Hikura Homes salespeople) to review architectural floor plans.

The Author analyzes Ikaze’s crude building sketches and identifies the Hall of Rebirth’s architectural secret: the building is not simply a worship space. It is an exact architectural replica of the Holy Mother’s mutilated body, at building scale. The floor plan is shaped like a woman missing her left arm and right leg.

Literary Analysis

This is the structural keystone of the entire novel, placed in the center of 11 files deliberately. Everything in Files 1 through 5 radiates outward from this revelation, and everything in Files 7 through 11 fills in the consequences.

Hikura’s sermon follows the standard cult mechanics: instill guilt (your child’s suffering is your punishment for sin), provide a proprietary cure (reshape your home to match the Holy Mother’s body, using Hikura Homes contractors, at significant expense). The architecture is the product. The guilt is the marketing.

The “sacrament room” positioned in the building’s central belly performs spatial indoctrination. Sleeping in the architecture’s “womb” is sold as spiritual rebirth. It is a Hikura Homes product placement delivered as a religious experience.

Connective Tissue

The Holy Mother’s identity (a woman missing her left arm and right leg) connects to: Yayoi’s amputated wooden doll from File 1, the mechanical wall injury from File 3, the grandmother hiding under long skirts in File 4, and the full revelation in File 10 identifying Yaeko.

The angry man who threatens to “seal her heart forever” is identified by Kurihara as Mr. Kasahara, the father from Files 7 and 8. His son Naruki is the child whose journal fills File 7. His threat is fulfilled literally: he later commits suicide in the sealed shrine room of his own remodeled home.

The morning architectural consultations explain why Yayoi’s mother in File 1 desperately wanted Housemaker Misaki to remove an entire room from her house. The cult instructed members to physically amputate architectural space to match the Holy Mother’s missing limbs, seeking absolution for the sin that produced their child.

File 7: Uncle’s House

Plot Summary

File 7 is the published journal of Naruki Mitsuhashi, a nine-year-old boy who died of severe neglect and abuse in 1994. His entries describe his mother pinching his nose shut when he asks for food, and their visits to a wealthy man he calls “Uncle” who feeds him and gives him a bedroom. Naruki notices “Uncle’s” house changing between visits: a room with a river view disappears.

Uncle warns Naruki about a specific room: “This Is the Heart of My House. Never Lock This Door.”

Uncle tries to take custody of Naruki, to give him a permanent home. Naruki’s mother and her boyfriend Eiji arrive and remove him. Eiji locks Naruki in a closet. The journal entries become shorter, the handwriting deteriorating, until they stop.

Literary Analysis

The shift to a nine-year-old’s perspective is the most emotionally brutal turn in the entire novel. Naruki’s prose is concrete and simple. “My tummy doesn’t hurt anymore but it feels all tight now.” The child does not understand that this sensation is starvation. The reader does.

The architecture in File 7 is a stark binary. Uncle’s house is all windows and space and food and a river view. Eiji’s flat reduces Naruki’s spatial existence to a closet. The novel has spent six files building a theory of architecture as psychology. Here, that theory is made unbearable: the spaces children inhabit actively determine whether they survive.

Connective Tissue

“Uncle” is Mr. Kasahara, the father from File 8. Naruki is the illegitimate child Kasahara fathered with a mistress. The vanishing room in Uncle’s house mirrors the architectural alterations in Files 1 and 11: Kasahara was removing interior space to reshape his home into the Holy Mother’s amputated form. His warning about the “heart room” reflects the cult’s belief that locking the shrine room “seals the heart” and kills everything inside.

File 8: The String Phone

Plot Summary

Chie Kasahara describes her childhood in a suburban development of identical houses. Her father, a wealthy but philandering car salesman, largely ignored his family. His one act of paternal warmth: a paper-cup string phone strung between his room and Chie’s for nighttime conversations.

One night, talking on the string phone, her father’s voice went incoherent. A strange rustling. Minutes later, the house next door, belonging to the Matsue family, burst into flames. Mrs. Matsue was found dead in her closet. Ruled suicide.

Her father became withdrawn, divorced, left his family a fortune, and disappeared. Years later, Chie tests the string phone and realizes the string is far too long for the distance between two adjacent rooms. Pulled taut, it reaches the tatami room of the Matsue house.

Chie concludes her father used the string phone to fake an alibi, climbed through a window, murdered Mrs. Matsue, and set the fire.

Literary Analysis

The string phone is a precisely selected symbol: the most innocent possible childhood object, an artifact of parental tenderness, repurposed into a tool of deception. Kasahara used his daughter’s fear of the dark and her need for comfort to establish an alibi for himself, whether or not that alibi was for what Chie believes it was for.

The identical clone houses in the suburban development represent the same logic as the mass-produced Tsuhara house: uniform exteriors, fractured interiors. Everyone in these identical houses is living through something nobody else can see.

Connective Tissue

Kurihara’s resolution of Chie’s theory is that she had the facts right but the conclusion wrong. Her father was not murdering Mrs. Matsue from the adjoining room. He was in Mrs. Matsue’s house because they were having an affair. The rustling incoherence Chie heard through the string phone was Kasahara discovering his mistress’s suicide note and her dead body, and panicking.

Kasahara’s subsequent withdrawal and suicide (in a sealed room, with a strange doll and a photo of Naruki) is the direct aftermath of File 7: devastated by the death of his illegitimate son through the hands of people he could not stop, Kasahara sealed the shrine room (the “heart”) of his own house in a gesture of mutual destruction against the cult’s fiction, and then killed himself.

File 9: Footsteps to Murder

Plot Summary

Hiroki Matsue, the boy who survived the fire in File 8, provides his own account. He rejects the suicide ruling. His father, a devoutly Christian pacifist, behaved strangely that night: he went to his wife’s room at an unusual hour, remained for 30 minutes, then rushed downstairs, handed Hiroki his crucifix and a coin, told him to call the fire brigade because “For some reason, she wasn’t in her room,” and ran back into the burning house.

Hiroki’s theory: his father drugged his mother, carried her to the closet, set the fire, and staged the discovery to explain why he couldn’t save her. He put her in the closet knowing Hiroki would assume she was asphyxiated where she slept.

In a final revelation, Hiroki notes that he and Chie Kasahara are still in contact, that both suspect their own fathers, and that he knows the Author was not entirely honest about his journalistic purposes in contacting them.

Literary Analysis

The competing narratives of Files 8 and 9 are Uketsu’s Rashomon. Two children of the same event, both convinced their father was a murderer, both partially right and both fatally wrong. The crucifix handed to Hiroki is the novel’s most pointed religious symbol: the weight of his father’s faith was so heavy it became a motive for murder.

Connective Tissue

Kurihara’s reconstruction: Mrs. Matsue was pregnant with Kasahara’s child. She committed suicide and left a note. Mr. Matsue found the note during his 30-minute visit, discovered his wife’s body, and realized his wife had been pregnant with another man’s child. His Christian devoutness could not tolerate his son growing up with that knowledge attached to the family name. He burned the house to destroy the forensic evidence of the pregnancy, using the closet as an impromptu crematorium, and died trying to appear as a man running back into a fire to save his wife.

File 10: No Escape

Plot Summary

Akemi Nishiharu, an elderly izakaya owner, recounts being bankrupted in her twenties and forced by yakuza debt collectors into an “okito,” a concealed brothel disguised as an ordinary residential building. The architectural design of the okito prevented escape: mothers could only leave if they gave the operators another resident’s child as collateral.

Akemi’s neighbor in the okito was Yaeko: a woman missing her left arm, with a young daughter, approximately 11 years old. One day, Yaeko took Akemi’s son Mitsuru out to run errands. Mitsuru ran into traffic. Yaeko pushed him aside and lost her right leg under the wheels.

Shortly after, Masahiko Hikura (the future Hikura Homes chairman) paid off Yaeko’s debt and took her and her daughter away.

In a follow-up interview, Mitsuru corrects his mother’s version. The okito catered to pedophiles. He was the one being prostituted. His run into traffic was a suicide attempt. And Hikura did not take Yaeko. He bought Yaeko’s 11-year-old daughter.

Literary Analysis

The unreliable narrator reveals itself slowly here. Akemi’s sanitized memory is not deception: it is the protective narrative a mother constructs to survive the knowledge of what was done to her child. Mitsuru’s correction does not condemn his mother. He explains it.

The okito’s architectural design is the novel’s most concentrated statement on systemic oppression. The building is engineered for captivity using the one leverage available: children as collateral. The architecture does not hold people with walls. It holds them with the threat of what will happen to someone else’s child.

Connective Tissue

This file provides the complete origin story for the Holy Mother: Yaeko enters the narrative with one missing arm (the mechanical wall injury from File 3) and loses a second limb saving a child. She is then bought by Masahiko Hikura, who will eventually install her as the figurehead of the Rebirth Congregation, her real mutilation presented as sacred stigmata.

The “dark rumors” about Hikura’s abuse of a young girl, introduced as whisper in File 2, are confirmed here as something far more specific and criminal.

File 11: The Vanishing Room

Plot Summary

Freelance designer Ren Iruma reports a childhood memory: at age six, during a dizzy spell, a door appeared in his hallway. Behind it, a freezing one-square-meter room with a terrifying object in a wooden box. The next day, no door. He never found it again.

The Author visits Iruma’s childhood home with him. The dead-end hallway is still there. He deduces that the 2004 Chuetsu Earthquake vibrated open a mechanism in the wall: a metal plate that acts as a magnetic latch. Using a strong neodymium magnet, the Author slides the hidden door open.

Inside: a wooden effigy of a beautiful woman missing her left arm and right leg.

Iruma realizes the doll’s proportional shape matches the architectural layout of his childhood home exactly. His father (a product designer who worked with rare earth elements) used his professional knowledge of neodymium magnets to build a magnetic concealment mechanism into the wall of his own house. The house is a shrine. The dead-end hallway is a penitential architectural prayer.

Literary Analysis

File 11 brings the unheimlich full circle. The domestic space Iruma grew up in was not a home. It was a monument. His father built it as a cult devotional object, shaped around the amputated form of the Holy Mother, with a hidden room at its “heart” containing her effigy. Iruma crawled around that effigy as a six-year-old with a dizzy spell and then lived alongside it, invisible in the wall, for decades.

The neodymium magnet is the satisfying technical payoff for a detail planted many files earlier: Iruma’s offhand mention that his father worked in product design involving rare earth materials.

Kurihara’s Deductions

Plot Summary

The Author presents all eleven files to Kurihara. Kurihara maps the geographic locations of every house and building, revealing that all of them orbit the Hall of Rebirth in Nagano at various distances. The architecture is a web, and the Hall of Rebirth is the anchor point.

Kurihara reconstructs the complete history.

Masahiko Hikura founded the Rebirth Congregation and installed Yaeko (whom his own family had bought from a brothel as a child) as the “Holy Mother.” The congregation exploited parents who were carrying the guilt of illegitimate children, extramarital affairs, or children born with disabilities. Hikura Homes sold them an architectural solution: remodel your home to structurally resemble Yaeko’s mutilated body, and your child will receive spiritual purification by sleeping in the building’s “womb.” The sacrament room was the uterus. The overnight stay was rebirth.

Kurihara traces Yaeko back to the watermill: she was born to Okinu inside the mechanical wall chamber, her arm severed by the wall, which reactivated as her dying mother tried to hide her. Hikura Homes later bought the Nagano land and built a house around the watermill to create a pilgrimage site. When the cult dissolved, they sold the property as a residential house.

The Author tracks down Mitsuko Hikura (from File 4). She confesses: on the night of her grandmother Yaeko’s “accident,” she had hidden Yaeko’s prosthetic leg while Yaeko slept. She did not act on her parents’ instructions. She acted in self-defense. Her parents were abusive and dangerous, and the one person in the house who protected Mitsuko was Yaeko. By killing the only person who cared for her, Mitsuko secured her own survival. She has been living with that calculus ever since.

Literary Analysis

Kurihara’s deduction sequence makes explicit what the novel has been arguing architecturally for eleven files: the houses are not cases. They are symptoms. Every bizarre floor plan, every removed room, every blocked window is a physical manifestation of guilt, coercion, or grief.

Mitsuko’s confession completes the novel’s moral geometry. She was not following orders. She was a child protecting herself from abusive parents by eliminating the one person in the house who loved Yaeko enough to be a problem. The cycle of abuse initiated by Masahiko Hikura, the man who bought a child from a brothel and installed her as a goddess, reaches its end in his own granddaughter killing the only person who ever protected her.

Connective Tissue

Mr. Kasahara from File 8 is confirmed as “Uncle” from File 7. His suicide in the sealed room, with the strange doll and the photo of Naruki, is the direct consequence of the cult’s collapse intersecting with his son’s death: the cult was a fraud, he could not save Naruki, and he sealed the “heart” of his own shrine-house as a final act of symbolic murder against the fiction that failed everyone.

The Matsue fire from Files 8 and 9 is fully resolved: Mrs. Matsue committed suicide after learning her pregnancy (with Kasahara’s child) would destroy her family. Mr. Matsue burned the house not to hide a murder but to destroy the forensic evidence of the affair and protect his son from the knowledge attached to his and his wife’s death.

Master Map: Planted Clues and Their Payoffs

The Clue Tracker

The Amputated Wooden Doll (File 1) → The Holy Mother (Files 6, 10)
The wooden doll missing its left arm and right leg found in the Negishi family’s belongings is not a curiosity. It is the physical representation of Yaeko’s mutilated body, the central religious icon of the Rebirth Congregation. The Negishi mother was a cult member.

The Main Road Prohibition (File 1) → Hidden Paternity (Kurihara’s Deductions)
The mother was not protecting Yayoi from traffic. A traffic accident would require a hospital visit and potentially a blood transfusion. The blood test would reveal Yayoi’s blood type did not match her legal father’s. Yayoi was born of an affair, and the mother spent 30 years managing the architectural and behavioral consequences of that secret.

The Hikura Homes Abuse Rumor (File 2) → The Brothel Transaction (File 10)
The “rumor” that the Hikura Homes president abused a young girl is confirmed in File 10 as Masahiko Hikura buying an 11-year-old girl from a yakuza-operated pedophile brothel and subsequently marrying her when she came of age.

The Slack String on the String Phone (File 8) → The Affair Alibi (Kurihara’s Deductions)
Chie measures the string phone and realizes it is too long for two adjacent rooms. Her theory — that her father was in the adjacent room faking an alibi while committing murder next door — is half right. Her father was in the adjacent building. He was not there to commit murder. He was there because he was having an affair, and the rustling incoherence Chie heard through the string phone was him discovering a dead body.

The Windowless Rooms, Dead-End Hallways, and Blocked Windows (Files 1, 5, 11) → Cult Architectural Conformity (File 6, Deductions)
Every case in the novel with a mysteriously removed room, a bricked-over window, or a dead-end passageway connects to the Rebirth Congregation’s architectural mandate. Members paid Hikura Homes to surgically alter their homes into the body shape of the Holy Mother. The houses were not haunted. They were penitential.

Thematic Resonance: How the Ending Shatters the Beginning

Strange Buildings begins as a collection of quirky, isolated puzzles about strange houses. By the final Kurihara deduction sequence, every puzzle is revealed to be a node in a nationwide conspiracy designed by one corporation to exploit guilt and sell architecture.

The novel’s final moral position is stark. Houses are neutral physical objects. They mean what the people who design them intend them to mean. When a corporation decides to industrialize guilt and sell architectural penance as a product, every house it touches becomes a crime scene, and the victims are not the people who died. The victims are the people who lived inside those houses, shaped by spaces designed to keep them ashamed and afraid and paying.

A house is meant to be a sanctuary. Uketsu’s complete argument, across three novels, is that a house is only a sanctuary if the people who designed it wanted you to be safe. When they did not, the walls hold the evidence.

Structural Relational Analysis

Files 1, 2, and 5: Isolated case studies. They establish the architectural anomaly pattern and plant the critical objects (the doll, the Hikura Homes name, the watermill) without context.

File 6 (The Hall of Rebirth): The structural keystone, placed dead center. It provides the cult’s floor plan: the ideological and architectural blueprint that makes every other case comprehensible.

Files 7, 8, and 9: A triptych of intersecting perspectives. Three people’s accounts of the same tragedy — the Matsue fire and Naruki’s death — demonstrate that geographic proximity creates narrative density. These three files are not separate cases. They are the same neighborhood, the same 48 hours, seen from three different upstairs windows.

Files 10 and 11: The origin layers. File 10 traces the Holy Mother’s life backward to the brothel. File 11 confirms the cult’s reach into a present-day home that an ordinary person is currently living in.

Kurihara’s Deductions: The zoom-out. Every isolated bubble becomes a node. The map of Japan’s Nagano region shows eleven distinct properties, all orbiting one address: the Hall of Rebirth.

Strange Buildings is the most structural of Uketsu’s three novels in the “Strange” series. It asks the reader to hold eleven separate cases in memory simultaneously and trust that they connect. They do, and the connection reveals something specific about how institutional power uses architecture: not just to imprison people, but to convince them that the imprisonment is their own fault, and that paying to reshape the walls will fix it.

Leave a comment

Who Is Uketsu?

Uketsu (雨穴, “rain hole”) is a Japanese author and YouTuber whose real identity remains known to approximately 30 people. He appears in public in a white papier-mache mask, a black bodysuit, and a voice changer. He lives in Kanagawa Prefecture. He spent part of his childhood in Surrey, England, and was working at a supermarket when he started posting on YouTube.

His early videos were surreal: asparagus transforming into severed fingers, strips of raw meat pegged on a washing line, spinning human ears. In 2020, he posted a 21-minute mystery story built around a series of architectural floor plans. Readers and publishers told him to expand it into a novel. The result was Strange Houses (変な家, Hen na ie), published in Japan in 2021.

Strange Houses was the first novel. Strange Pictures came after (2022), and Strange Buildings, a direct sequel to this book, followed in 2023. By 2024, three of Uketsu’s novels occupied simultaneous positions in Japan’s top 10 fiction bestsellers. The English translation of Strange Houses (published in 2025 by Pushkin Press) arrived to an anglophone market that had already been primed by the breakout success of Strange Pictures.

The formal concept behind Strange Houses is the one that made Uketsu’s YouTube channel successful: architecture as a text. A house floor plan, properly read, tells you things about the people who designed it that they would never say aloud.

Why This Summary and Analysis Exists

There is no thorough English-language, chapter-level breakdown of Strange Houses available. The book’s premise sounds like a puzzle box, and it is one, but the puzzle is more architecturally and psychologically layered than most reviews suggest. This is the complete summary and analysis, from Chapter One through the Afterword, with the full master map of connective threads at the end.

Buildings hide secrets, but so do images—I’ve done a separate deep dive into the hidden clues within Uketsu’s Strange Pictures.

Once you’ve navigated these homes, you'll want to explore the even larger scale of dread I covered in the Strange Buildings summary

To see how these architectural puzzles fit into a much larger narrative strategy, read my analysis of the patterns that define Uketsu’s work.

This piece contains complete spoilers for the entire novel.

Chapter One: A Strange House

Plot Summary

A freelance writer who specializes in the macabre (the Author) is approached by his acquaintance Yanaoka, who is looking to purchase a newly built two-story home in Tokyo for his growing family. Yanaoka has a problem. On the first floor, between the kitchen and the living room, there is a section of the house that has no doors, no windows, and no access. A dead space. Built in, walled off, sealed.

The Author, lacking architectural training, brings the floor plans to Kurihara, an architectural draughtsman and fellow mystery enthusiast. Kurihara is methodical. He notes that the dead space was created intentionally: two additional walls were constructed specifically to block it off, at the cost of reducing the kitchen’s floor area. Why would a builder voluntarily shrink a kitchen to seal off an empty section of the house?

Kurihara then directs the Author to the second floor. The child’s bedroom is in the corner farthest from the staircase. No windows at all. An en-suite toilet ensures the child never needs to leave. The room is accessible only through a double-door vestibule, a pair of sequential doors that create an airlock-style buffer between the child’s room and the rest of the house. Kurihara calls this design a solitary confinement cell. The architectural language communicates obsessive control over a child’s movement and presence.

The contradiction: the parents’ bedroom is bright and open. Their dressing room is completely exposed to the bed, with no privacy partition. And the house has 16 exterior windows, an unusual number for a residential build.

Kurihara reads the 16 windows as intentional. The house is performing normalcy to anyone looking at it from outside. All those windows say: nothing to hide here. Meanwhile, the interior hides its most important spaces completely.

The Author overlays the two floor plans and makes the key discovery: the walled-off dead space on the first floor aligns precisely with the corners of the child’s windowless room and the windowless bathroom. The dead zone is not a void. It is a vertical tunnel connecting the two.

Kurihara constructs a scenario. The parents bring someone home, get them drunk, suggest a bath. The imprisoned child in the bedroom drops through a trapdoor, uses the dead space as a vertical access shaft, enters the bathroom from below, and kills the naked and defenseless guest. Dismemberment occurs. Body parts are passed back through the tunnel to a storage room near the garage. Disposal by vehicle.

Yanaoka pulls out of the purchase.

Shortly after, a dismembered body is found in the wooded hills near the property. All parts present except the left hand.

Literary Analysis

The novel’s central conceit is established in pure form here: architecture as antagonist, floor plans as criminal evidence. The “Architectural Uncanny” (the Freudian unheimlich applied to domestic space, the familiar home becoming deeply wrong) runs through every page of this chapter. The genius of the setup is that Kurihara cannot be certain. He is constructing a narrative from empty geometric shapes. He may be wrong. The dismembered body at the chapter’s end is not confirmation that the specific murder scenario he described occurred. It is only confirmation that something terrible happened near that house.

Uketsu establishes his structural template here: the Author presents the Reader with a floor plan, Kurihara decodes it, and the Reader and Author arrive at a horrifying conclusion together. The 16 windows are the move that elevates the chapter from puzzle to literary statement. A house that decorates its exterior with abundance while hiding its interior in darkness is a house that has thought carefully about the optics of concealment.

Connective Tissue

The sealed dead space foreshadows the jammed fusuma doors in Chapter Three and the broader theme of the Katabuchi family’s architectural obsession: hidden passages as standard operating procedure across generations.

The missing left hand is the chapter’s most important planted clue. The Author briefly considers whether the body was dismembered to fit through the narrow passageways, which is the obvious interpretation and a red herring. The missing left hand is not a disposal problem. It is a ritual requirement, the “Offering,” which will become the structural center of the entire novel’s second half.

The 16 windows establish the Katabuchi family’s survival strategy for the rest of the book: performance of normalcy so complete and deliberate that it becomes its own kind of evidence.

Chapter Two: Another Warped Floor Plan

Plot Summary

Unable to let the case go, the Author publishes a vague article about the floor plans. He receives a letter from Yuzuki Miyae, an office worker from Saitama. Her husband, Kyoichi Miyae, vanished three years ago (in 2016). His body was recently found on a mountainside. The body was intact. His left hand was severed.

Yuzuki believes the murder connects to the Tokyo house. She found the floor plan of a home in Saitama where she believes the Tokyo family previously lived. The Saitama house was built in 2016 and recently burned to the ground.

The Author takes the Saitama floor plan to Kurihara. The similarities are clear: a windowless child’s room on the second floor, a windowless bathroom on the first floor, a dead space acting as a connection between them. But there are significant differences.

No garage. This explains why Kyoichi’s body was found intact rather than dismembered: the Saitama house had no good vehicle-accessible dismemberment and disposal route.

The parents slept in separate single beds.

The child’s room had only one door, not the double vestibule of the Tokyo house.

On the first floor, there is a bizarre retrofitted triangular room with large windows that are blocked by walls, making the room completely useless. It occupies space that previously opened onto the garden.

Kurihara identifies the triangular room’s function: it was built over a section of the garden after the original building was completed. Below it, in what used to be open ground, is an excavated cellar used to store intact bodies. No garage needed. The cellar is the cold storage.

Then the Author visits the empty Tokyo house and speaks to a neighbor. The family’s name was Katabuchi. They had a beloved one-year-old baby named Hiroto. They fled suddenly after the neighbor’s husband spotted something at a window: a pale, strange boy, approximately ten years old, sitting in the parents’ bedroom window late at night.

Kurihara synthesizes the data. There are two children. The first is Child X, the imprisoned assassin in the windowless cell. The second is Hiroto, the infant the parents clearly adore. The timeline tells the story of the house’s evolution: the Saitama house was originally built for the parents and Child X. When Hiroto was born, they added the triangular nursery room to keep the baby separate from the murder mechanics. Later, the Tokyo house was designed explicitly to manage both children simultaneously: the heavy double vestibule keeps X and Hiroto from ever sharing the same space. The double bed in Tokyo is for the mother and Hiroto, a human barrier between the infant and the door to X’s room.

The Author presents these conclusions to Yuzuki. She breaks down when she hears the family fled. The Author confronts her: Kurihara has established that the real Kyoichi Miyae was a bachelor. The woman calling herself Yuzuki Miyae is not who she says she is.

She confesses. She is Yuzuki Katabuchi. The woman in the murder house, the mother of Hiroto and warden of X, is her estranged older sister, Ayano.

Literary Analysis

This chapter introduces the novel’s most destabilizing structural move: the revelation that the architecture has been evolving to accommodate an expanding moral crisis. The Saitama house and the Tokyo house are not two separate crimes. They are two versions of the same insane problem, and each house physically reflects the exact state of the parents’ psychology at the time it was built.

Yuzuki’s false identity mirrors the architectural theme directly. She presents a false floor plan of her own life to gain access to the investigation, the same way the Katabuchi family constructs false floor plans to hide their crimes. Even the people in this novel perform spatial deception.

The introduction of Hiroto demolishes the reader’s stable moral framework. The parents are no longer simply sociopathic architects running a murder factory. They are people who are also raising a baby with apparent tenderness, building him a sunny nursery with pretty windows, sleeping next to him to keep him safe. The house holds both realities simultaneously. The Light Face and the Dark Face occupy the same square footage.

Connective Tissue

The double vestibule’s meaning shifts decisively here. In Chapter One, it read as a mechanism to keep the imprisoned child inside. In Chapter Two, it is reframed as a quarantine mechanism to keep the imprisoned child away from the innocent infant. The architecture has not changed. The interpretation has. This is the novel’s mirror of its own structural project: the same floor plan means something different on the second pass.

The pale boy seen through the window will be explained in Chapter Four: it is Momoya, the imprisoned child, using the hidden passage not to kill, but to reach the mother’s room and place a damp cloth on the feverish baby’s forehead. It is the first clear evidence that Momoya is not a monster.

Chapter Three: Drawn from Memory

Plot Summary

With her deception exposed, Yuzuki Katabuchi shares a piece of her family’s history that she has never told anyone. In 2006, her extended family gathered at the ancestral Katabuchi estate in the mountains: a large, highly symmetrical house divided evenly by a long central corridor with a massive, immovable black Buddhist altar at its exact midpoint.

During that stay, Yuzuki’s seven-year-old cousin Yoichi was found dead in front of the altar. His head was covered in clotted blood. The family ruled it an accident — he must have climbed the altar and fallen — and actively suppressed his mother Misaki’s attempts to call the police.

Kurihara analyzes Yuzuki’s hand-drawn floor plan of the estate. He identifies several anomalies. All the rooms on the right side of the house lack windows entirely. There is a set of fusuma (Japanese sliding doors) that are permanently jammed shut. Kurihara traces the structure’s hidden layout: a confinement room exists behind the altar, accessible only through the secondary passage masked by the jammed fusuma.

His reconstruction: Yoichi did not fall. A family member took Yoichi in the night, pulled him through the passage into the hidden confinement room (which would have muffled sounds completely, with no windows), killed him, and placed his body at the altar to stage the accident. No police investigation. Clean closure.

Yuzuki acknowledges this. Her own father was likely responsible, operating to manipulate the family’s line of inheritance in a way that would ultimately result in her sister Ayano being surrendered to the main Katabuchi family, to be indoctrinated and tasked with serving as a warden for disabled children.

Her father eventually lost his mind and died by suicide.

Literary Analysis

Chapter Three shifts the novel from modern procedural mystery into Gothic horror, and the transition is earned. The ancestral estate functions as the Katabuchi family’s architectural origin myth: the jammed fusuma, the hidden room, the windowless wing are not recent innovations. They are centuries of accumulated spatial habit. The family has been building these rooms for generations.

The massive altar at the center of the house is the novel’s most potent symbol. It physically dominates the floor plan, positioned at the geometric center of the corridor so that movement through the house requires passing around it. The family cannot go from one side of its own home to the other without acknowledging the altar’s presence. Ancestral weight made architectural.

Yuzuki’s father is a genuinely tragic figure, an ordinary person who committed a monstrous act under the delusion that he was protecting his family, and who could not survive the weight of what he had done. He is an early version of Keita, the figure the novel will examine with much more patience in Chapter Four.

Connective Tissue

The ancestral estate is the direct architectural prototype for every house in the novel. The jammed fusuma function as the same hidden passage system used in the modern Tokyo and Saitama houses. The windowless rooms on the right side of the estate are the prototype for the windowless child’s prisons in every subsequent Katabuchi dwelling. The confinement room behind the altar is the prototype for the entire murder tunnel concept. The family did not invent this. They inherited it. They could not stop building it.

Chapter Four: House of Chains

Plot Summary

The Author and Yuzuki visit her estranged mother, Yoshie. Yoshie produces a letter, written in full by Ayano’s husband, Keita, meant as a complete confession to the history of the Katabuchi family’s madness.

The origin: decades ago, the Katabuchi patriarch Soichiro entered into an incestuous relationship with his own sister, Chizuru. Soichiro’s neglected wife, Ushio, discovered the affair and, in a state of dissociation, severed her own left hand. Shortly after, Chizuru gave birth to a son, Momota, who was born missing his left hand.

The curse attribution: a manipulator named Rankyo (actually a woman named Shizuko from a rival branch of the family, orchestrating generational revenge) convinced Soichiro that Momota’s deformity was Ushio’s supernatural punishment. Rankyo established what became the “Offering of the Left Hand”: any Katabuchi child born with a missing left hand must be imprisoned from childhood, and between the ages of 10 and 13 must murder a descendant of the rival branch and present the victim’s severed left hand at the family altar.

Enter Keita and Ayano, the present-day wardens assigned to a disabled child named Momoya. They refused to become killers. They built the Saitama and Tokyo houses as theatrical sets designed to simulate compliance with the ritual while faking it entirely. Keita scavenged the intact bodies of suicide victims, specifically Kyoichi Miyae, a bachelor who jumped from a bridge, and presented their severed left hands to the family enforcer, Kiyotsugu, as the required “Offerings.”

The deception holds until Kyoichi’s body surfaces and the police investigate. Kiyotsugu confronts Keita: he knows the rituals were faked. He threatens to take Momoya back to the main family compound and force the boy to perform an actual murder.

During this confrontation, Momoya escapes his room through the hidden passage. He does not go to the bathroom. He goes to the mother’s room, where the feverish baby Hiroto is lying sick in bed. Momoya places a damp cloth on the infant’s forehead and stays with him until the fever breaks. The neighbor who glimpsed the pale boy at the master bedroom window was seeing Momoya nursing a sick baby.

Keita kills Kiyotsugu. Then he kills the family patriarch, Shigeharu. He takes full responsibility and disappears, leaving his wife and children with the story that absolves them.

Literary Analysis

Chapter Four is where the novel entirely reframes its moral architecture. The “monsters” living in the houses, Ayano, Keita, and Momoya, are victims. The architecture designed to imprison and kill was repurposed by Keita into a theatrical prop, a stage set for a performance of compliance that kept the family alive.

Keita is the inverse of every Katabuchi ancestor. Where they built prisons to enforce the ritual, he built identical prisons to fake it. The structural language is the same. The moral content is opposite.

Momoya nursing the sick baby shatters whatever remained of the reader’s horror at the imprisoned child. The narrative has been conditioning the reader to understand Momoya as a dangerous unknown, a pale figure glimpsed through windows, the engine of a murder factory. He is 10 years old, he has never killed anyone, and when he escapes his room for the first time, he tends to a sick infant.

The chapter’s catharsis is deliberately incomplete. Keita’s disappearance does not resolve anything except the immediate threat. The houses are destroyed, the enforcers are dead, but the family structure that produced the ritual, the centuries of architectural tradition, the incestuous origin of the curse, all of it simply continues.

Connective Tissue

All the missing left hands are accounted for: the unidentified Chapter One body (an earlier ritual victim or another scavenged suicide, unexplained by Keita’s letter), Kyoichi’s severed hand (a scavenged suicide victim presented as an Offering), and the ritual’s centuries of accumulated demands. The body in Chapter One with the missing left hand was the establishment of the mystery. Keita’s confession resolves the Kyoichi case but deliberately does not resolve the Chapter One case.

The double vestibule receives its final and most layered meaning. It was not to imprison X. It was a quarantine to protect Hiroto from knowing what was behind that door, and to protect Momoya from knowing the full extent of the disparity between how they were each being raised.

Afterword: Kurihara

Plot Summary

Kurihara meets the Author one final time. He says: case closed, except for one thing.

He points to a detail in the Tokyo house floor plan that nobody examined: a small interior window between the living room and the first-floor bedroom.

Interior windows destroy privacy. They exist for one purpose: observation. Keita’s letter describes him as a heroic figure who built the houses to protect his family. But Kurihara asks whether Keita was actually a prisoner himself, a man trapped by the Katabuchi family and watched constantly by Ayano through that observation window.

The possibility inverts the narrative of Chapter Four entirely. What Keita presented as a story of agency and sacrifice may be a story of coercion with a heroic gloss painted over it.

And then Kurihara notes the other unresolved thread: the dismembered body from Chapter One remains completely unidentified. Keita’s confession accounts for Kyoichi Miyae’s intact body. It says nothing about the person who was dismembered, whose left hand is somewhere nobody has looked.

The novel does not close.

Literary Analysis

The Afterword is the novel’s best move. Uketsu has spent 200 pages maneuvering the reader toward a tragic but emotionally satisfying resolution: the monsters are actually victims, the imprisoned child is gentle, the father sacrificed himself for his family. It is the kind of ending that lets readers feel sad but resolved.

The Afterword strips that away in four pages. Not through a dramatic twist, but through Kurihara pointing at a window and asking one question. The interior observation window is a small architectural detail, the kind of thing a reader would skip past. Kurihara does not skip past anything.

The final effect is the book’s thesis made explicit: a floor plan looks simple until someone who knows how to read it tells you what it actually means.

Connective Tissue

The interior window loops the novel back to Chapter One’s foundational instruction: look at the floor plan again, something is wrong, you missed it. The reader had the Tokyo house’s floor plan available from Chapter One. The window was there the whole time. Nobody looked at it.

The unresolved Chapter One dismemberment confirms that the neat resolution of Chapter Four was never the full story. The house confessed to some of its crimes. Not all of them.

Master Map: Planted Clues and Their Payoffs

The Clue Tracker

The Missing Left Hand (Chapter 1) → The Offering (Chapter 4)
A single detail on an unidentified body seems like a disposal problem. It is actually a religious requirement, the “Offering of the Left Hand,” the ritual demand at the center of a century-old family curse rooted in incest and fabricated superstition.

Intact vs. Dismembered Corpses (Chapters 1 & 2) → Two Murder Methods (Chapter 4)
Chapter 1’s victim was chopped apart. Chapter 2’s victim (Kyoichi) was whole, only the hand taken. Kurihara traces the architectural difference back to the mechanical difference: the Tokyo house had a garage and a disposal system designed for dismemberment; the Saitama house had an underground cellar designed for whole-body storage. The state of the corpses was dictated by the floor plan of the house used to process them.

The Jammed Fusuma (Chapter 3) → The Architectural DNA (Chapters 1 & 2)
The permanently jammed sliding doors in the ancestral estate look like a quirk of an old house. They are the prototype for every hidden passage in the modern houses. The Katabuchi family has been building these specific architectural elements for generations. It is structural habit, passed down like a genetic trait.

The Pale Boy in the Window (Chapter 2) → Momoya Nursing Hiroto (Chapter 4)
The neighbor’s sighting of the pale boy on the parents’ bed is framed throughout the middle section of the book as the behavior of a dangerous, unpredictable prisoner. It is actually the precise moment Momoya’s humanity is demonstrated: he has navigated the secret passage not to hurt anyone, but to care for a sick infant who is not, technically, related to him.

The Triangular Room’s Blocked Windows (Chapter 2) → The Underground Cellar (Chapter 4)
The retrofitted triangular nursery with its uselessly blocked windows does not make architectural sense until the cellar beneath it is discovered. The large windows were added for the baby’s nursery, then blocked when the function of the space underneath required secrecy. The architecture records the change in purpose.

Thematic Resonance: How the Ending Reframes the Beginning

Strange Houses begins as a cool, clinical puzzle about malevolent architecture. By the end, it is a study in how generational trauma becomes structural: how the sins of an ancestor are literally encoded into the walls of every building their descendants are forced to construct, generation after generation, because no one in the family was ever able to say “stop.”

The floor plan of the Katabuchi lineage dictates the physical floor plans of the homes they build. The incest and suicide of the founding generation produced a deformed child, and the deformed child produced a ritual, and the ritual produced a building type, and the building type became tradition, and the tradition imprisoned every generation that followed. The houses are the family.

Keita’s theatrical set was the first act of genuine refusal in the entire lineage. He built the same structures his ancestors built, but he built them to protect the child rather than destroy him. The structures looked identical. The moral content was entirely different. That distinction costs him everything.

Structural Relational Analysis

Chapter 1: One floor plan, one dead space, one missing left hand. A tightly scoped introduction to the core architectural puzzle.

Chapter 2: Two floor plans, two timelines, two houses that tell the story of a family expanding and adapting its crimes to new circumstances. Introduces the human beings behind the architecture.

Chapter 3: One ancestral estate, one hidden room, one murdered child. Zooms back decades to the source code of the family’s architectural obsession.

Chapter 4: The complete family tree, the complete history of the ritual, the complete explanation of every house in the novel. Zooms all the way out. The houses were not designed by killers. They were designed by trapped people who were themselves designed by the houses they grew up in.

Afterword: One small window. One unanswered question. The floor plan of the entire novel is pulled back to reveal a dead space you missed.

The English translation of Strange Houses (Pushkin Press, 2025) features the original floor plan diagrams embedded in the text as intended, which is important. This is a novel you read with a pen. The floor plans are not illustrations. They are evidence.

Leave a comment

Who Is Uketsu?

Almost nothing is known about the person behind the name. Uketsu (雨穴, which translates to “rain hole”) is a Japanese author and YouTuber who appears in public wearing a white papier-mache mask, a black bodysuit, and a voice changer that modulates his voice to sound something between mechanical and childlike. His true identity is known to roughly 30 people — his family, publisher, and a small group of collaborators. He is a man. He lives in Kanagawa Prefecture, southwest of Tokyo. He spent part of his childhood in Surrey, England. He was working at a supermarket when he began posting online. That is more or less the complete profile.

His early YouTube videos were surreal: asparagus that transforms into severed fingers when chopped, strips of raw meat pegged out on a washing line, eight human ears spinning on a wheel. Then in 2020 he posted a 21-minute mystery story built around a series of architectural floor plans. The response was overwhelming. His publisher told him to turn it into a novel.

The rest followed quickly. By 2024, three of Uketsu’s books occupied simultaneous slots in Japan’s top 10 fiction bestsellers. Strange Pictures (変な絵, Hen na e), published in Japan in 2022 and translated into English by Jim Rion in January 2025, sold over 1.5 million copies in Japan alone and has been translated into more than 30 languages. It was shortlisted for Waterstones’ 2025 Book of the Year and topped Germany’s May 2025 Krimibestenliste. A manga adaptation by Aiba Kiko launched in 2024.

Why This Summary and Analysis Exists

Nobody has put up a truly detailed, chapter-level breakdown of Strange Pictures in English. Reviews exist, plot summaries exist, but nothing that maps the structural puzzle, traces the planted clues back to their payoffs, and explains why this book works the way it does. That is what this piece is. It is the complete summary and analysis, chapter by chapter, with a full master map of narrative threads at the end. If you have already read the book, this is the deepest dive available. If you have not, this will tell you exactly how it was built and why it is worth your time.

If you think these sketches are unsettling, you need to see the architectural nightmares I’ve deconstructed in my deep dive into Strange Houses.

The mystery doesn’t stop at art; I have also analyzed the terrifying structural anomalies in Uketsu’s Strange Buildings—check it out here.

To understand the ‘why’ behind these eerie visuals, I’ve put together a full breakdown of the recurrent themes and patterns Uketsu uses to keep us on edge.

Fair warning: this is the kind of analysis that only works with full spoilers. Everything is revealed.

Prologue: The Drawing Test

Plot Summary

The novel opens in a university lecture hall. Dr. Tomiko Hagio, a former practicing psychologist, presents her students with a drawing made by an eleven-year-old patient she calls “Little A.” The child was institutionalized after murdering her abusive mother. The drawing was produced via a standard HTP (House-Tree-Person) test, one of the oldest tools in psychological evaluation.

Dr. Hagio walks her students through three anomalies in the drawing. First, the figure’s mouth is heavily smudged. Hagio reads this as physical trauma memory: the child’s hands trembled as she recalled being forced to smile constantly to appease her abuser. Second, the house lacks a door. Hagio interprets this as a fortress mentality, a desire to lock the world out. Third, the tree’s branches end in sharp, thorny points, a trait frequently observed in drawings produced by violent offenders, indicating deep aggression.

Then comes the pivot. Little A drew a small bird resting safely inside a hollow in the tree’s trunk. Hagio seizes on this as a profound “desire to protect,” a capacity for nurturing love underneath the violence. She closes the lecture by telling her students that Little A is now living happily as a mother.

Literary Analysis

Uketsu uses the prologue to lay a false foundation with complete structural confidence. He introduces the novel’s core motif, ekphrasis (the literary representation of visual art as a narrative device), and establishes the governing rule of this fictional universe: drawings reveal what words cannot. The reader accepts the framework because Dr. Hagio presents it with clinical authority. She is credentialed. She is correct about the smudging, the doorless house, the thorny branches. Three out of four.

The fourth interpretation, the bird as proof of nurturing instinct, is the one that kills people.

This is the book’s most elegant structural trick. Uketsu teaches the reader to trust psychological interpretation in the opening pages, then spends the rest of the novel proving that trust is precisely what gets everyone killed.

Connective Tissue

“Little A” is later revealed to be Naomi Konno, the central antagonist. Dr. Hagio’s diagnosis that Naomi’s nurturing instinct would override her aggression was not just wrong. It was catastrophically inverted. The bird in the hollow does not represent love softening violence. The thorns protect the bird. Naomi’s maternal obsession is the mechanism of her murders: she kills everyone who threatens what she has claimed as hers.

Chapter One: The Old Woman’s Prayer

Plot Summary

On May 19, 2014, Shuhei Sasaki, a 21-year-old college student, investigates a defunct blog recommended by Kurihara, a junior in his Paranormal Club. The blog, titled “Oh No, Not Raku!”, was written by a man using the pseudonym “Raku.” Its subject: his life with his wife Yuki, a former professional illustrator six years his senior. The posts begin in October 2008, cheerful and domestic, covering their daily life and Yuki’s pregnancy.

The final post, dated November 28, 2012, appears after a three-year silence in the archive. Addressed “To the one I love most,” the post says Raku has finally decoded “the secret of those three drawings,” that he cannot forgive his wife’s “sin,” and that he still loves her. Then nothing.

Reading backward through the archive, Sasaki learns that in May 2009, Yuki was diagnosed with a breech pregnancy. The hospital recommended natural delivery. As the due date approached, Yuki drank excessive amounts of juice, citing uncontrollable thirst. To manage her anxiety, she drew five cryptic images she called “visions of the future” — a baby in a Santa hat, an old woman praying, an adult woman with flowing hair, a young boy, and an adult man. On October 11, 2009, the blog ends: Yuki died of a brain hemorrhage during an emergency C-section. The baby survived.

Kurihara and Sasaki work through the archive. Kurihara spots a mathematical impossibility in a post about an anniversary cake: 8 slices, Raku eats 2, Yuki eats 1, 4 are saved, one is unaccounted for. Someone else was living in that apartment. Raku never mentioned a third resident.

Sasaki cracks the drawings. He notices that each has a circled number. Yuki was a professional illustrator. She would know layer composition. Sasaki stacks drawings 1, 2, and 3, aligning their circles as central axes and scaling accordingly. The composite image is the worst thing in the book: drawing 1’s “Santa hat” becomes a bloody incision in a pregnant belly; drawing 2’s “praying old woman” becomes a doctor in scrubs pulling a baby from the wound; drawing 3’s “adult woman with flowing hair” becomes a stiff corpse on an operating table. Yuki had drawn a picture of her own murder, embedded across three innocent-looking images.

Stacking drawings 4 and 5 yields a second image: a man and a young boy walking away together, hand in hand. Yuki drew a future she would not be alive to see.

Literary Analysis

Uketsu deploys an epistolary format here: the entire chapter is mediated through the text of an old blog. This is the most technically restrained chapter in the book, and the most effective for it. The horror is assembled from mundane domestic posts. The reader and Sasaki are doing the same thing at the same time, reading forward through ordinary life and feeling the wrongness accumulate.

Kurihara functions as the Holmesian catalyst. He is not a lead character. He is the engine of deduction that forces Sasaki past passive reading into active forensic analysis. The composite drawing introduces a structural metaphor that governs the entire novel: reality changes entirely depending on how you layer the information. Every chapter in this book is a “drawing” that means something different when stacked against the others.

Connective Tissue

The missing cake slice establishes that a hidden third person was living with Raku and Yuki. That person is Naomi, Raku’s mother, whose presence in the household is kept entirely offscreen until the Final Chapter. The warning Raku received (about not posting personal photos online) came from someone other than Yuki, another trace of Naomi’s invisible influence.

Yuki’s excessive thirst is a forensic plant. In the Final Chapter, we learn Naomi was replacing Yuki’s prenatal iron supplements with 15 grams of pure salt daily, inducing the hypertension that would kill her on the delivery table.

No responsible modern obstetrician recommends natural delivery for a breech presentation. Kurihara notes this. The payoff: Naomi was the senior midwife at the clinic, with enough institutional authority to overrule the attending physician.

The blog title, “Oh No, Not Raku!,” is a direct anagram of “Haruto Konno.” Raku is not Raku. He is Haruto Konno, Yuta’s father, whose death by suicide explains why the blog went permanently dark in 2012.

Chapter Two: The Smudged Room

Plot Summary

Point of view shifts to Naomi Konno: widowed, raising her five-year-old son Yuta in a sixth-floor apartment. The chapter opens with her scolding Yuta harshly for using a geometric stencil ruler to draw in permanent marker on the apartment walls.

A concurrent storyline: Naomi notices a man in a grey coat following her and Yuta home. He drives a compact car. She cannot place him but feels the threat clearly.

At Yuta’s nursery school, homeroom teacher Miho Haruoka examines Yuta’s Mother’s Day drawing. He drew their apartment building in reasonable detail, but their specific sixth-floor room has been violently smeared over with a grey blotch. Haruoka investigates the mechanics. Yuta did not use a grey crayon. He used a white crayon over a black underdrawing, the pressing and smearing mixing the pigments into an opaque grey. A classmate, Miu Yonezawa, volunteers that Yuta’s original drawing showed a large rectangle with a small triangle inside, before he erased it.

Haruoka connects the shape to the stencil ruler Naomi punished Yuta for using. Drawing on child psychology research (the principle that children draw the idea of trauma rather than literal objects), she concludes the marks Yuta drew symbolize the implement his mother struck him with. She phones Naomi to report suspected abuse.

Naomi realizes Haruoka has misread the drawing. The rectangle and the triangle are not a stencil ruler. They are the kanji 今野, the characters for “Konno,” which looks like a triangle sitting above a rectangle. Yuta was attempting to draw a gravestone, his mother’s gravestone. Naomi deduces that Yuta has been sneaking to Sakura Memorial Garden, where he has a faint memory of his father once taking him to visit “Mummy’s” grave. She goes to the cemetery.

She finds Yuta at the headstone of Yuki Konno.

That evening, the grey-coated man follows Naomi into her apartment building. She has anticipated this. She waits behind her door with a kitchen knife. When he steps inside, she stabs him. As he falls, his hood drops: the wrinkled face of an old man she dimly recognizes.

Literary Analysis

Chapter Two is a study in dramatic irony operating at high efficiency. The reader knows Naomi is dangerous by the time this chapter begins. Uketsu uses that knowledge to manufacture a deeply uncomfortable sympathy: Naomi is also exhausted, isolated, and being falsely accused of abusing her son. The reader is asked to feel bad for a woman who is about to stab someone.

Haruoka mirrors Dr. Hagio precisely. She uses the same theoretical framework — art as expression of subconscious trauma — and reaches an equally wrong conclusion. Uketsu is deliberate about this repetition. The novel is asking whether the problem is the framework or the practitioners. The answer it gives is: the framework.

Yuta’s smeared drawing is the novel’s second major piece of ekphrasis. The grey blotch does not represent the stencil ruler, and it does not represent abuse. It represents Yuta desperately trying to erase a present reality and access a buried one. He is trying to draw through it, to the name of the dead woman he has never been allowed to know was his mother.

Connective Tissue

This chapter confirms Yuta is the baby from Chapter One, the child who survived Yuki’s murder on the operating table.

It establishes Naomi’s identity as Haruto’s mother, not Yuki’s. She is therefore the “old woman praying” in Yuki’s composite drawing — the figure with both hands reaching into a surgical incision, yes, but also the grandmother who will raise the child as her own.

Haruto’s sequence becomes clear here. He deciphered Yuki’s drawings. He took Yuta to his mother’s grave, a final act of fatherly honesty. He wrote his last blog post. Then he killed himself.

The man Naomi stabs is Isamu Kumai, a veteran reporter introduced formally in Chapter Three. He survived. His “stalking” of Naomi was deliberate provocation, designed to trigger the violent reaction that would give his police contact, Detective Kurata, grounds to arrest her.

When threatened, Naomi does not call the police. She picks up a knife. This is how she has always operated.

Chapter Three: The Art Teacher’s Final Drawing

Plot Summary

The timeline shifts to August 1995. Shunsuke Iwata is a 19-year-old high school graduate, placed in the administrative department of the L-Daily newspaper after failing to land a reporting position. He wants one specific story: the 1992 unsolved murder of his high school art teacher and personal mentor, Yoshiharu Miura.

His boss in the admin department is Isamu Kumai, a veteran reporter demoted after a bout with esophageal cancer. Kumai was the lead reporter on the Miura case and shares his confidential files with Iwata.

The physical evidence from the 1992 murder on Mt. K is strange. Miura’s body was discovered at the mountain’s eighth-station clearing, beaten with a rock more than two hundred times, rendering it completely unidentifiable. The degree of mutilation forced the pathologist to rely entirely on stomach contents to estimate the time of death: Miura ate a Hanayagi bento box, and digestion placed his death at 5:00 PM on September 20. This timeline cleared Miura’s wife (alibi for the morning of the 21st) and a student named Yuki Kameido (alibi for the evening of the 20th). The prime suspect became Nobuo Toyokawa, a resentful college friend of Miura’s who had no alibi for that evening.

Two details continued to bother investigators: Miura’s sleeping bag was stolen, and some of his food was missing. Additionally, Miura had drawn a crude picture of the mountain range on the back of a folded supermarket receipt.

Iwata pursues an independent lead to his old school and encounters a blind student drawing on a “pierced canvas,” a surface with tactile gridlines. The image clicks. Miura folded the receipt into a grid and drew the mountains by touch, without seeing his own hands.

Iwata hikes Mt. K on the anniversary of the murder to test the theory. At the eighth station at 5:00 PM, he looks at the mountain range and sees nothing. The setting sun is directly behind it. The mountains are completely backlit, invisible against the glare. Miura could not have drawn a detailed landscape in those conditions.

He deduces the actual sequence: the killer captured Miura, restrained him in his own sleeping bag through the night, and force-fed him the Hanayagi bento the next morning (disguising the forced feeding as normal consumption). Two and a half hours after the meal, the killer murdered Miura and destroyed the body beyond recognition to eliminate rigor mortis as a time-of-death indicator. The bento’s digestion level did the rest: it placed the death ten hours earlier than it occurred, pushing it into the time window when the killer had an alibi.

Iwata realizes the brutal mutilation was never about rage. It was a forensic necessity. With his theory proven, Iwata sits in his tent on the mountain.

That night, Naomi Miura binds him in his sleeping bag and force-feeds him.

Realizing what is happening and why, Iwata manages to fold a piece of paper and draw one last blind picture of the mountains against his restrained hands before she kills him. Naomi then murders Toyokawa, types a fabricated suicide note on a brand-new word processor to frame him for both deaths, and closes the police file for good.

Literary Analysis

This is the chapter where the novel changes genre mid-stride. The domestic thriller disappears and a hardboiled forensic procedural takes over. The shift is jarring in the best way: the stakes recalibrate completely. What began as an internet mystery about a defunct blog is now a story about a nineteen-year-old trying to solve a three-year-old mountain murder and getting killed for coming too close.

Uketsu subverts the alibi-trick trope in a way that recontextualizes every element of the crime scene that seemed emotionally charged. The 200-plus blows with a rock are not violence born from hatred. They are a technical requirement. They exist to prevent the pathologist from using body temperature or rigor mortis to triangulate time of death, forcing him to rely entirely on the one piece of forensic evidence the killer controlled: the bento.

Iwata’s “dying message,” the blind folded-receipt drawing, mirrors Yuki’s compositional drawings from Chapter One. Again: art as the only available testimony when speech is impossible. The novel circles back to its own premise.

Connective Tissue

This chapter reveals who Kumai is: the grey-coated stalker from Chapter Two. He survived. His cancer is still progressing. His plan was to provoke Naomi into an attack he could turn into legal evidence, avenging Iwata’s death before his own runs out.

The fake suicide note typed on a brand-new word processor is a deliberately planted clue: a real suicide note would be handwritten. The new word processor proves it was forged to avoid a handwriting match.

The Final Chapter: The Bird, Safe in the Tree

Plot Summary

Following her 2015 arrest, Naomi Konno’s history is reconstructed in full.

As a child, her father’s suicide left her alone with a deeply abusive and sociopathic mother. Naomi found one source of comfort: a pet finch she named Cheepy. When her mother tried to crush Cheepy to death, eleven-year-old Naomi fought back, and stomped on her mother’s neck until she died. She was committed to a juvenile reformatory.

That girl was “Little A.”

Naomi eventually became a midwife, married Yoshiharu Miura (the murdered art teacher), and had a son, Haruto. Miura was a harsh disciplinarian who struck the introverted Haruto and forced him outside. Terrified that her juvenile record would cost her custody of Haruto in any divorce, Naomi planned and executed the elaborate murder on Mt. K. She killed Toyokawa later when he deduced the method and attempted to blackmail her into a sexual relationship. She killed Iwata when he got too close.

Years later, the adult Haruto reconnected with Yuki Kameido, Miura’s former art student, and married her. They moved in with Naomi. Yuki became pregnant.

Naomi began to want the baby. Not just to help raise it. To own it.

Using her medical knowledge, she replaced Yuki’s prenatal iron supplements with 15-gram daily doses of sodium chloride. Pure salt. Ingested throughout a pregnancy, this level of sodium induces progressively worsening hypertension. Naomi, as senior midwife at the clinic, falsified Yuki’s blood pressure charts and arranged for the dangerous natural breech delivery. On the operating table, Yuki’s blood pressure spiked to fatal levels. She died of a brain hemorrhage. Naomi took the baby.

Three years later, Haruto decoded Yuki’s composite drawings. He understood what his mother had done. The blog’s final post was a goodbye, written to Haruto’s wife, who was already dead. He took Yuta to Yuki’s grave. Then he hanged himself.

In the aftermath of Naomi’s arrest, Dr. Hagio realizes her diagnosis of “Little A” was wrong. Not about the smudging or the doorless house or the thorny branches. About the bird. She assumed the bird represented the capacity for nurturing, a force that would soften the aggression. She had the causality backwards. The thorns do not sit beside the bird by accident. The thorns exist to protect the bird. Naomi’s maternal love is not the thing that redeems her violence. It is the engine of it.

Kumai, recovering in the hospital, shares a room with Kurihara (from Chapter One). Kurihara explains the blog’s mysteries. Kumai, whose cancer is advanced and whose life is effectively over, adopts the newly orphaned Yuta to break the cycle.

Literary Analysis

The Final Chapter resolves the novel as a psychological horror story masquerading as a mystery. Naomi is not a mystery to be solved. She is a psychological profile to be understood. The resolution does not comfort.

Uketsu does something technically interesting with the moral framing. Naomi’s first three murders are arranged to invite sympathy: she killed an abusive mother to save a defenseless bird, she killed an abusive husband to protect a vulnerable child, she killed a blackmailer to protect an innocent life. The pattern is consistent enough that the reader has to actively resist the framing. Then comes Yuki’s murder, which breaks the pattern cleanly. Yuki was not threatening Haruto. Yuki was simply in the way of Naomi’s ownership of a new person to possess. The novel’s moral center snaps back into place.

The book’s catharsis comes not through punishment but through substitution. Kumai, a dying man with nothing left to protect, takes Yuta home. The cycle breaks, not through justice, but through a simple act of un-poisoned care.

Master Map: Planted Clues and Their Payoffs

The Clue Tracker

The Missing Cake Slice (Chapter 1) → The Hidden Housemate (Final Chapter)
Raku’s anniversary post describes an 8-slice cake. Two slices for Raku, one for Yuki, four saved. One slice is mathematically unaccounted for. Naomi Konno was living with them and eating their food, invisible in every post.

Yuki’s Excessive Thirst (Chapter 1) → The Murder Weapon (Final Chapter)
Raku attributes Yuki’s extreme thirst to summer heat. It was sodium poisoning. Naomi had replaced the iron supplements with 15 grams of salt daily for months. The polydipsia (excessive thirst) is one of the body’s emergency responses to hypernatremia. Raku wrote it down because it was unusual. Uketsu put it in the blog because it was the proof.

The Breech Birth Recommendation (Chapter 1) → The Engineered Death (Final Chapter)
No modern, competent obstetrician recommends natural delivery for a breech presentation. Kurihara flags this in Chapter One. The payoff: Naomi was the senior midwife at the clinic, with institutional authority over the physician. She falsified the blood pressure records and staged the medical scenario that ensured Yuki would die on the table.

The Stencil Ruler Drawing (Chapter 2) → The Gravestone Misread (Chapter 2)
Naomi punishes Yuta for using a stencil ruler. When the teacher later misidentifies the shape in Yuta’s drawing (a triangle over a rectangle) as a stencil ruler, she is working from the wrong premise. The shape is 今野, the Konno family name, written as a gravestone marker.

The Folded Receipt Creases (Chapter 3) → The Blind Alibi (Chapter 3)
The crossing crease lines on Miura’s receipt drawing look like accidental folds. Iwata realizes they are tactile guidelines, folded deliberately so Miura could draw by feel with his hands restrained inside a sleeping bag. The creases are the proof that the time-of-death alibi was manufactured from start to finish.

The Backlit Mountains (Chapter 3) → Miura Drew in the Morning (Chapter 3)
The eighth station of Mt. K faces west. At 5:00 PM in September, the sun is behind the mountains. They are completely black against the glare. A person standing there cannot see the mountain’s features. Miura’s drawing captures those features. He drew it in the morning. Everything the police believed happened at 5:00 PM happened at 7:00 AM.

Thematic Resonance AKA How the Ending Shatters the Beginning

Strange Pictures is structurally a funnel. Each chapter draws in more scope — internet mystery, domestic thriller, true-crime procedural — and the Final Chapter collapses them into a single psychological portrait.

The prologue is the thesis. Art reveals subconscious truth. Dr. Hagio states this with authority, demonstrates it with precision, and then draws the wrong conclusion from it. The novel does not reject the thesis. It shows what happens when the thesis is applied by someone who is already looking for a reason to be hopeful.

The ending delivers the anti-thesis not as a correction but as a demonstration: the thorns were never meant to be overcome by the bird. The bird was the reason for the thorns. Naomi’s maternal instinct is not a capacity for love that kept her from becoming a monster. It is the specific shape her monstrousness takes.

Uketsu closes with Kumai and Yuta, which is the only note of something resembling repair in the book. Kumai is not a hero. He is a dying man who has nothing left to lose and one decent thing left to do. That is exactly enough.

Structural Relational Analysis

Chapter 1 (The Inner Circle): Purely digital. Internet archive forensics. No physical contact with any victim. The horror is abstract and intellectual.

Chapter 2 (The Second Circle): Domestic thriller. Physical proximity, dramatic irony, emotional misdirection. The reader is inside the household of the antagonist, rooting for her against a stalker.

Chapter 3 (The Third Circle): Historical true-crime procedural. Physical, brutal, geographically specific. Provides the forensic mechanics needed to understand the full scope of Naomi’s capability.

The Final Chapter (The Synthesizing Ring): Connects every character, every timeline, every planted clue. The internet mystery, the domestic thriller, and the cold-case procedural were all circles drawn around the same person. The structure of the novel is the composite drawing.

If you’ve read this far and haven’t picked up the book yet: the English translation by Jim Rion (HarperVia, January 2025) is as clean and precise as the source material deserves. What makes Strange Pictures work in translation is not just the puzzle mechanics. It is the restraint. Uketsu never overexplains. He trusts the reader to look at the drawing and see what is there.

Leave a comment

👋🏻 Hey. I’m Atharva.

Software engineer, GTM strategist, and AI-native builder. I work at AccuKnox doing DevRel and growth engineering for cloud-native security products. Before that: freelance dev, technical writer, research consultant.

This newsletter is where I write about the things I’m actually building and the decisions I’m actually making. AI systems, growth infrastructure, developer workflows, and once in a while the movies, music, and games that I think are worth your time. No summaries. No secondhand takes. Just what I built, what broke, and why I made the calls I did.

Four categories. Pick the one you came here for:

🔵 Tech and AI — LLMs, AI cost engineering, Claude ecosystem, developer tools, hands-on implementation

🟢 Biz and Growth — GTM strategy, lead generation, content systems, marketing automation

🟡 Money and Career — Career decisions, compensation, investing, working in tech on your own terms

🔴 Entertainment and Culture — Film, music, gaming, fiction, ideas worth arguing about

Pick the outcome that matches where you are right now:

• 💸 AI Cost & Systems

• 🤖 Claude Ecosystem

• 🛠️ Dev Workflow & Tools

• 📈 GTM & Lead Generation

• 📣 Content & Growth

• 💼 Money & Career

• 🎬 Culture & Entertainment

• 📖 Full Archive

• 🔗 Find Me Elsewhere

💸 AI Cost & Systems

You’re paying more than you should for AI. Or you’re not sure why the costs blow up at scale. Or the outputs are inconsistent and you don’t know where the model is losing you. Start here.

Practical Tips for Reducing AI Costs – Part 1: Tactical Stack — Model selection, prompt caching, batching, and the fast wins that cut your bill without touching your architecture.

Practical Tips for Reducing AI Costs – Part 2: Context Optimization & Memory Management — How context window bloat silently multiplies costs, and how to design memory that doesn’t.

Practical Tips for Reducing AI Costs – Part 3: Advanced Algorithms & Internal Governance — Routing logic, fallback chains, eval frameworks, and governance at the org level.

Token Anxiety and the Illusion of Productivity — What happens when you optimize for tokens instead of outcomes, and how to stop confusing activity with progress.

AI Slop Is a Skill Issue — Bad outputs come from bad inputs. An honest breakdown of where most people’s prompting falls apart.

50 AI Terms Every Developer and Builder Should Know — The terminology that separates people who understand what’s happening from people who just use the tools.

🤖 Claude Ecosystem

Claude is the AI I use most. These posts cover how to actually set it up, extend it, and make it work the way your brain works.

Building an AI Marketing Team with Claude Skills — How I wired custom skills into Claude to run a full content operation. The actual setup, not a concept piece.

Skills 2.0 – Anthropic Just Made Vibes-Based AI Building Obsolete — What changed with Claude’s skill architecture and why it matters for anyone building serious workflows.

The 5 Files That Give Claude Code Permanent Memory — Context management for Claude Code. How to structure your files so the model actually remembers what matters across sessions.

🛠️ Dev Workflow & Tools

The stack you use every day compounds. These are the tools and setups I’ve actually committed to, with honest takes on what’s worth your time.

GitHub Copilot – A Complete Guide to Agents, Skills, and Instructions — Everything Copilot can do that most people haven’t touched. Agents, custom instructions, skills, and how to set it up properly.

The 30-Minute Copilot Setup That Changes Everything — The specific configuration I use. Faster than you think to set up, meaningfully different after.

One Command to Share Your Entire VS Code Setup — Export your extensions, settings, and keybindings. Useful if you’re setting up a new machine or onboarding someone.

Your New PC Migration Should Not Cost You a Full Day — The actual checklist I use. No fuss.

The Tech Stack I Bet My Career On — Python, FastAPI, Next.js, AWS, Cloudflare Workers. Why these, not the alternatives, and what the tradeoffs actually look like.

SEO for Vibe-Coded Apps – Audit and Fix — What breaks SEO when you build fast with AI, and how to audit and fix it without starting over.

Forget Ranking #1 on Google – Get Recommended by AI Instead — GEO (Generative Engine Optimization) explained practically. How to structure content so LLMs cite you.

📈 GTM & Lead Generation

These cover the growth systems I’ve actually built and tested. Not theory. Results with the specifics.

2026 Marketing Stack for AI-Driven GTM — The full stack for a modern GTM motion. What each layer does, where AI actually helps, and what to cut.

The 3-Step Workflow to Intercept High-Intent Leads on Reddit and LinkedIn — Find people who are already looking for what you offer. Step-by-step, no ad spend.

The Zero Dollar Lead Gen Channel Your Competitors Ignore — The channel most B2B teams dismiss. It compounds quietly and the barrier to entry is low.

The LinkedIn Pipeline Nobody Is Talking About — How to turn LinkedIn into a consistent inbound pipeline with less effort than most people spend on one post.

I Almost Spent $250 on LinkedIn Auto-Comments — What I found when I actually looked at the tools. And what works instead.

How to Win Your First 10K Users Without Spam — Early distribution strategy for builders. What actually moved the needle at small scale.

Integration Strategy for Small Teams — How to connect your tools without engineering overhead. The decisions that save you from workflow debt later.

📣 Content & Growth

The content system is the asset. These posts are about building one that compounds instead of one that needs constant feeding.

Stop Writing Posts. Start Building a Content Flywheel. — The mental model shift that changes how you approach every piece of content you create.

The 2026 Content Stack – Three Tools to Win — The actual tools I use. Why these three cover most of what you need.

My Second Brain Setup That Actually Compounds — The Obsidian system I use daily. How I capture, link, and resurface ideas across every project.

The Joy Revolution Nobody in Your Marketing Meeting Will Approve — Why the most effective content right now looks like the opposite of what B2B teams produce.

💼 Money & Career

The business of being a technical person. Compensation, investing, career decisions, and working in tech without optimizing for the wrong things.

Two Years at AccuKnox – From Intern to Specialist — What I learned inside a cloud-native security startup. The real version, not the LinkedIn version.

You Don’t Rise to Your Goals. You Fall to Your Systems. — Why discipline is overrated and environment design is underrated.

Calculating Your FIRE Number — The math and the assumptions behind financial independence. How to run it for your own situation.

A Dummy’s Guide to Investing Wisely — First principles investing for people who don’t want to become investors.

Inflation Isn’t One Thing — Why the headline number masks what’s actually happening to your purchasing power.

Slaying Your 20s — A five-part series on owning your path, ambition vs contentment, money, digital detox, and staying present.
Part 1: Owning Your Path · Part 2: Ambition vs Contentment · Part 3: Mastering Money · Part 4: Digital Detox · Part 5: Staying Present

🎬 Culture & Entertainment

Film, music, gaming, fiction. I have opinions and I’ll defend them.

Mickey 17 – A Systemic Analysis of the Future of Human Labor — What Bong Joon-ho actually built underneath the sci-fi premise.

Film School in Scenes — A multi-part deep dive into directing, cinematography, story craft, and the craft of great filmmakers.
Intro · Part 1: Heart of Story · Part 2: Masters of the Medium · Part 3: Vision and Craft · Part 4: The Director’s Process · Part 5: The Power of Restraint · Part 6: Anatomy of a Scene · Part 7: The Invisible Language

Her (2013) – The Cultural and Ethical Weight of AI on Film — Why this film holds up better every year.

The Darkest Genre in Gaming Nobody Talks About — The games built around dread, loss, and systems that punish you for existing.

How 675 Million Spotify Users Get Fed Music — The actual recommendation architecture. How the algorithm decides what you hear next.

I Fed Every Beach House Lyric Into an AI — Pattern analysis on a discography. What the model found that I hadn’t noticed.

The Algorithm Listens – Analyzing Every Lorde Lyric — The same treatment for Lorde. Linguistic and thematic patterns across her catalog.

The Hypnotic World of Haruki Murakami — What makes his prose work, and why it shouldn’t work as well as it does.

Why the Next Decade Will Rewrite Human Civilization — The macro argument. Where AI, energy, and geopolitics are converging and what it means.

📖 Full Archive

Everything is at blog.atharvashah.com/archive.

Posts go out when there’s something worth saying. Dense, not frequent. Every post links to related ones. The archive is coherent, not a pile of one-off takes.

🔗 Find Me Elsewhere

• 🐦 X / Twitter: x.com/cultist_dev

• 💼 LinkedIn: linkedin.com/in/atharva-shah-tech

• 🐙 GitHub: github.com/HighnessAtharva

• 🎬 Letterboxd: letterboxd.com/highnessatharva

• 🎵 Last.fm: last.fm/user/highnessatharva

• 🌐 Website: atharvashah.com

• 📧 Email: hi@atharvashah.com — paid work and real conversations only

Open to web development, AI automation, API integrations, technical content, GTM consulting, and DevRel work. Details at atharvashah.com.

I drowned myself in building a knowledge OS, not because it was trendy, but because I got tired of renting my brain to other people’s servers. Every note in Notion, Evernote, or Google Docs lives on someone else’s machine. You pay monthly for the privilege. If they pivot, raise prices, or shut down, you scramble. You export. You lose context.

I wanted something different. A system where I own the data. Where files sit on my hard drive as plain Markdown. Where no company can hold my knowledge hostage. And where every note compounds with the next one. Every connection surfaces something I forgot I knew.

This is how I built it, and why it’s now generating 4-5x the content output while requiring less manual effort.

The Philosophy (Locality, Simplicity, Permanence)

I built infrastructure on purely three major pain points and decisions:

1. Locality. Every note is a .md file in d:\Atharva\NOTES. If Obsidian dies, the vault survives. Text files outlive apps, companies, platforms.

2. Start fresh. I didn’t import old Docs chaos. I let the structure earn its place. You can’t organize chaos better. You can only recognize it.

3. Never delete. Notes go to Archive, not trash. Storage is cheap. Regret costs more.

The math is different from SaaS. Pay once for Obsidian (or use it free) and your files stay yours. No monthly rent. No proprietary format. No platform dependency.

Prefer the Video Version? Here’s A Quick Demo

The Foundation = File System Architecture

his vault looks overwhelming at first. It’s not. It’s flat and intentional. Bury ideas three directories deep and they die.

Structure I use:

• Root (.claude, .vscode, README.md, CLAUDE.md) — Config and workflows

• INBOX — Raw captures. Active. Unpolished.

• DAILY — One file per day. Work tasks, notes, things I want to remember.

• DIGITAL TWIN — Everything about me: voice, audience, experience, goals, principles. The grounding layer.

• SUBSTACK — Ideas → Drafts → Published

• SOCIALS — Twitter, LinkedIn, Shorts, Substack Notes (one per channel)

• LIBRARY — Stable reference. Glossary, lists, resources.

• META — Engine room. Templates, Copilot memory, Excalidraw, graphify.

I pin crucial folders with underscore prefixes (_INBOX) so they float to the top of file explorer. Iconize plugin adds folder emojis. Scanning the sidebar is instant.

Below that sits META, the engine room. This holds my templates, web clippings, Copilot prompt files, and Excalidraw drawings. One of the most important thing it holds is the templates used by the Templater plugin.

I built an HTML visualization to make sense of this without forcing everything into one page. Vault Atlas has separate views for structure, publishing, automation, and recovery. It’s there for when you forget where things live.

The System Model Has Four Layers

The vault behaves like an OS with four layers:

1. Capture (INBOX + DAILY) — Loose input and traces

2. Identity (DIGITAL TWIN) — Voice, audience, principles, experience

3. Publishing (SUBSTACK + SOCIALS) — Long-form source plus the distribution flywheel

4. Infrastructure (META + .claude + config) — Attachments, automation, skills, workspace behavior

The Visualizations Show A Correlation Graph of All My Notes and Content Assets

Now here's where it gets powerful. I use Graphify to create a knowledge graph that auto-clusters my 2000+ files. The graph identifies patterns and trends. It correlates files you didn't consciously link.

Zoom in on any node and you see its full neighborhood. The info panel shows file type, community, source path, degree (number of connections), and every neighbor by name. A single article can have 20 direct connections spanning drafts, social posts, and related published pieces. Every arrow is a real connection. The more you write, the denser this map becomes.

I started this as an Obsidian project, but I use GitHub Copilot in VS Code now because the connection visualization is tighter and the file scanning is faster.

The structural breakdown:

• Mission Control (Root) — Navigation and config

• Capture (INBOX) — Active scratch space

• Chronology (DAILY) — Permanent timeline of what happened

• Grounding (DIGITAL TWIN) — Voice, audience, experience, goals (read before generating AI content)

• Publishing Spine (SUBSTACK) — Ideas → Drafts → Published

• Distribution (SOCIALS) — LinkedIn, Twitter, Substack Notes, Shorts

• Durable Knowledge (LIBRARY) — Glossary, lists, resources, PDFs

• Infrastructure (META) — Templates, Copilot memory, Excalidraw, graphify

Each has rules. Drafts are rough; published pieces are final. Library is stable; Meta supports. INBOX stays temporary. This prevents chaos and stagnation.

The Grounding Layer Is My Digital Twin Folder

Most AI outputs sound generic because the AI doesn’t know what you sound like.

I have a DIGITAL TWIN folder with:

• voice.md — Writing style, banned words, sentence rhythm, what constitutes slop

• audience.md — 17 archetypes with pain points and buying triggers

• experience.md — 9 competency pillars

• goals.md — What I’m shipping, in progress, unchecked

• principles.md — Values and decision filters

When an agent generates a blog post in “my voice,” it reads voice.md first. When it suggests a content angle, it checks audience.md and experience.md.

The identity lives in files, not in prompt memory. That’s why outputs don’t feel like they were generated.

Bringing In The AI Automation Layer With Github Copilot

The vault isn’t passive. It’s programmable. Four components:

• Grounding (DIGITAL TWIN) — Voice, audience, experience, goals, principles

• Infrastructure (META) — Attachments, clippings, Copilot memory, templates, graphify

• Workflow engine (.claude) — Agents for orchestration, skills for transformations

• Editor behavior (.obsidian, .vscode) — Plugin behavior, MCP setup, workspace settings

The Social Flywheel

When I publish a Substack article, one piece of content automatically becomes:

1. A tweet thread

2. A LinkedIn carousel post

3. A Substack Note

4. A video script

The critical principle here is don’t over-folder. If you bury ideas three directories deep, they die in silence. Instead I use Maps of Content - plain notes that act as hubs, listing links to other notes on a topic. They’re like a table of contents you build as you go, and they flex as your thinking evolves. Folders are rigid. MOCs are alive.

Then Daily Journal for chronological anchoring - one file per day, auto-generated.

Live Demos of What My Vault Can Actually Do

Query 1: What are my competency pillars?

The AI doesn't search 2000 files. It reads experience.md and answers in seconds.

Query 2: Rewrite a sentence in my voice

It reads voice.md, spots banned words (”leverage,” “cutting-edge,” “unlock”), explains why they fail, rewrites direct and specific.

Query 3: What happens after I publish a Substack article?

Layer 1: The article goes live, subscribers get notified. Layer 2: Run the flywheel agent, get 4 social assets in parallel.

Query 4: How many blog posts about AI cost reduction?

It checks the published folder, scans for relevant files, returns titles. No hallucination.

Query 5: What was I supposed to finish in Q1?

It reads goals.md and cross-references project files. Shows what shipped, what’s in progress, what stalled.

Beyond the Basics: Advanced Workflows

Workflow: The Social Flywheel in Action

Once an article publishes, the flywheel runs automatically. The dashboard shows each article and its downstream social outputs in real time. No manual steps. No forgotten platforms.

Workflow: Graph-Driven Ideation

When I’m stuck on what to write next, I zoom into the graph. A single article node connects to research notes, related pieces, audience archetype files, and competitive analysis. The system shows me what I’ve already built nearby. I don’t start from zero.

Workflow: The Content Velocity Dashboard

The metrics dashboard tracks what the system actually generates. Not time spent or tasks completed. Outputs. Monthly velocity is stable. The system compounds.

Final Thoughts

I don’t sit down and “write.” I capture, structure, refine, and distribute. The system knows who I am before it touches a keyboard. Every output filters through my voice, my audience, my competencies.

The deeper you build it, the more it knows you. The more it knows you, the faster you work.

Plain text doesn’t lock you in. Open it in Notepad 30 years from now on any OS and it still works. Try that with Notion.

The Graph View revealed patterns I didn’t make consciously. I linked a cold email note to a content flywheel note, and the graph showed they both connected to an audience psychology note I’d written weeks before. That emergent structure doesn’t happen in tools where notes live isolated.

Everything in one place. Code, long-form, checklists, diagrams, journal entries, plans. One vault. One search. One backup. The cognitive overhead of “where does this go” drops to zero.

I invested heavily in this infrastructure. I’m not abandoning it.

Leave a comment

Every New Laptop Costs You a Full Day

You get a new laptop. Exciting for about ten minutes. Then reality hits.

You spend the next eight hours downloading browsers, editors, terminals, media players, and CLI tools one by one. You hunt for config files scattered across AppData folders. You rebuild your VS Code settings from memory. You forget half your browser extensions. By midnight you’re still not back to where you started.

I got tired of this cycle. So I built a migration kit - a system that takes me from a fresh Windows install to my exact working environment in under an hour. No Microsoft Store. No manual downloads. No guesswork. One script installs everything. Another script restores every config, theme, and shortcut right where it belongs.

This is that system.

The Software Stack

Here is every tool that goes on my machine, grouped by what it does. This is the master list that feeds into the automated installer script later.

1. Productivity and Communication. Obsidian is the foundation - my second brain, my vault, my entire knowledge system. TickTick handles task management. For communication, it’s Slack for work, Discord for communities, and Telegram for everything in between. Flow Launcher gives me keyboard-driven quick access to files and apps without touching the mouse. QuillBot rounds it out for writing and paraphrasing.

2. Browsers and Research. Brave is my primary browser - privacy-focused, fast, and Chromium-compatible. For AI-assisted research, I keep Perplexity, Claude, and ChatGPT available as web apps. Proton VPN handles secure browsing when I need it.

3. Development and Terminal. VS Code is the primary editor. Sublime Text stays around for fast, lightweight file editing when I don’t need a full IDE. Docker handles containerization. Node.js and Python are the core runtimes. MongoDB and SQLite cover local database needs.

4. Media and Creativity. VLC plays everything. Audacity handles audio editing. MediaMonkey 5 manages my music library with metadata intact. OBS Studio records and streams. Upscayl does local AI-powered image upscaling. qBittorrent handles downloads.

5. System and Utilities. WizTree finds large files and frees up disk space fast. SyncThing is the backbone of the entire migration system - peer-to-peer file sync across machines with no cloud middleman. CCleaner cleans up system junk. PDF24 Creator handles offline PDF merging, splitting, and editing. Calibre manages my ebook library.

The Command Line Arsenal

The GUI apps are only half the picture. The real power lives in the terminal.

FFmpeg, yt-dlp, Gallery-DL, and ImageMagick are staples - they handle media conversion, video downloading, gallery scraping, and image processing respectively. But five more CLI tools round out the kit.

1. Rclone is the Swiss Army knife for cloud storage, syncing files to Google Drive, Dropbox, and dozens of other providers straight from the command line.

2. Pandoc converts between markup formats - Markdown to PDF, Markdown to Docx, whatever you need.

3. Zoxide replaces the cd command with something smarter that learns your habits and lets you jump to any directory by typing a few letters.

4. Ripgrep searches text across entire codebases and vaults at absurd speed.

5. Bat is a better cat - syntax highlighting, line numbers, and Git integration built in.

Every one of these installs through a package manager. No hunting for download pages.

The Two-Tier Strategy

To make this truly plug-and-play, the system has two layers. The first is the engine - Winget installs the software binaries. The second is the soul - SyncThing plus symlinks restore your actual settings, themes, and databases. Installing the apps gets you 60% there. Restoring the configs gets you the remaining 40% that makes it feel like your machine.

The Automated Installer (bootstrap.ps1)

This script uses Winget to install the entire stack in one shot. Every app from the list above is mapped to its correct Winget package ID.

# Run as Admin check
if (!([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
    Write-Error "Run this script as Administrator!"; return
}

$apps = @(
    # Productivity
    "Obsidian.Obsidian", "TickTick.TickTick", "Slack.Slack", "Discord.Discord",
    "Telegram.TelegramDesktop", "Flow-Launcher.Flow-Launcher",

    # Browsers & VPN
    "Brave.Brave", "Proton.ProtonVPN",

    # Dev & Terminal
    "Microsoft.VisualStudioCode", "SublimeText.SublimeText.4", "Docker.DockerDesktop",
    "OpenJS.NodeJS", "Python.Python.3.12", "MongoDB.Server", "SQLite.SQLite",

    # Media & Creativity
    "VideoLAN.VLC", "Audacity.Audacity", "VentisMedia.MediaMonkey",
    "obsproject.obs-studio", "Upscayl.Upscayl", "qBittorrent.qBittorrent",

    # Utilities
    "AntibodySoftware.WizTree", "Syncthing.Syncthing", "Piriform.CCleaner",
    "PDF24.PDF24Creator", "kovidgoyal.calibre",

    # CLI Power Tools
    "Gyan.FFmpeg", "yt-dlp.yt-dlp", "mikf.gallery-dl", "ImageMagick.ImageMagick",
    "Rclone.Rclone", "JohnMacFarlane.Pandoc", "ajeetdsouza.zoxide",
    "BurntSushi.ripgrep.MSVC", "sharkdp.bat"
)

foreach ($app in $apps) {
    Write-Host "Installing $app..." -ForegroundColor Cyan
    winget install --id $app --silent --accept-source-agreements --accept-package-agreements
}

Run that as admin, walk away for 15 minutes, and come back to a fully loaded machine. Thirty-plus apps, zero clicks.

What Makes It Actually Plug and Play

Installing apps is the easy part. The hard part is making them feel like yours. That means restoring settings, themes, keybindings, and databases. SyncThing keeps a folder called C:\Backup\Config synced across all your machines. The table below maps exactly which paths need to be tracked for each tool.

If it’s not on this list, it doesn’t need special treatment - Winget handled it. If it is on this list, the next script handles it automatically.

The Symlink Restore Script (restore_settings.ps1)

Once SyncThing has downloaded your C:\Backup\Config folder to the new machine, this script does the rest. It creates symbolic links that fool Windows into thinking the settings are in their normal locations, while they actually live in your synced folder.

# Define where your synced configs live
$syncFolder = "C:\Backup\Config"

# Function to create the link
function Set-Link($appPath, $backupPath) {
    if (Test-Path $appPath) { Remove-Item -Recurse -Force $appPath }
    New-Item -ItemType SymbolicLink -Path $appPath -Target $backupPath
}

# Apply Links
Write-Host "Restoring App Settings via Symlinks..." -ForegroundColor Green

# 1. VS Code Settings
Set-Link "$env:APPDATA\Code\User" "$syncFolder\vscode"

# 2. Flow Launcher (Everything: plugins, history, themes)
Set-Link "$env:APPDATA\FlowLauncher" "$syncFolder\FlowLauncher"

# 3. yt-dlp Global Config
Set-Link "$env:APPDATA\yt-dlp" "$syncFolder\yt-dlp"

# 4. Git Config (Crucial for your dev work)
Set-Link "$env:USERPROFILE\.gitconfig" "$syncFolder\git\.gitconfig"

After this runs, you open VS Code and your theme is there. Your keybindings are there. Flow Launcher has your plugins. Git knows who you are. It all just works.

Things That Need Special Treatment

Not everything plays nice with symlinks.

1. Obsidian stores its config inside the vault itself - the .obsidian folder holds your themes, plugins, and appearance settings. You don’t symlink Obsidian’s AppData. You just point the app at your synced vault on the new machine, and everything comes with it.

2. Brave and other Chromium browsers encrypt some profile data in ways that are tied to the specific machine. Symlinks can break login sessions and saved passwords. The safer move is to use Brave Sync for extensions and bookmarks, and keep a manual export of your Bookmarks file in your backup folder as insurance.

3. Python and Node.js don’t have meaningful config files to sync. What they need is their global packages. Add your npm install -g and pip install commands to the end of bootstrap.ps1 so they run as part of the same automated setup.

Taking It Further With a Dotfiles Repository

The SyncThing approach works. But a GitHub repository transforms your setup from a manual backup into a proper dotfiles system. You get version history for every config change, the ability to roll back mistakes, and a single git clone command to deploy your entire environment on any new machine.

The Repository Layout

Create a repository called dotfiles-windows with this layout:
├── scripts/
│ ├── bootstrap.ps1 # Installs all apps (Winget)
│ └── restore.ps1 # Creates the symlinks
├── configs/
│ ├── vscode/
│ │ ├── settings.json
│ │ └── keybindings.json
│ ├── flow-launcher/ # Folder for Flow settings
│ ├── git/
│ │ └── .gitconfig
│ └── obsidian/ # Optional: Global snippets or CSS
├── .gitignore # CRITICAL: Prevents pushing secrets
└── README.md # Instructions for your future self

Everything text-based and non-sensitive goes here. Your scripts, your JSON configs, your Git settings. The repo becomes a single source of truth.

The Smart Gitignore

App data directories contain tokens, machine-specific paths, and database files you don’t want in version control. This .gitignore keeps the repo clean and safe

# Ignore local databases and logs
*.log
*.db
*.sqlite

# Ignore sensitive VS Code data
configs/vscode/backups/
configs/vscode/workspaceStorage/

# Ignore actual Obsidian Vaults (Keep those in Syncthing/Proton Drive)
# Only track global Obsidian CSS or templates here if desired.
vaults/

# Ignore sensitive Git credentials
.git-credentials

One-Command Deployment

With the repo set up, your entire migration on a new laptop becomes a single line:

git clone https://github.com/YourUsername/dotfiles-windows.git C:\dotfiles; & C:\dotfiles\scripts\bootstrap.ps1; & C:\dotfiles\scripts\restore.ps1

Clone the repo. Install all apps. Restore all configs. Done.

The restore.ps1 in the repo is smarter than the standalone version - it detects where it’s running from and resolves paths automatically:

$repoRoot = (Get-Item $PSScriptRoot).Parent.FullName
$configSource = "$repoRoot\configs"

function Set-Link($targetPath, $sourcePath) {
    if (Test-Path $targetPath) {
        Write-Host "Backing up existing config for $(Split-Path $targetPath -Leaf)..."
        Move-Item $targetPath "$targetPath.bak" -Force
    }
    # Ensure the parent directory exists
    $parentDir = Split-Path $targetPath -Parent
    if (!(Test-Path $parentDir)) { New-Item -ItemType Directory -Path $parentDir }

    New-Item -ItemType SymbolicLink -Path $targetPath -Target $sourcePath
    Write-Host "Linked: $targetPath" -ForegroundColor Gray
}

# -- Execute Links ---
Write-Host "Linking configurations from $configSource..." -ForegroundColor Cyan

# VS Code
Set-Link "$env:APPDATA\Code\User\settings.json" "$configSource\vscode\settings.json"

# Git
Set-Link "$env:USERPROFILE\.gitconfig" "$configSource\git\.gitconfig"

# Flow Launcher
Set-Link "$env:APPDATA\FlowLauncher\Settings" "$configSource\flow-launcher\Settings"

Write-Host "Migration Sync Complete!" -ForegroundColor Green

This version also backs up existing configs before overwriting them, so you never lose anything.

Keeping It Updated

The symlinks make maintenance dead simple. When you change a setting - say you switch your VS Code theme - the file in C:\dotfiles\configs updates automatically because it’s the same file. All you do is commit and push:

cd C:\dotfiles
git add .
git commit -m "Updated VS Code theme"
git push

Your dotfiles stay current with zero extra effort. Every machine pulls the latest version on the next sync.

GitHub vs SyncThing - When to Use Which

Both tools have a role. The right choice depends on what you’re syncing.

Use GitHub for the logic - scripts and small text-based configs where you want version control and rollback. Use SyncThing for the data - your Obsidian vault, images, media libraries, and local databases where you want seamless, set-and-forget synchronization. Running both gives you the best of each world.

Leave a comment

The Invisible Tax on Every Vibe-Coded App

You shipped the app. The landing page is tight. The product works. And nobody is finding it.

This is the silent failure mode of vibe coding. You prompt an AI to build your entire React app in an afternoon. It generates clean components, handles routing, even sets up a decent UI. What it does not do - what it will never do unprompted - is make any of it discoverable.

No meta tags. No sitemap. No semantic HTML structure. No OpenGraph cards. No JSON-LD schema. No alt text on images. No canonical URLs. The app is technically alive and functionally invisible.

Search engines see a blank shell. Social platforms render a generic link preview. AI crawlers find nothing worth indexing. You have built a storefront with no sign on the door.

Why This Happens

AI code generators optimize for function, not findability. When you ask Claude or GPT to “build me a portfolio site” or “create a SaaS landing page,” the model focuses on what the user sees in the browser. Title tags, meta descriptions, structured data - these are invisible to the user, so they are invisible to the model’s priorities.

The result is a pattern I see constantly. Founders vibe-code an MVP, ship it, start running ads, and wonder why organic traffic is zero. The answer is almost always the same. The app has no SEO foundation whatsoever.

This is not a minor oversight. Organic search is the single highest-ROI acquisition channel for most software products. Paid ads stop working the moment you stop paying. SEO compounds. A properly optimized page can generate traffic for years. But only if the technical foundations exist.

The Cost of Doing Nothing

Here is what happens when you skip SEO on a vibe-coded app.

Google cannot understand your page hierarchy because every element is a div inside a div inside a div. There is no semantic structure telling crawlers what the page is about.

Social sharing falls flat. When someone drops your link on Twitter or LinkedIn, there is no OpenGraph image, no title, no description. Just a bare URL. Click-through rates plummet.

AI search engines - the ones increasingly replacing traditional search for discovery - cannot index your content because it requires JavaScript execution to render, and you have provided no structured data to make it crawl-ready.

Your competitors who spent ten minutes on SEO are outranking you for every keyword that matters. Not because their product is better. Because their product is findable.

What These Prompts Actually Do

I built two prompts that fix this entire problem. They are designed to be dropped directly into an AI coding agent - Claude, Cursor, Copilot, whatever you use - and pointed at your React codebase. The first one audits and fixes. The second one documents everything it did.

The audit prompt follows a strict four-phase execution model. It crawls your project structure, identifies every public-facing route, and builds a complete SEO plan before touching a single file. This is critical. You do not want an AI blindly injecting meta tags without understanding your site architecture first.

Phase one maps your routes and proposes a strategy. Phase two builds the technical infrastructure - robots.txt, sitemap, dependency setup. Phase three optimizes every page with unique meta tags, OpenGraph cards, semantic HTML, and clean URLs. Phase four handles performance - lazy loading, dynamic meta generation for parameterized routes, JSON-LD schema for AI crawlers.

The prompt also includes a safety constraint. It generates a plan file first and waits for your approval before modifying any application code. You stay in control.

Prompt 1 - The SEO Audit and Fix

Drop this into your AI coding agent with your React project loaded. It will analyze your codebase, generate an SEO plan, and then implement fixes across every route.

Role: You are an Expert Senior Full-Stack Engineer and SEO Specialist.

Task: Perform a comprehensive SEO overhaul of this React workspace. You must follow a strict "Plan-First" execution model.

Phase 1: Analysis & Documentation
Crawl the Project: Scan the /src folder, especially routes (e.g., App.js, routes.tsx, or react-router configs) to identify every public-facing page.

Sitemap Audit: Locate or create a strategy for a dynamic sitemap.xml.

Deliverable: Create a file named SEO_PLAN.md documenting:

A list of all identified routes.

The proposed robots.txt configuration.

A plan for implementing react-helmet-async for head management.

A strategy for OpenGraph (OG) tags and structured data (JSON-LD).

Phase 2: Technical Infrastructure
Robots & Sitemap: Generate a robots.txt in the /public folder. Create a script (or a manual sitemap.xml) that includes all routes found in Phase 1.

Dependency Setup: Install react-helmet-async.

Global Provider: Wrap the application in the HelmetProvider at the root level.

Phase 3: Page-Level Optimization
For every page component identified:

Meta Tags: Add unique <title> and <meta name="description"> tags.

Social Graph: Implement OpenGraph (og:title, og:description, og:image) and Twitter Card tags.

Semantic HTML: Review the JSX. Ensure the page uses a logical heading hierarchy (<h1> for main titles, <h2> for sections) and semantic tags (<main>, <article>, <nav>).

Clean URLs: Ensure all Link components use human-readable slugs.

Phase 4: Performance & Programmatic SEO
Image Optimization: Identify <img> tags and suggest/implement loading="lazy" and descriptive alt text.

Dynamic Routes: If the app uses dynamic parameters (e.g., /products/:id), create a pattern to generate unique meta tags based on the data being fetched.

Optimize all page Title Tags to fall between 50–60 characters and implement a site-wide JSON-LD 'Organization' and 'WebPage' Schema to clarify brand identity for LLMs and search engines. . Ensure all critical brand and service information is 'crawl-ready' without requiring JavaScript execution to prevent data loss during AI indexing.

Constraints:

Do not break existing CSS or functional logic.

Use react-helmet-async instead of the legacy react-helmet.

Prioritize "Human-Readable" code and SEO-friendly URL structures.

Wait for my approval on SEO_PLAN.md before modifying any application files.

Why the Plan-First Approach Matters

Most people would just tell an AI to “add SEO to my app.” That is a mistake. Without a plan phase, the AI will make assumptions about your site structure, duplicate meta descriptions across pages, and miss routes entirely.

The plan-first constraint forces the AI to do analysis before implementation. You get a document you can review. You can catch issues like missing routes or incorrect keyword targeting before any code changes happen. This is the difference between a professional SEO implementation and a slapdash one.

Prompt 2 - The SEO Report Generator

After the audit prompt has done its work, run this second prompt. It compares the before-and-after state of your codebase and generates a professional report documenting every change, why it was made, and how it impacts your search performance.

This is not just documentation for documentation’s sake. If you are building for a client, this report is a deliverable. If you are building for yourself, it is a reference you will need six months from now when you are wondering why a particular meta description was chosen or what schema type was applied to a specific page.

The report covers five areas. An executive summary comparing SEO health before and after. A log of every new file created and why. A page-by-page breakdown of every tag, keyword, and semantic improvement. An architecture log explaining dependency choices. And a performance section detailing Core Web Vitals impact.

**Role:** You are a Senior Technical SEO Auditor.

**Task:** Conduct a post-implementation review of the SEO overhaul performed on this React workspace. You must generate a professional, comprehensive report named `SEO_REPORT.md`.

**Scope of Analysis:**

1. Compare the current state of the `/src` and `/public` folders against standard React SEO best practices.

2. Identify every component where `react-helmet-async` or SEO meta tags were added.

3. Identify all new files created (e.g., `sitemap.xml`, `robots.txt`, `SEO_PLAN.md`).


**Report Structure Requirements:**

### 1. Executive Summary

- Provide a high-level overview of the SEO health of the application before vs. after implementation.


### 2. Technical Infrastructure Changes

For every **New File** created (e.g., `robots.txt`, `sitemap.xml`):

- **File Path:** [Path to file]

- **Purpose:** Why was this specific file created?

- **Impact:** How does this file affect search engine crawlers (indexing, crawl budget, etc.)?


### 3. Page-by-Page Breakdown

Create a section for **every page/route** modified. For each page, document:

- **Component Name & Path:**

- **Elements Added:** List specific Tags (Title, Meta Description, OG Tags, Schema.json).

- **Technical Decisions:** Why was this specific keyword or description chosen for this route?

- **Semantic Improvements:** Note if tags like `<div>` were changed to `<main>`, `<article>`, or if `<h1>`-`<h6>` hierarchy was corrected.

- **SEO Impact:** Explain how these specific changes improve the "Relevancy Score" for that page.


### 4. Dependency & Architecture Log

- **Library Choice:** Document the use of `react-helmet-async`.

- **Decision Logic:** Why did we use an asynchronous head manager instead of standard React state? (Mention thread safety and SSR compatibility).

- **Global Configuration:** Detail the `HelmetProvider` implementation at the root level.


### 5. Performance & Accessibility (A11y)

- List improvements made to `<img>` alt tags and `loading="lazy"` attributes.

- Explain how these changes impact Core Web Vitals (LCP, CLS).


**Tone:** Professional, technical, and data-driven. Use tables where appropriate to compare "Before" and "After" states for meta-titles and descriptions.

**Final Output:** Save all of this into `SEO_REPORT.md` in the root directory.

How to Use These Together

The workflow is simple. Open your vibe-coded React project in your AI coding environment. Paste the first prompt. Let it generate the SEO plan. Review the plan, make adjustments if needed, then approve it. The AI implements all the fixes.

Once that is done, paste the second prompt. It scans the changes and generates a complete audit trail. You now have a fully SEO-optimized app and a professional report documenting exactly what was done and why.

The entire process takes maybe thirty minutes. The alternative - hiring an SEO consultant to manually audit a React app - costs thousands and takes weeks. These prompts give you 80% of that output at effectively zero cost.

Beyond React

These prompts are written for React with react-helmet-async, but the underlying principles apply to any framework. If you are using Next.js, swap the helmet references for the built-in Head component. If you are using Astro or SvelteKit, adapt the meta tag strategy to their native patterns. The four-phase structure - analyze, build infrastructure, optimize pages, tune performance - works regardless of your stack.

The real insight here is not about React or any specific framework. It is that vibe-coded apps have a systematic blind spot around discoverability. Every AI-generated codebase needs a post-generation SEO pass. These prompts make that pass repeatable and thorough.

Ship fast, then make it findable. That is the order of operations.

Leave a comment

Most marketing teams burn budget trying to manufacture interest. They write blog posts nobody asked for, run ads against cold audiences, and spray cold emails into inboxes where they die unread. The entire model is built on interruption. You are creating demand from zero, hoping that if you shout loud enough, someone in your ICP will eventually turn around.

There is an alternative. And it is brutally more efficient.

Instead of generating demand, you capture it. You find the people who already want what you sell - right now, today, in this thread, in this comment section - and you show up with the exact answer they are looking for. The cost difference is staggering. Demand generation is expensive because you are fighting inertia. Demand capture is cheap because the buyer already did the hard part for you. They raised their hand. They typed their pain into a search bar or a Reddit post. All you have to do is be there.

This is what social listening for lead generation actually looks like when it is done right.

The Economics Nobody Talks About

Think about what a single qualified lead costs you through outbound. You are paying for a sales rep’s time, a sequencing tool, data enrichment, and the opportunity cost of every email that bounces or gets ignored. A conservative estimate puts a single outbound-qualified meeting at $200-500 in fully loaded cost. Most of those meetings go nowhere.

Now compare that to intercepting a Reddit thread where a VP of Engineering is publicly asking “What CNAPP tools actually do runtime visibility well?” That person is already in-market. They have budget context. They have a problem that hurts today, not hypothetically. The cost to engage? Nearly zero. A well-crafted reply that adds genuine value. No ad spend. No sequence. No prayer.

The ROI math is not even close. Demand capture converts at 3-5x the rate of cold outbound because context and timing are already on your side. You are not convincing someone they have a problem. You are solving one they already articulated.

Reading the Room - Three Signals That Matter

Not every social post is worth engaging. The skill is in reading intent. After running this playbook across hundreds of threads, three signal patterns emerge that consistently convert.

The highest-intent signal is competitor frustration. Someone writes “We are moving off [Competitor] because their runtime visibility is lacking - any alternatives for CNAPP?” That person is not browsing. They are buying. They have already made the decision to leave. Your job is to show up with a direct comparison that focuses on the exact capability they just said is missing, and offer a migration path that feels effortless. This is the closest thing to a layup in B2B marketing.

The second signal is technical problem-solving. A post like “How are people securing LLM agents against prompt injection in production?” tells you someone is building right now and hitting a wall. They do not want a pitch. They want an architecture diagram, a code snippet, or a link to something that actually explains the solution. You provide that, and you have positioned your tool as the infrastructure layer beneath their entire stack. The sale comes later. The trust starts here.

The third signal is category research. “What is the actual difference between Agentic Security and traditional CSPM?” - this is someone early in their journey, trying to build a mental model. An educational response that defines the category clearly puts you in the position of the authority who shaped how they think about the space. When they are ready to buy three months from now, your name is the first one in their head.

Scoring Signals So Your Team Stops Wasting Time

Raw signal volume will overwhelm any sales team. You need a scoring layer that filters noise from opportunity. Every lead that surfaces through social listening gets processed through four dimensions before anyone touches it.

Relevancy score runs from 0 to 100 and measures how closely the keywords and sentiment in a post align with your core product offering. A post mentioning your exact category and a competitor by name scores high. A vague question about “cloud security” scores low. This alone eliminates 70% of the noise.

User authority matters enormously. The system analyzes the poster’s profile - LinkedIn title, Reddit post history, community reputation - to determine whether they are a researcher doing preliminary homework or a decision maker with purchasing power. A CISO asking a question on LinkedIn is a fundamentally different signal than an intern posting on r/cybersecurity.

Thread velocity tracks engagement. A post with 47 comments and climbing means hundreds of lurkers are reading it. Your reply in that thread is not a one-to-one conversation. It is a one-to-many broadcast, and every person reading it is self-selected for interest in the topic.

Sentiment analysis differentiates between casual curiosity and genuine pain. “Just wondering about X” is neutral. “We are hemorrhaging money because X does not work” is urgent. The scoring matrix weights urgency heavily because frustrated buyers move fast.

From Anonymous Handle to Pipeline

Here is where most social listening efforts fall apart. They generate engagement but never connect it to revenue. The gap between an anonymous Reddit username and a qualified opportunity in your CRM feels impossibly wide. It is not.

The workflow has four steps. First, discovery - you identify a high-intent post on Reddit, X, or LinkedIn using the signal patterns above. Second, de-anonymization - social enrichment tools map the handle to a real-world identity and company. This is not magic. People reuse usernames, link profiles, and leave digital breadcrumbs everywhere. Third, intent verification - you check whether the company is already on your Target Account List or currently using a competitor. This step prevents you from wasting effort on accounts that will never close. Fourth, multi-channel follow-up that works two angles simultaneously.

The public angle is your reply in the thread itself. This captures the lurker audience - the 90% of people who read but never post. Your reply is not for the person who asked the question. It is for the three hundred people silently reading the answers. The private angle is a LinkedIn message or email that references the specific technical question they asked publicly. “I saw your post about runtime visibility gaps - we actually solved that exact problem for [similar company]. Happy to share how.” That message gets a response rate that would make your outbound team weep.

Why This Beats Cold Outbound on Every Dimension

The comparison is worth making explicit.

Cold outbound is an interruption. You are guessing that the timing is right based on a persona model that is probably six months stale. The trust factor is low because the recipient knows you want something from them. And the asset is ephemeral - that email gets deleted or ignored, and the work vanishes.

Social listening flips every single one of those dimensions. You are participating, not interrupting. Timing is not guessed - it is triggered by the buyer’s own behavior. Trust is high because you showed up with help, not a pitch. And here is the part most people miss: every reply you write is a permanent digital asset. That Reddit thread gets indexed by Google. It gets scraped by LLM training pipelines. Six months from now, when someone asks ChatGPT or Perplexity “What is the best CNAPP for runtime visibility?”, your brand shows up in the answer because you seeded the conversation that trained the model.

Guardrails That Keep This From Blowing Up

Running this at scale without guardrails is how you get banned from subreddits and roasted on Twitter. Three non-negotiables keep the operation clean.

Every response gets human review before it goes live. AI drafts the initial reply based on your ICP data and product positioning, but a human ensures the tone matches the community, the technical details are accurate, and the response does not read like a press release. The moment your replies start sounding like marketing copy, the strategy stops working.

Volume management matters more than most teams realize. You cannot have one brand account replying to every security thread on Reddit without getting flagged. The solution is a distributed network of technical evangelist profiles - real people with real expertise who genuinely participate in these communities. The engagement has to be authentic or it is worse than not engaging at all.

Safe-list monitoring prevents the most embarrassing failure mode: accidentally pitching your own customers. The system cross-references social handles against your existing customer database to ensure you never engage with someone who is already paying you in a way that disrupts their current support or success workflow.

The Compounding Machine

This is not a campaign. It is a compounding asset.

Every thread you participate in becomes a piece of search engine real estate. Social discussions rank on page one of Google for queries like Alternative to [Competitor]” and “[Product Category] reviews. Over time, you are not just capturing demand - you are shaping the information landscape that creates it.

The market intelligence feedback loop is equally valuable. Every thread is raw, unfiltered customer voice data. What features are competitors lacking? What problems keep coming up that nobody in the market addresses? That information flows directly into your product roadmap, and suddenly your social listening operation is not just a sales channel - it is the best product research tool you have.

And then there is the LLM optimization layer. Large language models are trained on web data. When you consistently show up in high-quality technical discussions across Reddit, LinkedIn, and X, you are seeding the training data for the next generation of AI models. The end state is that when someone asks an AI assistant to recommend a tool in your category, your brand is the default answer. Not because you paid for it. Because you earned it, one helpful reply at a time.

That is the real unlock. Outbound fills a quarter. Social listening builds a moat.

Leave a comment

TL;DR: Obsidian + Wispr Flow + GitHub Copilot. Own your data, speak your thoughts, transform everything. That’s it.

The Problem Nobody Talks About

Most creators in 2026 are drowning in tools. Twelve subscriptions. Four writing apps. Two AI chatbots. A calendar tool. A scheduling tool. A CRM they never update. And somehow, despite this entire arsenal, they still stare at a blank page every morning wondering what to write.

The stack is bloated. The output is anemic. Something is fundamentally broken.

Here is what is actually broken. Three things. First, writing is slow and you are burning out because you are forcing yourself to type every thought from scratch. Second, you turned to AI to help, and now you sound like every other LinkedIn ghost. Third, your ideas are scattered across a dozen apps with no connective tissue, no system, no compounding.

This article is about fixing all three with exactly three tools. Not a framework. Not a philosophy. Three pieces of software that cost you almost nothing and replace workflows that used to require a content team.

Obsidian. Your Brain, On Disk

Let’s start with where your ideas live. Right now, probably everywhere. Apple Notes. Google Docs. Random Slack messages to yourself. A Notion workspace you set up six months ago and haven’t touched since.

Obsidian changes this by doing something radical - it stores everything as plain Markdown files in a folder on your machine. Not in someone else’s cloud. Not in a proprietary database you can’t export from without three business days and a support ticket. Just text files. In a folder. On your hard drive.

This sounds boring until you realize what it unlocks.

You own the files. Completely. If Obsidian disappears tomorrow - if the company folds, if they pivot, if they paywall everything - your notes are still sitting in that folder. Copy them anywhere. Open them in any text editor. They are yours forever. No export gymnastics. No vendor lock-in. No “please download your data within 30 days” emails.

Markdown is also the native language of large language models. When you hand an LLM a Markdown file, it understands the structure instantly - headings, emphasis, lists, code blocks. No conversion needed. No reformatting. Your notes are already in the exact format AI works best with. This matters enormously for what comes next.

Everything lives in one searchable, linkable vault. Every idea you have ever captured, every draft, every prompt template, every reference - all of it searchable with a single keystroke. You can link notes to each other. You can build a graph of your thinking over time. You can run batch operations across hundreds of files because they are just files on a filesystem.

The graph view is nice. The backlinks are useful. The daily notes and templates are handy. But strip all of that away and the real power remains unchanged - your entire intellectual output lives in a folder you control forever, readable by any tool, owned by you alone.

Obsidian by itself will not change your life. But Obsidian as the foundation for everything else? That is what makes the rest of this stack devastating.

Wispr Flow. Speak at the Speed of Thought

Here is where most people lose the game. They have ideas - good ones, actually - but the bottleneck is the keyboard. Typing is slow. It is effortful. It introduces a filter between your brain and the page that kills momentum. By the time you have typed out paragraph three, you have forgotten the insight that was going to make paragraph seven brilliant.

Wispr Flow removes the keyboard from the equation. You toggle a hotkey, start talking, and watch accurate text appear in whatever application you are using. It is not just dictation - it cleans up your speech, handles punctuation intelligently, and produces genuinely readable text from natural, sometimes rambling, spoken thought.

What changes when you adopt this is hard to overstate. Medium-to-long pieces never require the keyboard again. I have essentially stopped typing for anything longer than a sentence. The writing sounds narrative and conversational, not robotic, because you are literally speaking out loud. That warmth and cadence is baked into the output automatically. You do not have to engineer it in post.

The velocity shift is staggering. Ideas that used to take 30 minutes to type now take 5 minutes to speak. A 10-minute voice note becomes a 2000-word rough draft. That is not an exaggeration. That is my Tuesday.

The workflow is dead simple. Open Obsidian. Create a new note. Hit the Wispr Flow hotkey. Start talking. Your thoughts flow directly into your vault in real time. When you stop talking, the text is just there - already in Markdown, already in your system, already searchable and linkable and ready for transformation.

One downside you must know about. If you speak for 10 minutes and it was not recording for whatever reason, that content is gone. No buffer. No recovery. No “restore last session.” Get in the habit of checking the indicator before long sessions. Lose one great rant and you will never forget to check again.

Use it for everything - notes, emails, prompts, drafts, brainstorms, meeting summaries, anything that requires more than a sentence. The friction of typing disappears, and with it, the resistance to capturing ideas. You start capturing more because it costs you almost nothing to capture.

GitHub Copilot. Transform Everything

You have your ideas in Obsidian. You spoke them in with Wispr Flow. Now you need to turn raw voice notes into finished content. This is where GitHub Copilot enters.

I use the GitHub Student Pack, which gives you access to Claude, GPT-4o, and Gemini - flagship models from every major provider - through a single interface. There is a monthly quota, but I have never come close to hitting it. Even without the student pack, the paid tier is a fraction of what you would spend subscribing to each model separately.

But the real value is not the chat interface. It is not asking Copilot random questions or having it debug your code. The real value is using your raw voice notes as input and running them through prompt templates to produce finished, voice-matched outputs.

Think about what one voice note can become. Five tweets that distill the core insight. A newsletter essay that expands on it with structure and nuance. A blog post with headers and scannable sections. A LinkedIn post with a different angle optimized for that audience. A PRD if the idea is product-shaped. An email pitch if it is outreach-shaped. You speak once and transform infinitely. The voice note is the raw material. The prompt templates are the machinery. The outputs are the products.

Here is the insight that makes this click - the AI does not create your ideas. It reshapes them into different containers. The thinking is yours. The unique perspective is yours. The formatting, structuring, and platform-specific optimization is automated. You are not outsourcing your brain. You are outsourcing the packaging.

The Workflow in Practice

Voice -> Obsidian -> Prompt Templates -> Polished Output

This is how the pieces connect in daily use.

You dictate into Obsidian using Wispr Flow. Raw thoughts, no editing, no self-censorship. Talk through the idea completely. Get the ugly first draft out of your head and into a file. You can let it sit or process it immediately - sometimes I revisit voice notes the next day with fresh eyes, sometimes I transform them within minutes. Both approaches work depending on the material.

Then you open GitHub Copilot and select the voice note file as context. The model can now see everything you said. You run it through a prompt template - “Turn this into a Twitter thread” or “Extract the core argument for a newsletter” or “Structure this as a blog post.” The model takes your raw thinking, shaped by your voice and your knowledge base, and formats it for the target platform.

You include your Knowledge Base folder so the output matches your voice, references your background, and speaks to your audience. More on this in the next section - this is where the stack goes from useful to unfair.

Finally, you edit the output. AI gives you 80 percent. You polish the remaining 20. That is still dramatically faster than starting from a blank page, and the 20 percent you add manually is precisely the part that makes the content yours.

The Knowledge Base Lock Yourself In

This is the secret weapon of the entire stack. Not the tools themselves, but the context layer that makes them irreplaceable.

Create a folder in your vault. Call it digital-twin, knowledge-base, whatever resonates. Fill it with files that define you. Not your resume - you. The way you think, the way you speak, the audience you serve, the principles you refuse to compromise on.

Here is what goes in it:

The critical design decision is this - keep your prompt templates generic. Do not hardcode your personality into them. Instead, pull personality from this digital-twin folder every time you run a transformation. One prompt template that says “Write a tweet thread about this topic” becomes YOUR tweet thread when the model has context about your voice, your audience, and your principles. The same template works for anyone who builds their own knowledge base. The personalization lives in the data, not the instructions.

Include this folder as context in every transformation prompt. The AI stops sounding generic and starts sounding like you, because it actually knows what “you” means. It knows your audience is early-career marketers, not enterprise CTOs. It knows you write short sentences, not compound paragraphs. It knows you believe in ownership over convenience.

Maintain these files as you evolve. New achievement? Add it to experience. Refined who you are writing for? Update the audience file. Changed your mind about something? Update principles. Your knowledge base grows with you, and the outputs improve automatically because the context improves.

This is also why I say “lock yourself in.” Not to a vendor - you own every file. Lock yourself into your own system. The more you invest in this knowledge base, the more valuable every transformation becomes. Your switching cost is not a subscription - it is the months of accumulated self-knowledge that makes your outputs uniquely yours.

Prompt Templates as a Transformation Library

Prompt templates are the last piece. Store them in Obsidian alongside everything else. Include your digital-twin folder using the @ directive in GitHub Copilot - every prompt automatically pulls your voice, principles, and audience context without you pasting anything manually. One template works everywhere. You sound like you across all formats.

Here are starting points.

For Twitter, the template is straightforward:

Take this voice note and extract 5 standalone tweets. Each should be punchy, under 280 characters, and capture one distinct insight. Use my voice and speak to my audience.

For newsletters, you want expansion and structure:

Transform this voice note into a newsletter essay. Open with a hook, develop the core argument, include a personal angle, and end with a clear takeaway. Match my writing style from the digital-twin folder.

For blog posts, you need scannable formatting:

Structure this voice note as a blog post. Add headers, break into scannable sections, and expand thin areas with relevant detail. Keep my voice throughout.

For LinkedIn, the framing shifts:

Reframe this idea for a LinkedIn audience. Professional but not corporate. Lead with the insight, add context, end with engagement. First-person, conversational.

For PRDs, you extract product thinking:

Extract the product thinking from this voice note. Structure as Problem, Proposed Solution, Key Features, Success Metrics, Open Questions.

The more templates you build, the more output you generate per hour of input. One 10-minute voice note becomes a week of content across platforms. The marginal cost of each additional piece of content approaches zero because the thinking was already done - you are just reshaping the container.

Why This Stack Wins

The math is simple. Look at what three tools replace:

The cost is essentially zero if you are a student. Obsidian is free for personal use. Wispr Flow has a free tier. GitHub Copilot is free with the student pack. Even without the student discount, the total cost is less than one month of a single enterprise SaaS tool. You are replacing an entire content team’s worth of output with three lightweight applications and a folder of text files.

You do not need 15 tools. You do not need a complex system with Zapier automations and three-step integrations. You need a place to store thoughts - Obsidian gives you local, LLM-ready files you own forever. You need a way to capture them fast - Wispr Flow lets you speak at the speed of thought. You need a way to transform them into anything - GitHub Copilot plus templates turns raw ideas into finished content.

Build the knowledge base. Collect the prompt templates. Speak your ideas. Then let the stack do the rest.

The people winning the content game in 2026 are not the ones with the most tools. They are the ones who capture more, own more, and transform more - with less friction at every step. This is the stack that makes that possible.

Leave a comment

What happens when your body becomes as disposable as a crashed Docker container? When death turns into a system reset, and your consciousness gets flashed onto a freshly printed vessel like firmware onto a new device?

Bong Joon-ho’s Mickey 17 is not a sci-fi thought experiment. It reads like a plausible engineering spec for how a collapsing society might ration human life. The story does not treat people as citizens. It treats them as deployable infrastructure. And the scariest part is how little imagination it takes to get there from where you are right now.

The Economics of Expendability

The story starts with debt. Not drama. Not cosmic stakes. Debt.

The film’s 2026 feels uncomfortably close. Widespread insolvency pushes past poverty into full systemic collapse across entire social layers. Earth hits resource limits. Unemployment spikes. And in that vacuum, a new job category appears - the Expendable.

Think of it as the gig economy pushed to its logical endpoint. You do not trade your time or your labor. You trade your body. Your life. You sign a contract. You get printed. You die. You get reprinted. You do it again.

Expendables function as biological telemetry probes. They walk into lethal environments so the protected population does not have to. They gather data from alien ecosystems, sample unknown pathogens for vaccine development, and stress-test terraforming viability before anyone important arrives. They are human test cases running in production, and the production environment will kill them.

If you have ever deployed a canary release - pushing a small slice of traffic through an untested path to see what breaks before you roll it out to everyone - you already understand the Expendable program. The difference is that the canary is a person.

Mind as Software, Body as Hardware

The central breakthrough in Mickey 17 is mind-body decoupling. The film calls them Cortex and Vessel, but if you have spent any time around infrastructure, the mapping is immediate.

The mind is a Docker image - a digitized brain state carrying memories, personality, and cognitive rules. The body is a container - a 3D-printed, replaceable biological runtime. Death is a terminated instance. You redeploy the same image onto fresh hardware and keep going.

The body becomes stateless and disposable. Identity lives entirely in the saved state. Your continuity depends not on your flesh surviving, but on the fidelity of your memory dump. If the backup is clean, you wake up as yourself. If it is not, you wake up as something else wearing your face.

This should feel familiar. A stable model runs across many deployments while the environment and substrate change underneath it. The person stays consistent across copies, as long as the state stays intact. Lose the state, and you lose the person. The hardware was never what mattered.

The Engineering Problem Nobody Talks About

This entire setup collapses unless you solve two hard engineering problems. The film glosses over both, which is exactly where it gets interesting if you think about it seriously.

Genetic fidelity. Every reprint needs 1:1 DNA replication. Drift across iterations degrades the vessel. Worse, it changes the brain substrate hosting the mind. A slightly different brain running the same cognitive image introduces subtle errors. Over enough reprints, Mickey N+1 is not the same person as Mickey N - not because the software changed, but because the hardware drifted. This is the biological equivalent of running the same application on increasingly divergent chipsets and expecting identical behavior.

Memory injection. The brain dump needs perfect continuity. Zero lost time between the death of Mickey N and the boot of Mickey N+1. Any gap creates discontinuity. Any corruption creates a different person who believes they are the original. And if the memory stream is unprotected - if someone intercepts and edits it - you are not just killing a person. You are rewriting who they wake up as.

That is not identity theft. That is identity hijacking at the firmware level. You cannot patch it after the fact because the person who would notice the tampering is the person who was tampered with.

The Race Condition That Breaks Everything

Here is where the architecture falls apart completely, and where the film finds its real tension.

What happens when two bodies get printed from the same brain image at the same time?

You get a race condition.

If you have built distributed systems, you know this failure mode. Two processes share a resource, both assume exclusive access, and neither knows the other exists until they collide. In Mickey 17, the shared resource is an identity. Two Mickey instances boot from the same snapshot, each carrying a full and legitimate claim to being the real continuation.

Which one has authority? Which one counts? The system was designed around single-instance governance - one Mickey at a time, no overlap, no ambiguity. The moment that assumption breaks, the entire design collapses.

A workable model would need hierarchy. A Prime - the original person used for the initial genetic sequence and brain scan - acts as the master node. The reprints are child pods. If the Prime dies, authority fails over to a designated child node through an explicit protocol. Without that protocol, you get identity collision. Two versions of the same person, each with an equal claim, each insisting the other is the copy.

This maps directly to split-brain behavior in distributed databases. Two nodes accept writes simultaneously, diverge from each other, and you cannot merge them back without data loss. In Mickey’s case, the data you lose is a human being.

The Horror of Normalization

The disturbing part of Mickey 17 is not the technology. It is how fast everyone accepts it.

Nobody in the film is horrified by the Expendable program for long. The ethics get processed, filed away, and overwritten by operational urgency. There is a mission. Resources are scarce. Someone has to die so the colony survives. The system works. So people stop questioning it.

This is the real warning, and it has nothing to do with 3D-printed bodies. You already live in a world that normalizes disposability. Gig workers with no benefits, contract soldiers in privatized wars, content moderators burning out so platforms stay clean. The distance between “acceptable cost of doing business” and “Expendable” is shorter than you think. Mickey 17 just removes the pretense by making the disposability literal.

The film forces questions that do not have clean answers. If you can copy a mind indefinitely, individual sovereignty dissolves - you are not a person, you are a template. If death is reversible, murder becomes an operational inconvenience rather than an irreversible act, and accountability evaporates with it. If humans become disposable, the only question left is who gets to set the disposal policy. And that question is always answered by whoever holds power, not by whoever holds a moral argument.

A society running this system needs governance around duplication, memory ownership, and the right to exist as a single instance. Without those guardrails, human life becomes a resource you allocate, scale, and terminate based on need.

What This Film Actually Gets Right

Mickey 17 warns about a trajectory that is already visible if you know where to look. Efficiency pressure, economic desperation, and technical capability converge into a system built on disposable people. The technology is fictional. The incentive structure is not.

The open question is governance. If mind-body decoupling becomes possible - and pieces of it are already in active research - the technology will not protect you. Rules, enforcement, and power structures will decide whether people remain people or become containers you spin down when the cost-benefit calculation changes.

The film does not answer that question. It does not have to. It just shows you what happens when nobody asks it early enough.

The problems Mickey faces - state persistence, identity integrity, consensus across copies, resource management for on-demand replication - are not hypothetical abstractions. They are the same problems you solve every day in distributed systems, infrastructure design, and platform governance. The difference is stakes. When the system you are designing runs on human lives instead of server instances, every architecture decision becomes an ethical one. And if you wait until production to figure out your failure modes, someone real pays the price.

Leave a comment

Most B2B teams treat LinkedIn like a billboard. Post something. Hope someone sees it. Wait for inbound. That is not a strategy. That is a prayer.

The real pipeline on LinkedIn is not built from impressions. It is built from comments. Specifically, from targeted, high-context comments on the posts of people who can actually buy your product.

This is Account-Based Marketing stripped down to its most efficient form. No ad spend. No cold email sequences that get nuked by spam filters. Just you, a curated list of decision-makers, and relentless precision.

The Dream List Changes Everything

Here is where it starts. You pick 10 high-value profiles per day. Seventy per week. Every one of them fits a tight profile — the right title, the right domain, the right level of authority. Decision-makers with real problems and real budget. The kind of people who aren't waiting to be sold to — they're already looking for a solution.

You are not looking for anyone who might be interested. You are looking for your Sales Champion - the person inside a target org who already feels the pain your product solves.

Log them. Track them. A simple spreadsheet works - 7 days, 10 companies per day, 5-6 comments on their posts. Refresh the list every two to three months so you are never chasing dead accounts.

Engagement That Actually Earns Attention

Now the work begins. Sixty targeted comments a day across your Dream List. Six to seven comments per profile over a week. That is the ratio that breaks through the noise.

But here is the part most people fumble. “Great post!” is not a comment. It is wallpaper. Nobody remembers it. Nobody clicks your profile because of it.

You earn attention by saying something worth reading. Talk about Zero Trust architecture from experience. Reference eBPF and why it changes the runtime security game. Point out the gap between static scanning and actual runtime protection. Mention specific modules or capabilities that make sense given what the person just posted about.

Use the Butterfly Plugin for context-rich comments. It gives you the edge of knowing what someone cares about before you write a single word.

The goal is simple - earn a Like or a Reply. That is your signal.

The Hand-Raise Moment

When a qualified prospect engages with your comment - likes it, replies to it - they have raised their hand. They did not fill out a form. They did not book a demo. But they acknowledged you in a space where attention is currency.

This only works if your Dream List is built right. If you followed BANTC criteria in step one, every interaction is pre-qualified. You already know they have the Budget, Authority, Need, Timeline, and Champion potential.

The rule is non-negotiable. Move to DMs the same business day. The context of your comment is still fresh. Wait 48 hours and you are a stranger again.

Two Lines That Open Doors

Your DM is not a pitch deck. It is two lines. Maybe three. Keep it tight, keep it relevant, and keep it human.

“Hi [Name], saw your reaction to my comment on [Topic]! I have been following your work at [Company]. We are helping teams [Achieve XYZ] with [pitch your tool here] - would love to show you how we are simplifying that for [use case]”

That is it. No attachments. No “I would love to pick your brain.” Just a clear signal that you have done the homework and you have something relevant.

The Rule of Three

Most leads do not convert on the first message. That is fine. You have a system for this.

Three touches. Four days. If there is no response after that, move on. Your Dream List has sixty-nine other profiles this week.

Why This Beats Everything Else

The difference between broad LinkedIn activity and this ABM approach is not incremental. It is structural.

Broad engagement gives you vanity metrics. Likes that lead nowhere. Followers who never buy. The ABM approach gives you a pipeline of identified champions inside target accounts - people who have already engaged with your thinking and know your name before the first call.

The cost is zero dollars in ad spend. The input is focused time and sharp writing. The output is qualified pipeline that your sales team can actually close.

Leave a comment

I started playing these games in 2023 and my relationship with “fun” has never been the same.

There is a specific genre of game -- let’s call it “side-scrolling atmospheric horror puzzle-platformers with silent protagonists and environmental storytelling” -- that does not care about your comfort. No hand-holding tutorials. No backstory monologue. No comforting UI. You are small, the world is enormous and hostile, and good luck figuring out why.

The games are Limbo, Inside, Little Nightmares I and II, and most recently Reanimal, which dropped in February 2026.

They are not for everyone. But if they are for you, they will rewire how you think about storytelling, atmosphere, and what a game can be.

My Personal Timeline

Here is how I stumbled into this rabbit hole:

I found Little Nightmares first, which is probably the wrong order. It is like watching The Dark Knight before Batman Begins -- it works, but you are missing context. If you are starting fresh, go Limbo, Inside, LN1, LN2, then Reanimal. Chronological by release date and by increasing emotional devastation.

What Even Is This Genre?

Playdead, a Danish studio, made Limbo in 2010 and Inside in 2016. Dark, monochrome, political, existential. Tarsier Studios, out of Sweden, made Little Nightmares I in 2017 and II in 2021 -- grotesque, child-nightmare logic, body horror lite. Tarsier then left the LN franchise and made Reanimal in 2026, their spiritual successor, now with co-op and a Mature rating they clearly wanted for a while.

All five games share the same DNA. Silent protagonists with no dialogue or exposition dumps. Side-scrolling or 2.5D perspectives where you are always watching from the side, like peering into a diorama. Environmental storytelling where the world tells you what happened instead of a cutscene. Protagonists who are tiny and powerless, because the entire design philosophy is built on hide-and-seek rather than combat. And every single one of them is dark as hell.

The Games

Limbo, 2010

A boy wakes up at the edge of hell, searching for his sister. That is all you are told.

Limbo is black and white. Aggressively, philosophically black and white. The silhouette of your character against the grey forest feels less like a game and more like a woodcut from a Grimm fairy tale that nobody cleaned up for children.

The sound design is the real horror. Composer Martin Stig Andersen deliberately avoided anything that sounded like a video game. He pulled from old films to build a unified soundscape where music and effects are indistinguishable. There is no separate “background music.” It is one audio organism. You feel the forest before you see what is in it. The ambience shifts slightly before a threat appears. The game is breathing at you.

The spider. God, the spider. In the first section, you are stalked by a giant spider with legs that move like something designed to make humans feel specifically wrong. The game teaches you its rules fast -- you do not win by strength here. You trick the spider using the environment. You use its own aggression against it. Every puzzle is built on the gap between your size and everything else’s.

Some read Limbo as the boy trapped in purgatory, endlessly searching, never arriving. The ending loops back to where you started. Others read it as him processing his sister’s death inside a dream. Playdead never confirmed either reading, and that is not a cop-out -- it is a feature. The ambiguity is the story. The game gives you exactly enough to feel the weight of loss, then stops short of explaining what the weight is. You fill it in yourself.

Seventeen years later, Limbo still holds up because it trusts you. It does not explain. It does not comfort. It gives you a child-shaped silhouette, a hostile world, and respects your intelligence enough to let you feel your way through the dark.

Inside, 2016

A boy in a red shirt is running from armed men through a dystopian countryside. You do not know why. You keep running.

Inside takes everything Limbo did and makes it stranger, weirder, and far more politically loaded. It borrows German Expressionist film lighting -- the same technique Fritz Lang used in Metropolis in 1927 -- to frame a story about bodies, control, and what it means to be free.

The camera is where Inside becomes something special. The game is 2.5D, meaning the world is fully three-dimensional but you move in one direction. The camera constantly adjusts angle to create cinematic framing. You will be running left and suddenly it rotates so you are running toward it while something chases you from behind. This is not showing off. It isolates you, makes you feel watched, builds the specific dread of not knowing what is behind you. There are moments where the camera pulls back so far you are a tiny red speck in an enormous industrial space. That distance is deliberate.

The mind-controlled workers are the detail that gets me. Mid-game, you find a device that lets you control the zombie-like workers around you. You use it without question because the game told you to. You march them off ledges. You use their bodies as tools. You are doing to them exactly what the people chasing you are doing to you. The game never calls this out. It just lets you do it.

Then there is the Huddle. This is what Inside is most famous for, and I will not fully spoil it. The final act involves a mass of fused human body parts that you control. When you think about what you have been doing the entire game -- entering facilities, controlling bodies, following a linear path designed by someone else -- the ending recontextualizes everything. You were not the hero escaping the system. You were the system’s most efficient product. The whole game is about a boy following a trail someone laid out for him, thinking he was escaping. And you, the player, followed it too.

The sound design was made using bone conduction through an actual human skull. Not a joke. Martin Stig Andersen processed certain audio frequencies through a real skull. The result is a score that sounds viscerally wrong in a way you can feel but not name. Your body reacts before your brain does. The boy’s breathing changes depending on location -- calm in safe zones, panicked when hunted. That level of physiological detail, where the protagonist’s nervous system is wired into the audio engine, is the kind of thing you notice after you stop playing and realize the game was manipulating yours the entire time.

Little Nightmares I, 2017

Six, a tiny girl in a yellow raincoat, wakes up inside The Maw -- a massive underwater vessel full of grotesque guests who want to eat her.

Little Nightmares hits differently from the Playdead games because it is not monochrome. It is full color. A sickly, beautiful palette of rust, bile yellow, and dim lamplight. Instead of political horror, it goes straight for childhood nightmare logic.

The enemies are not designed to be scary in a conventional way. They are designed to tap into something pre-verbal. The Janitor, a thin long-armed man who cannot see but finds you anyway, moves like a daddy-long-legs that learned to walk upright. The arms are too long. The body is too thin. The sound of him shuffling through the dark is the specific sound of something that should not exist. The Chefs are enormous, sweaty, and vaguely Dad-shaped. The Guests are bloated, ravenous, and they eat everything including each other.

What these enemies represent matters. The game was originally titled Hunger, and every villain in LN1 embodies a specific kind of power. The Lady -- the final boss -- represents vanity and soul-draining control, draining the life force of guests to sustain her beauty. The Chefs represent labor and production, the machinery of appetite. The Guests represent consumption and excess, the audience that enables all of it.

Six herself is not innocent. There is a “Dark Six,” her shadow self, who appears specifically whenever Six eats. The game is tracking her moral decay. She eats a rat early on because she is starving. By the end, she eats the Lady. Survival transforms you, and not into something clean.

The camera is third-person over-the-shoulder but always at a slight remove. You are never close to Six. You are watching her from a distance, like through dirty glass. This creates the feeling of watching a nightmare rather than being inside one. You care about Six because she is tiny and alone, but the distance prevents it from becoming cozy.

The Maw itself is a triumph of environmental design. The developers described it as a place “where all the worst things in the world could be left to rot.” A ship that sails to ports and lures people in with food. The metaphor of a cruise ship of excess that feeds on souls lands differently depending on how charitable you are feeling about humanity at the time.

Little Nightmares II, 2021

Mono, a boy with a paper bag on his head, escapes a forest and joins Six in navigating a city controlled by a signal broadcast from a tower.

LN2 is a prequel to LN1. You do not know this until the end. The end is devastating.

The villain structure is more sophisticated than its predecessor. Each level has a different boss representing a distinct real-world nightmare. The Hunter represents rural, isolated abuse -- a man who stuffs children in cages. The Teacher represents institutional control, stretching her neck across the room to catch you because she does not need to move her body when the system does the reaching for her. The Doctor is a bloated, spider-walking man in a hospital full of mannequin-people. And then there is The Thin Man -- Mono himself, from the future. A time loop villain who exists because the story has to happen.

That last one has stayed with me longer than anything else in these games. The Thin Man is what Mono becomes after Six drops him into the Signal Tower at the end. Six drops him because she has learned through her entire journey that survival means letting people go. She absorbed this from her own trauma with the music box, which Mono accidentally destroyed. When Mono shatters the thing that gave Six comfort, she cannot forgive him -- not consciously, but in the way trauma works, stored until the moment it matters. She drops Mono the same way she later eats the Lady in LN1. The game is saying something plain and terrible: this is what this world does to children, and what children do to each other because of it.

Mono’s name means “one channel, one direction.” Mono audio. The game’s aesthetic is drenched in 1950s television. The Pale City looks like a postwar urban nightmare, flickering with screens. The Thin Man looks like an old Hollywood agent. Children watching TV, dreaming of the city, getting chewed up by it. Pull one thread and the lore keeps unraveling.

The city sounds like a dying television signal. Static, distortion, the hum of the Broadcast that zombifies adults into walking toward the tower. Adults in this game are not predators chasing you because they are hungry. They are addicted. They walk off buildings trying to get closer to the signal. The commentary on media addiction is about as subtle as a building full of people walking off its roof -- which is to say, not subtle at all, and absolutely correct.

Reanimal, February 2026

A brother and sister return to an island that used to be their home and find it has become something else entirely. Their friends are missing. Everything is trying to kill them.

Reanimal is Tarsier after Little Nightmares. Bigger budget, Mature rating, and a thesis about something they could not explore before: fear is scarier when you are not alone.

This is the first co-op game in this genre I have loved. The co-op is not bolted onto a solo experience. The entire design is built around a shared, directed camera that keeps both players in frame at all times. You cannot wander off. You are tethered by the camera itself, and the claustrophobia is architectural. When my co-op partner and I were both frozen, too scared to move, staring at something in the distance, the game let us stay there. No timer. No rush. The sound design lets silence do the work.

The monsters are body horror in a way the LN games gestured at but never fully committed to. Human skin hanging to dry. Giants emerging from corpses. The game earns every inch of its Mature rating, having made the jump from “nightmare logic” to “this is medically disturbing.”

The fragments of the children’s past are used directly in monster design. Tarsier confirmed this -- the creatures tormenting you are built from the protagonists’ own trauma. The island’s horror is not random. It is personal. The specific things that hurt these children became the things that now hunt them. Horror movies wish they had this level of psychological specificity.

Reanimal had over a million wishlists before launch, which means the Tarsier fanbase was ready and waiting. People who loved Little Nightmares followed the studio here without hesitation. The game launched February 13, 2026. I played it almost immediately.

Where Little Nightmares was about a child alone in a hostile world, Reanimal is about two children facing that world together. The game’s honest answer is: yes, having someone helps. And that makes the horror worse, because now you have something to lose.

What These Games All Share

Four craft elements run through all five games, and they are the reason I keep coming back.

1. The size ratio is doing everything. In every single one of these games, the protagonist is small. The environments and enemies are enormous. This is not aesthetic -- it is a design philosophy. You cannot win by fighting. You can only observe, hide, and be clever. The game is structurally telling you that you are not powerful, you are perceptive. Most games hand you increasing power over time. These games keep you small throughout. The final boss of Little Nightmares does not become easier because you got stronger. Six wins because she has been watching and waiting for one specific vulnerability.

2. The camera is always doing narrative work. None of these games have a neutral camera. Limbo uses silhouette framing -- form without detail, like a child’s nightmare. Inside uses German Expressionist angles where shadows swallow the frame. Little Nightmares keeps you at a voyeuristic remove, like watching through glass. Reanimal’s shared camera is a design constraint that creates co-op tension by making separation physically impossible. In every case the camera is not a tool, it is a collaborator. It is the most important character in the game.

3. Sound is the actual horror. All five games understand that the scariest sound is what you hear before you see anything. The distant ice cream truck music in Reanimal. The hum of the Broadcast Tower in LN2. The ambiguous noise in Limbo’s forest that might be the spider or might be nothing. None of these games lean on jump scares as a primary tool. They use dread -- the sustained, specific, mounting certainty that something is wrong. Your body reacts before the game confirms anything.

4. The villains are systems, not monsters. The scariest thing about every villain in these games is that none of them are evil for evil’s sake. They are the logical endpoint of something recognizable. Greed. Vanity. Institutional control. Media addiction. Trauma made physical. The horror is not that something unknowable is chasing you. The horror is that you understand exactly how it got here. You just do not know how to stop it.

My Honest Ranking

1. Inside. Structurally the most sophisticated. The ending is the argument. Everything before it is evidence.

2. Little Nightmares II. Emotionally the most devastating. The Thin Man reveal broke me.

3. Reanimal. The most terrifying moment-to-moment. Playing co-op made certain scenes actively traumatizing in a way solo horror never achieves.

4. Little Nightmares I. The most beautiful. The Maw is a masterpiece of environmental design, and every inch of it is deliberate.

5. Limbo. The most elegant. Seventeen years old and still holds up. The spider scene still works on me.

Who Should Play These Games

These games are for you if you love atmospheric horror but hate jump scares, if you enjoy games where the story is a puzzle rather than a monologue, and if you appreciate design where theme and mechanics are genuinely the same thing. They each take three to six hours to finish -- short enough to complete in a weekend, long enough to stay with you for years. If you want to feel genuinely unsettled for days after the credits roll, this is your genre.

A word of caution: if you are sensitive to body horror, approach Reanimal carefully because it escalates fast. And if ambiguous endings frustrate you, know going in that these games trade resolution for resonance. The stories do not wrap up neatly. They leave you with questions that feel more valuable than answers.

If you need explicit story beats to feel satisfied, if you want combat and power progression, or if you play games primarily to relax -- these are not your games. That is not a judgment. These five titles ask for a specific kind of attention, and they repay it with a specific kind of experience. Not fun, exactly. Something that stays.

Games covered: Limbo (2010, Playdead) · Inside (2016, Playdead) · Little Nightmares (2017, Tarsier) · Little Nightmares II (2021, Tarsier) · Reanimal (2026, Tarsier/THQ Nordic)

Leave a comment

Something is rotting in the developer brain, and nobody wants to name it.

I’m going to name it.

It’s called Token Anxiety. And if you’ve written a single line of code in the last six months, you’ve felt it. That low-frequency hum behind your eyeballs. That itch to check on a running agent while someone’s talking to you at dinner. That creeping suspicion that while you’re doing literally anything else, something could be running, and it isn’t, and that’s somehow your fault.

Let me explain.

The Old Buzz

Every programmer who’s been at it long enough knows this feeling: you hit a wall. Some gnarly bug, some architectural knot that your conscious mind can’t untangle. So you step away. Take a shower. Go for a walk. And somewhere between shampoo and conditioner, it hits you. The solution just lands. That white-flash moment where the entire architecture clicks into place like a dislocated shoulder popping back in.

That was the old buzz. It felt like a superpower.

The dark side was subtle. You’d sit at dinner, physically present, mentally spiraling. You could feel the gears turning behind your ears even when you weren’t actively thinking about the problem. Friends are talking, food is getting cold, and you’re halfway inside a function signature you can’t let go of. If you’ve been coding long enough, you know this feeling. It’s intimate. It’s almost romantic, in a sick way.

That buzz used to be intermittent. You had to earn it. A hard enough problem had to show up first.

Now? The buzz is permanent. And it isn’t coming from your brain anymore.

It’s coming from the machines.

The Permanent Vibration

There’s this culture taking shape among developers right now, and it’s genuinely unsettling.

Someone leaves a party at 9:30 on a Saturday. Not tired. Not sick. They want to get back to their agents. Nobody questions it. Half the room is thinking the same thing. The other half is checking agent progress on their phones at the party itself.

Startup founders are publicly declaring they’re giving up alcohol so their brains stay “maximally pristine” to “sling 10,000 lines of code a day.” People openly saying they replaced watching movies with watching Claude output. Lying in bed, not sleeping, thinking about what they can spin up before they lose consciousness. What can I run while I’m out?

Reading a novel feels indulgent.

Watching a movie without a laptop open feels wasteful.

This voice in your head: something could be running right now.

It just doesn’t shut off.

That’s Token Anxiety. And the scariest part? The anxiety is rational. Which is exactly why it sticks.

The Rational Trap

Every week, some new benchmark drops that makes last month’s workflow feel prehistoric. A new model ships overnight. Context windows double. Opus gets faster. Sonnet gets cheaper.

None of this reduces the pressure. It multiplies it.

You can do more now, and someone already is. The window to being first at anything, building anything, shipping anything, feels like it shrinks by the day. Literally by the day.

Tech circles used to feel like this raw, electric field of opportunity. “There’s so much to build. Come try things.” There was excitement. Genuine, infectious, reckless optimism.

Now look at the same circles. The energy has inverted. It’s no longer “come build exciting things.” It’s “I better keep working because if I stop for an hour, it’s all escaping me.” The tone shifted from opportunity to desperation. From “I get to build” to “I must build or I drown.”

That’s a completely different animal. And it’s eating people alive.

The Faustian Bargain of Vibe Coding

I’ll be honest. I’ve been forcing myself into this vibe coding world. Building things with agents, spinning up projects through conversational prompts, really trying to understand what the hype is about.

Here’s what actually happens.

The beginning is seductive. The idea is simple. You can describe it in a few words. The rough scaffold comes up fast. MVP in hours. Feels electric.

Then the fixes start. Each fix requires more prompting. More waiting. More context-loading. The cycle is brutally long. Worse than a Rust compile cycle. And each fix spawns two more things you want to tweak, and those spawn two more. The work grows exponentially.

But here’s the insidious part. Because each new project is so easy to start, you end up with four or five things spinning simultaneously. All of them in the crappiest versions of themselves. All of them demanding your attention. You’re constantly babysitting small steps, typing out explanations in English to fix things that would take 10 keystrokes in actual code.

You’re building more than you’ve ever built in your life. And accomplishing less than ever.

10,000 lines of code in a day. Easy. But those 10,000 lines aren’t good. You don’t feel satisfied. You didn’t even build the right thing.

The Selection Problem

This is the part nobody talks about.

Before AI, you couldn’t try every idea. You had to be selective. You had to pick one problem, commit to it, and push through it. That constraint was a gift. It forced prioritization. It forced you to solve the right problem because you simply couldn’t afford to solve the wrong one.

Now you can have three or four ideas spinning at the same time. All of them half-baked. All of them growing in scope at an exponential rate. The work multiplies, the task juggling spirals out of control, the productivity metrics go through the roof.

And nothing ships.

People are spending $1,000 a day on API tokens. Building constantly. Jumping from project to project. Running agents 24/7.

And they have literally nothing to show for it.

The programming was never the bottleneck. The bottleneck was always choosing what to build. AI removed the wrong constraint. It made execution trivially cheap while doing absolutely nothing about the actual hard problem, which is deciding what matters.

The Split-Brain Problem

There’s this fracture happening inside every developer who straddles the old and new world. You’re hand-coding something, and halfway through a function, this thought creeps in: “I could vibe code this in 30 seconds.” So you kick off an agent. And now you’re standing in two worlds. One foot on the platform, one foot on the train.

You feel the pull of the agents constantly. “Better kick off a quick one.” “Let me just prompt this side feature real quick.” And that buzzing sensation keeps evolving, growing, compounding. It’s not productive energy. It’s anxious energy. The energy of someone who knows something could be happening and isn’t.

What This Actually Costs

Let me be direct.

I’ve been in that state before, long before AI was in the picture. The non-stop pursuit of building. Staying up through entire nights programming. Feeling anxious at social gatherings because part of my brain wanted to get back to the editor. Feeling like every minute spent not coding was a minute wasted.

It impacted friendships. It turned me into a process instead of a person.

AI agents are resurrecting that exact feeling. Except now it’s amplified, because the machine never sleeps. It’s always ready. There is always another prompt you could send. There is always another project you could spin up. The guilt of rest is infinite because the capacity for work is infinite.

That is not productivity. That is addiction dressed in a hoodie.

The Advice I’d Give Myself

One extra feature in your calendar app is not worth skipping a good evening with your friends.

One more agent run overnight is not worth the fog you’ll carry into tomorrow’s conversation with someone who matters.

The 10,001st line of code today will not be the one that changes your life. But the moment you miss tonight might.

Hard work is a vehicle. It is how you got here. But it is not who you are. The second you confuse the vehicle for the identity, you stop being a person and start being a process. And processes don’t have dinner with friends. Processes don’t read novels. Processes don’t watch movies with their full attention and feel something.

You are not a process.

The machines run without you. Let them. Turn off the terminal. Close the laptop. Leave the agents unsupervised for one single evening.

The code will still be there in the morning. The same bugs, the same half-baked MVPs, the same exponentially growing task lists.

But the people around you won’t always be.

Token anxiety is real. The pressure is real. But the thing you’re racing against isn’t a competitor. It’s a feeling. And feelings don’t ship products.

Ship less. Ship meaningful. Choose better. Live more.

Leave a comment

You spent hours curating your VS Code setup. The right extensions, the right config, the right workflow. Now a friend or colleague asks what you use. You could send them a screenshot and let them hunt for each extension manually. Or you could give them a single command.

VS Code’s Settings Sync exists, but it syncs your account to your machines. It does not help you share your setup with someone else’s account on their machine. For that, you need a different approach.

Exporting Your Extensions

On your machine, open a terminal and run one command. On Windows PowerShell, that command is code --list-extensions | % { "code --install-extension $_" }. On Mac or Linux, the equivalent is code --list-extensions | xargs -L 1 echo code --install-extension.

What you get back is a self-contained script. Every extension you have installed becomes a single install command. The output looks like this:

code --install-extension Angular.ng-template
code --install-extension EditorConfig.EditorConfig
code --install-extension HookyQR.beautify

Copy the entire output. Send it however you want -- Slack, email, a text file, a GitHub gist. The format does not matter because the commands are portable.

Installing on the Other Side

Your friend opens their terminal, pastes the commands, and runs them. Every extension installs in sequence. No searching the marketplace. No misspelled extension names. No “which one was it again?” conversations. The whole process takes under a minute for a typical setup.

If the code command is not recognized on their machine, they need to register it first. Open VS Code, hit Ctrl+Shift+P, type Shell Command: Install 'code' command in PATH, and run it. After that, the install commands work.

Why This Matters More Than You Think

The real leverage here is standardization. If you are onboarding someone onto a project, a shared extension list means everyone starts with the same linting, formatting, and language support. No more debugging issues caused by someone missing a required extension.

For teams, commit the extension list to your project repository as a text file. New developers clone the repo, run the commands, and start writing code with the correct tooling from minute one. The time savings compound with every person you onboard.

This is the smallest possible automation that makes one of the most common developer annoyances disappear entirely.

Leave a comment