Found 11 posts in category AI Tools
I needed a logo for a presence that already existed: a handle, open-source work, and more than a decade online. Silhouette is the Grok Bot distilled from the three-hour run that built it in stages: discovery, ideation and an anti list, shapes, type, and then the whole mark, wordmark, and spacing locked as one silhouette.
Latch v1 gave the agent hands. Version 2 adds bounded recovery for that path: a LaunchAgent that relaunches Grok Bot when the process is down or the heartbeat is stale, an optional outside heal request for disconnects the Mac cannot see, and a bounded way for Latch to operate Grok Bot's own UI when structured tools run out. Relaunch proven on self-heal kit 1.4.2; current kit 1.5.0 adds observe-only logging for silent cloud drops.
The bot had a computer. The next step needed to happen on mine. Latch is a specialist Grok Bot for the small, authorized desktop interactions that stall larger workflows: mouse first, clipboard over keystrokes, screenshot receipts, and a hard hand-back. This is the story of building it, including the keyboard lockout that wrote most of its rules.
Codex has become the center of my development workflow, and the model is only part of the reason. Sessions that read other sessions, voice steering, goal mode, side chats, subagents on request, MCP, and an app server other harnesses can drive: the environment around the model is where the work happens now. Coding assistant is no longer a complete description.
A magic prompt is not a clever wall of instructions. It is a small, portable entry point into an engineered, tested workflow that takes a human and an agent from intent to a verified outcome — pre-flight, prerequisites, installation, authentication, validation, and the next step included. Here is how it should behave, and how to build one in layers.
Every week there is a new must-have AI tool, and somewhere inside the buzz there is usually a grain of truth. Buzzcut is a small agent whose only job is to find that grain: map the shiny new thing against what you already run and return keep, skip, or watch, with one flip condition. Not anti-hype. Anti-hype-driven architecture.
The pull request used to be finished code waiting to be merged. With agents doing most of the building, it has quietly become something more: a rich research and communication artifact — without shedding the code review and compliance checks that made it trustworthy in the first place.
Not every piece of context an AI coding agent sees carries the same weight. The user prompt and the code dominate; documentation is a secondary orientation layer. Here's why imperfect docs are usually good enough, and where your effort actually pays off.
AI can produce code, comments, PR descriptions, and review replies faster than humans can read and own them. The real bottleneck is no longer generation — it's comprehension. Here's how I think about effort symmetry, accountability, and why I don't buy a universal taxonomy.
Documentation drift is the silent killer of codebases. Your roadmap says one thing, your website another, and your README hasn't been updated in months. Here's how I built a pluggable Claude Code skill that detects drift, shows exactly what's out of sync, and fixes it—with your approval.
How I built an automated system that generates social images for blog posts using multiple AI providers, with Claude analyzing results and a PR comment interface for human-in-the-loop selection. A case study in agent-orchestrated workflows.