Field guide / primary domain

Developer Tools

221

sources in this field

Updated September 19, 2026

Current thesis

The shortest path to orientation.

This synthesis records claims and practices from the cited sources; reported outcomes and product capabilities have not been independently verified.

Developer tools standardize on agent-accessible knowledge formats and designer-level aesthetics. Agent Plugins v1.0.0 defines portable package format across Codex, ChatGPT, Cursor, GitHub Copilot, and VS Code. Infrastructure standardizes one-click deployment, real-time token cost visibility, and multi-model dev loops (~$400/month). Vertical slices—building API contract→frontend→services→DB incrementally (100–200 lines at a time)—outperform default horizontal plans since frontier models won't design vertically without explicit steering. Knowledge tooling densifies around Obsidian-as-agent-surface and markdown vaults via MCPs. Terminal emulators redesigned for agentic workflows (Ghostty). Free inference mainstream via NVIDIA. Git-based knowledge systems hit 2.3GB+ walls, forcing SQLite migration. Anthropomorphizing language in AI-generated code review provides audit signals for AI-authored feedback. UI generation now constrains via json-render: Zod schemas guarantee JSON output matches spec, with single definitions targeting 10+ renderers (React, Vue, Svelte, React Native, Next.js, Remotion, React PDF, React Email, Ink, React Three Fiber). Streaming compilation (createSpecStreamCompiler) enables progressive rendering from partial LLM responses. Dynamic prop expressions ($state, $cond, $template, $computed) bind generated specs to app state without imperative code. Pre-built @json-render/shadcn components (36 UI elements) reduce setup cost; devtools provide integrated inspection (spec tree, state editor, action log) via Ctrl/Cmd+Shift+J.

Evidence board

Claims worth carrying forward
01

A browser-based adversarial testing suite runs massively parallel adversarial checks against each new release, attempting to break it before ship, at a cost described as 'pennies.'

02

Parallelizing adversarial/browser-driven test runs across many instances makes exhaustive pre-release stress testing economically viable even for small teams.

03

json-render constrains AI-generated UI to a developer-defined catalog of components/actions with Zod schemas, guaranteeing JSON output matches the schema every time rather than hoping the model stays in bounds.

04

Single catalog definition targets 10+ renderers from one spec format: React, Vue, Svelte, Solid, React Native, Next.js, TanStack Start, Remotion (video), React PDF, React Email, Ink (terminal), and React Three Fiber (3D/Gaussian splatting).

05

createSpecStreamCompiler (in @json-render/core) supports progressive rendering: it processes streaming chunks from an LLM response and returns partial results/patches so UI can render before the full spec arrives.

06

Dynamic prop expressions ($state, $cond/$then/$else, $template, $computed) let generated specs bind to app state and branch logic without the AI needing to write imperative code.

07

experimental_composeSpec and experimental_createEvaluator (unreleased, source-build only) enable 'Jev' composition — combining/evaluating specs programmatically with a custom catalog; accessible via /playground's Jev (Experimental) mode.

08

@json-render/shadcn and @json-render/shadcn-svelte ship 36 pre-built shadcn/ui components ready to drop into a catalog, reducing the setup cost for AI-generated dashboards and apps.

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →

Chris Tate

json-render: Guardrailed Generative UI Framework from Vercel Labs

json-render (vercel-labs) is a cross-platform Generative UI framework that constrains AI-generated JSON specs to a predefined component catalog, enabling safe, predictable UI rendering across React, Vue, Svelte, Solid, React Native, video, PDF, email, and terminal targets. It ships streaming compilation, dynamic expression props, state watchers, and devtools, plus experimental spec-composition APIs.

Matt Dailey

How I Design with AI (De-Sloping Product Design)

Matt Dailey (Ref) outlines a 7-step design process for AI-assisted product design: fixing constraints before jumping to solutions, removing AI-added bloat, iterating in dedicated design tools rather than the live codebase, using component libraries, leveraging preview deploys, stealing proven UX patterns, and deliberately building personal taste.