I know SF is the subject of attention in tech, but SoCal is just better, it’s not even close…

Early innings still, but I love how easy it is to use the Zoah MCP server to generate initial ideas for typography, color palettes, and branding. Then have my agent translate to a design system with components, and use those comps to build and deploy a website, all in Zoah!

Enjoying an amazing conference at @valiocon with my wife! It’s our first conference together!

Love our dev tooling at @OpacityHQ. Makes it so easy to spin worktrees up, and spin worktrees down.

When a review agent concludes its work, you can have it comment its findings on the associated PR in GitHub, or file follow up issues. Great for also conveying to the team and for human reviewers what was already previously caught or considered, and what is flagged as follow ups

The most commonly used agents in our tool stack are the review agents. A general review agent acts like a coordinator, spawns subagents to check on specific aspects of the diff depending on what the changes entail. But any review agent can be invoked.

We manage GitHub issues from our IDE's using custom web views that also allow us to select and trigger specialized agents from within that issue's view, or create a new worktree for that issue. Agents can run interactively or autonomously. Or can be handed off to claude harness

All internal tooling is exposed via MCP to our agents. All request and entity data is hyperlinked making it easy to nav from a single request -> actions -> events -> data from within a local web app instance. Per-request telemetry means one click to view the related data and logs

To help build @OpacityHQ, we've built a significant amount of internal tooling to help manage worktrees, run multiple local app instances without colliding, and have deeply integrated server-side and browser-side tooling to measure performance, telemetry, visualize data, etc.