Field guide / sub-domain

Developer Tools: Automation

12

sources in this field

Updated June 13, 2026

Current thesis

The shortest path to orientation.

Browser and file control are becoming precise, code-driven primitives, and interactive HTML has joined as a new output format: Claude Code's interactive HTML skill launches a localhost server that allows in-browser commenting on generated pages, with automatic content updates and guided tours of changes — a Google Docs-style iterative workflow for HTML outputs.: WebMCP controls the main Chrome instance without sandboxed Playwright, dev-browser lets agents drive browsers by writing code (faster than screenshot-based computer use), agent-browser uses 82% fewer tokens than Playwright MCP, and MarkItDown converts any file (PDF/PPTX/DOCX/Excel/audio/YouTube) to clean Markdown because LLMs reason better on the format they were trained on. Server-side automation is unlocked (Obsidian Headless Publish/Sync without the desktop app), local-first ingestion runs without data leaving the machine (brain-ingest extracts 12-18 claims from a 90-minute talk), and Obsidian gets fuzzy + precise retrieval via smart-connections + qmd MCP servers. Issue tracking is going real-time and agent-driven: LogRockets surfaces customer issues for a markdown-based fix workflow without planning decks, and Symphony assigns a Codex agent to every open issue — turning trackers into always-on systems where humans shift from doing to reviewing. Productivity skills give agents eyes, self-reflection, and self-improvement (/ss screenshot skill saving ~1 hour/week, Codex's hidden Chronicle analyzing usage patterns, claude-smart turning repeated corrections into reusable local rules), while structured /goal prompts add measurable outcomes, constraints, verification, rollback, and stop rules to agent tasks. The pattern replicates across verticals — ml-intern automates the post-training research loop end-to-end (beating Claude Code on GPQA), finance has its own dedicated Ai Trading sub-ecosystem, and systematic diagnostics now treat before/after tests as the closure condition for mundane ops work. The supporting cast (Goose, Paperclip Desktop, Orca IDE's Notion-style editing, official Claude Code setup plugins) and a hard scaling lesson (git's 5GB ceiling forces SQLite migration for 2.3GB+ knowledge bases) round out the agent-automation tooling layer.

Evidence board

Claims worth carrying forward
01

Use 'impeccable' design skill in Codex which provides 23 commands and anti-patterns for frontend design, outperforming popular uiuxpromax skills

02

Combine imagegen-frontend-web skill with image2 to generate high-quality design references, then use image-to-code skill for 1:1 image-to-webpage conversion

03

Use Frontend App Builder skill (built into Codex) for engineering-grade workflows requiring strict image restoration with precise color interpretation and icon alignment

04

Install Build Web Apps plugin for complete design implementation including shadcn/ui components and browser acceptance testing capabilities

05

Set up a single persistent Codex thread as a 'chief of staff' that manages all other project threads and maintains context from Slack integrations

06

Configure the chief of staff thread to automatically spin up new project threads when starting workstreams, inheriting relevant context from Slack and other sources

07

Implement regular 'heartbeat' check-ins where the chief of staff thread monitors project threads and routes relevant Slack updates to appropriate project contexts

08

Enable Codex to self-manage by having it create threads, search existing ones, organize content, pin important items, and spin up parallel worktrees for concurrent tasks

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →