Botmonster Tech

Pair Meilisearch v1.12’s fast REST API with HTMX 2.0’s hx-get and hx-trigger attributes, and you get a real-time, typo-tolerant search box that returns results in under 50ms. You write no custom JavaScript and pull in no React or Vue. The server renders HTML fragments that HTMX swaps into the DOM, so the whole search box stays under 15 KB of total JS. This post covers the full setup, from Docker Compose to a working search UI with faceted filtering.

Service workers give you a programmable network proxy right inside the browser. They sit between your page and the server, intercept every fetch request, and let you decide whether to serve a response from cache or from the network. For static sites - where every page is a pre-built file and every asset has a predictable URL - this is a natural fit. A well-configured service worker makes your static site load in single-digit milliseconds on repeat visits, work fully offline, and pass every Lighthouse PWA audit. The entire implementation fits in a single JavaScript file under 100 lines.

I get better output from Claude Code by adding fewer tools, not more. Piling on MCP servers rarely helps, but the right official marketplace plugins, CLI tools, and skills do. Start with /plugin and picks like typescript-lsp and security-guidance, then add Supabase CLI, Playwright, GitHub CLI, and the GSD framework. That stack handles code, deploys, research, and browser work on its own.

When I first found Claude Code, I tried to connect every MCP server I could find. Within a week, the agent felt slower and less decisive, and it often picked the wrong tool for the job. The fix was almost always a smaller, more careful toolset.

Alembic is the standard migration tool for SQLAlchemy projects. You run alembic init, point it at your SQLAlchemy models, and use alembic revision --autogenerate to produce migration scripts. Alembic then applies those scripts in order with alembic upgrade head. You get repeatable, reviewable schema changes that work the same way everywhere your app runs. The latest stable release is Alembic 1.18.4. It supports SQLAlchemy 2.0 (now at 2.0.48) and its modern typed APIs.

Claude Code Agent Teams is an experimental feature, live since v2.1.32. It lets you run 2-16 Claude Code sessions under one team lead. Each teammate gets its own context window and full tool access. They talk through a shared task list and direct peer-to-peer messages. You turn it on with one config change, then describe the team you want in plain language. Claude handles the spawning, the assignment, and the coordination. The feature shines on work you can split up: multi-file refactors, cross-layer feature builds, and research-and-review jobs. The catch is that it costs 3-7x more tokens than a single session, and it cannot resume a session.

The single most important file in any Claude Code project is CLAUDE.md - a persistent instruction set that loads every session and shapes how the agent reads, writes, and verifies code. But CLAUDE.md alone is not what separates productive setups from fragile ones. The real productivity stack in 2026 combines CLAUDE.md conventions with on-demand skills, deterministic hooks, and git worktree isolation for running 10-15 parallel sessions against a single repository. Each session is scoped to one task, operating in its own branch, turning a solo developer into a small engineering team .