Entropy, Engineered

Work That Survives the Night: Beads for Multi-Session Tasks

Plan mode gives you a document. Beads gives you a graph of work with dependencies that the agent understands. Tasks small enough to survive context loss, blocking relationships that prevent premature work.



Claude Code Plugins: From Prompts to Packaged Expertise

A prompt is a one-time instruction. A plugin packages expertise into something that persists — commands you invoke, skills that load on demand, hooks that run automatically.



Stop Using Claude Code Like a Copilot

Most developers use maybe 10% of what Claude Code can do. Five pillars unlock the rest: context, skills, verification, persistence, and scaling.


AI for Call Preparation, Not Calling

Technical sales requires preparation, not automation. We spend 10x more preparing for a call than making it. AI handles research. The call itself? That's human.


Clay Can't Be Your Source of Truth

Rows don't know about each other. That single constraint means Clay can't track prospects over time, merge records, or maintain history. Here's why — and what to do about it.


Your Portfolio as Markdown Files

AI coding agents are the most capable tools we have. Your sales knowledge should be queryable by them. Here's how to set it up in 30 minutes.


Don't Trust the Model, Use a Framework

A practitioner's guide to defending against prompt injection. Structured outputs, trust boundaries, and patterns that actually work.



The Agent Skills, Part 1: The Diagnosis

Why 95% of Claude Code skills fail — and what actually works. Most AI skills are system prompts in a trench coat. Here's the diagnosis.




The Agent Skills, Part 4: The Playbook

How to build Claude Code custom commands that work. The 5-phase process: archaeology, stress test, codification, compilation, and QA audit.