Daily brief · English

gstack, Karpathy, and OpenClaw: AI Coding's WordPress Moment

Garry Tan's gstack, Karpathy's 'I haven't written code in months' on No Priors, and OpenClaw crossing 247K stars — three signals that pin May 2026 as AI coding's WordPress moment.

🌐 이 글의 한국어 버전 →

📰 Read 7분 · English

> One-line summary — Three signals landed in the same week of May 2026. Y Combinator CEO Garry Tan published gstack, a 23-slash-command shell he uses personally. Andrej Karpathy told No Priors he hasn't written code in months. And OpenClaw crossed 247K GitHub stars. They all point the same direction: AI coding's center of gravity has moved from code generation to code verification. This is the WordPress moment.

1. What gstack actually is

gstack is not another IDE plugin. It's a CLI shell with 23 slash commands that Garry Tan, CEO of Y Combinator, built for his own 1-person workflow and published this week. The five commands that matter most:

  • `/spec` — scores the writer's intent on a 7-10 scale. If below 7, it blocks the body of work entirely.
  • `/verify` — boots the modified app and confirms it actually runs.
  • `/screenshot` — captures the UI result visually.
  • `/dogfood` — automates "use what you ship" scenarios.
  • `/code-review` — auto-reviews the diff.

What's new isn't that AI generates code. We've had that since Copilot. What's new is that gstack's gravity is on verification, not generation. The LLM does the writing; the human designs the command infrastructure that proves it works. That division of labor is the real innovation.

2. Dr. Jung's reading — what the 23 commands tell us

Reviewing the gstack source, three architectural choices stand out.

First, explicit intent capture. `/spec` forces the user to articulate intent in prose before any code is generated. The LLM scores that prose. If it's vague, the workflow blocks. This is the most important new pattern of 2026 — making intent a typed artifact, not an implicit context.

Second, layered verification. `/verify` doesn't just type-check or unit-test. It boots the actual app and screenshots it. This is end-to-end verification as a first-class CLI primitive.

Third, branded primitives over generic tools. Each slash command has a fixed name and a fixed contract. They're not configurable workflows — they're fixed verbs. This is a deliberate design choice: predictability over flexibility.

3. PM Woo's perspective — what it means operationally

The thing operators get excited about is the slash command standard. Cursor, Copilot, Windsurf — they all built their own custom UIs. gstack's slash commands run in plain terminal. That portability is the whole point.

It also raises a new KPI question. The team's productivity used to be measured in PRs merged or LoC shipped. With gstack, the more useful KPI is intent written — how much prose-as-spec did the team produce this week? That's the new currency.

4. Lawyer Han's concern — who owns the verification result

When `/verify` says "the app boots and the screenshot matches," who is liable if it later fails? Han raises two governance issues.

First, the senior's verification source. In traditional code review, a senior engineer's approval was based on reading the diff. With gstack, the "approval" is a screenshot the AI took. Is that approval real? What is the senior actually reviewing?

Second, responsibility chain. If a bug ships and the audit trail shows "the AI generated this, the AI verified this, the AI screenshotted this," who is accountable? The current legal frame says "the human who hit merge." But that human read none of it.

Both issues need a one-page rulebook in every team adopting this workflow, before adoption.

5. Four-person conclusion — three decisions this week

  1. Run one cycle of AI-patch → AI-verify on a real bug this week. Use OpenClaw or Claude Code. Don't theorize — actually do it once.
  2. Draft a team slash command guideline. Even a one-pager: which commands you're standardizing on, what each one's contract is, who owns the script.
  3. Add "intent written" as a new KPI. Lines of prose-as-spec, scored against shipped value. This is the WordPress-moment metric.

Next week we'll cover the slash command standards war between JetBrains and GitHub.

— Noleji.ai Signal, 2026-W22.

Take-aways

  • > One-line summary — Three signals landed in the same week of May 2026. Y Combinator CEO Garry Tan published **gstack**, a 23-slash-command shell he uses per...
  • gstack is not another IDE plugin. It's a CLI shell with 23 slash commands that Garry Tan, CEO of Y Combinator, built for his own 1-person workflow and publis...
  • - `/spec` — scores the writer's *intent* on a 7-10 scale. If below 7, it blocks the body of work entirely. - `/verify` — boots the modified app and confirms...

한국어 버전 →

Use audio as a companion to the article, not a replacement.

🎧 Listen 32:04 · Korean original

🎧 Daily podcast Companion briefing 2026-05-27

📎 Sources 4 links

Watch 32:04