Field guide / primary domain

Vibe Coding

64

sources in this field

Updated July 15, 2026

Current thesis

The shortest path to orientation.

Vibe coding has matured into genuine production-scale software with frontier models now handling complex tasks autonomously. Ultracode mode in Opus 4.8 removes manual orchestration by enabling Claude to invoke Dynamic Workflows independently for complex problems. The supervisory workflow delegates subgoals to monitored threads, routes routine execution to cheaper models, and enforces quality gates—every subagent self-reviews, passes a bug bot, and submits recordings before PR acceptance. With 60+ PRs possible overnight, human review throughput becomes the bottleneck.

A two-model adversarial review loop proves effective: Claude Opus 4.7 drafts feature plans and code, GPT-5.5 reviews and identifies issues, Opus iterates until GPT approves, then Playwright handles automated UX/UI testing. GPT-5.5 consistently finds issues in both planning and code review phases—suggesting heterogeneous model pairs catch more bugs than single-model loops. At ~$400/month for Opus 4.7 + GPT-5.5 via Conductor Build, end-to-end feature planning, code generation, testing, and adversarial review costs equivalent to a fractional dev team.

Design has moved into the terminal; principals complete 95%+ via design.md specs without Figma. The ticket-to-PR loop enforces discipline: reproduce failure, prove root cause, make minimal credible fix, rerun tests. No unrelated refactors. Best practices invert rapidly; treat prior guidance as perishable.

Evidence board

Claims worth carrying forward
01

Two-model adversarial review loop: Claude Opus 4.7 drafts the feature plan, GPT-5.5 reviews and finds issues, Opus updates until GPT approves, then Opus builds, GPT reviews code, Opus fixes, GPT signs off. Playwright handles automated UX/UI testing between steps.

02

GPT-5.5 consistently finds issues in both the plan phase and code review phase when acting as a second-opinion reviewer over Claude Opus output—suggesting heterogeneous model pairs catch more bugs than single-model loops.

03

~$400/month for Claude Opus 4.7 + GPT-5.5 via Conductor Build covers end-to-end feature planning, code generation, automated testing, and adversarial review—framed as equivalent cost to a fractional dev team with no push-back on small UI changes.

04

Conductor Build (@conductor_build) is a tool that simplifies bouncing work between multiple LLM providers (Anthropic + OpenAI) in a single workflow, removing the friction of context-switching between APIs or interfaces.

05

JustHireMe's quality gate deterministically rejects leads before they enter the pipeline, filtering on: missing URL, thin content, staleness, senior-only roles, unpaid/commission listings, and missing company context. This pre-filtering is the primary mechanism for 'more signal, less noise'—ranking only runs on accepted leads.

06

Fit scoring combines deterministic rubric + GraphRAG proof from a Kuzu profile graph + LanceDB semantic vectors + optional LLM evaluation + feedback learning. Crucially, every ranking decision exposes a visible reason (which skills matched, which projects support the application, what gaps exist), making it auditable rather than a black box.

07

The app runs keyless by default: discovery, ranking, and generation work with zero API key using a bundled ONNX all-MiniLM-L6-v2 model with a deterministic hashing fallback. Keyed providers (OpenAI, Gemini, Groq, 15+ others) are optional. Ollama, Claude Code CLI, and Codex CLI cover all LLM steps without cloud credentials.

08

Tech stack: Tauri 2 (desktop shell, auto-update, cross-platform), React 19 + TypeScript + Vite (frontend), Python 3.13 + FastAPI + WebSockets (backend sidecar), SQLite (CRM), KuzuDB (profile graph), LanceDB (vector store), Playwright (experimental automation only). Thin installer ~100MB; heavy runtime (browser + vector libs + ONNX model) downloads once on first run.

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →

Vasu-Devs

JustHireMe: Local-First Agentic AI Job Intelligence Workbench

JustHireMe is an open-source, AGPL-licensed desktop app (Tauri + React + Python/FastAPI) that addresses broken job search UX with a local-first, explainable AI pipeline: scrape → quality gate → rank → match (GraphRAG + vector) → generate tailored application materials. All data stays on-device by default, LLM usage is keyless-capable via Ollama/Claude Code CLI, and the architecture prioritizes human-in-the-loop control over blind automation.

GREG ISENBERG

Design.md + AI Skills: Consistent Startup Branding in One Hour

Google's open-source Design.md format captures typography, colors, and spacing in a single markdown file that agents reference to produce consistent outputs. Combined with reusable skill files (landing page, mobile, pitch deck), it creates a design system any AI agent can apply uniformly across all surfaces—replacing the common pattern of polishing one screen while everything else looks generic.

tobi lutke

Shopify's River: Public AI Work as Institutional Learning

Tobi Lütke describes River, Shopify's internal AI coding agent living in Slack, designed with one hard constraint: it only works in public channels, not DMs. This forces all AI-assisted work into the open, creating a 'Lehrwerkstatt' (teaching workshop) where knowledge spreads osmotically. In 30 days, 5,938 employees used River across 4,450 channels; it opened 1,870 PRs in one week (~1 in 8 merged PRs). Merge rate climbed from 36% to 77% over two months purely from collective human feedback, not model changes.

klöss

/goal Command Structure for Codex, Claude Code, and Hermes

A structured /goal prompt template for AI coding agents (Codex, Claude Code, Hermes) that prevents scope creep, ranks uncertainties before acting, and closes completion loops. Key sections: GOAL (single measurable outcome), CONSTRAINTS, PLAN (understand-first), DONE WHEN (verifiable state), VERIFY (tests + rollback), STOP RULES (halt on ambiguity, surface ranked proposals not open questions).

George from 🕹prodmgmt.world

The /goal Command and What It Demands from Product Managers

Claude Code's /goal and Codex's /goal commands implement a completion-contract pattern: a working agent loops until a separate evaluator confirms a stated condition is met, judged only from evidence surfaced in the conversation. The post argues this punishes vague PM requirements faster than traditional development, raising the bar from 'write enough detail an engineer understands' to 'define done clearly enough an agent can keep trying and a harness can inspect proof.' Includes a practical goal template and anti-patterns.