Reusable prompts and slash commands
This is the sixth post in our series on the AI engineering toolkit. The previous one cut off the edit tool until the agent had read enough to write down a plan. This one is ...
Read more ⟶
This is the sixth post in our series on the AI engineering toolkit. The previous one cut off the edit tool until the agent had read enough to write down a plan. This one is ...
Read more ⟶
The most capable AI model gets pulled because it turns dangerous once the guardrails come off. Any model gets jailbroken within days regardless. If that is where we are, have we hit a quiet ceiling ...
Read more ⟶
This is the second post in a series on the AI engineering toolkit. The first one moved you into the terminal. This one teaches the agent about the project you work in, so you stop ...
Read more ⟶
Ode to the software engineer The plan is what separates spec-driven development from vibe coding. It is the most important lever for the long-term health of your codebase, and the place where the role of ...
Read more ⟶
This is the fifth post in a series on the AI engineering toolkit. The first one moved you into the terminal, the second taught the agent your conventions, the third covered the context window, and ...
Read more ⟶
This is the third post in a series on the AI engineering toolkit. The first one moved you into the terminal, and the second taught the agent your project’s conventions. Both of those write something ...
Read more ⟶
This is the first post in a series on the AI engineering toolkit. It runs from terminal-curious to fairly advanced and has no planned end. The early posts will be simple, maybe too simple if ...
Read more ⟶
This is the fourth post in our series on the AI engineering toolkit. The first one moved you into the terminal, the second taught the agent your project’s conventions, and the third covered the context ...
Read more ⟶
If you spent any time around AI tooling this year, you watched “harness” go from a word nobody used to one in every changelog, blog post, and conference slide. Anthropic’s own docs describe Claude Code ...
Read more ⟶
Engineering is hard Let me start with a couple stories. A team picks up notification preferences, the kind of feature where users choose how they want to be contacted. Brief discussion, general agreement, shipped in ...
Read more ⟶
This is the sixth post in our series on the AI engineering toolkit. The previous one cut off the edit tool until the agent had read enough to write down a plan. This one is ...
Read more ⟶
This is the fourth post in our series on the AI engineering toolkit. The first one moved you into the terminal, the second taught the agent your project’s conventions, and the third covered the context ...
Read more ⟶
This is the third post in a series on the AI engineering toolkit. The first one moved you into the terminal, and the second taught the agent your project’s conventions. Both of those write something ...
Read more ⟶
This is the second post in a series on the AI engineering toolkit. The first one moved you into the terminal. This one teaches the agent about the project you work in, so you stop ...
Read more ⟶
Engineering is hard Let me start with a couple stories. A team picks up notification preferences, the kind of feature where users choose how they want to be contacted. Brief discussion, general agreement, shipped in ...
Read more ⟶
This is the fifth post in a series on the AI engineering toolkit. The first one moved you into the terminal, the second taught the agent your conventions, the third covered the context window, and ...
Read more ⟶
The most capable AI model gets pulled because it turns dangerous once the guardrails come off. Any model gets jailbroken within days regardless. If that is where we are, have we hit a quiet ceiling ...
Read more ⟶
If you spent any time around AI tooling this year, you watched “harness” go from a word nobody used to one in every changelog, blog post, and conference slide. Anthropic’s own docs describe Claude Code ...
Read more ⟶
This is the first post in a series on the AI engineering toolkit. It runs from terminal-curious to fairly advanced and has no planned end. The early posts will be simple, maybe too simple if ...
Read more ⟶
Ode to the software engineer The plan is what separates spec-driven development from vibe coding. It is the most important lever for the long-term health of your codebase, and the place where the role of ...
Read more ⟶
This is the sixth post in our series on the AI engineering toolkit. The previous one cut off the edit tool until the agent had read enough to write down a plan. This one is ...
Read more ⟶
This is the fifth post in a series on the AI engineering toolkit. The first one moved you into the terminal, the second taught the agent your conventions, the third covered the context window, and ...
Read more ⟶
This is the fourth post in our series on the AI engineering toolkit. The first one moved you into the terminal, the second taught the agent your project’s conventions, and the third covered the context ...
Read more ⟶
The most capable AI model gets pulled because it turns dangerous once the guardrails come off. Any model gets jailbroken within days regardless. If that is where we are, have we hit a quiet ceiling ...
Read more ⟶
This is the third post in a series on the AI engineering toolkit. The first one moved you into the terminal, and the second taught the agent your project’s conventions. Both of those write something ...
Read more ⟶
If you spent any time around AI tooling this year, you watched “harness” go from a word nobody used to one in every changelog, blog post, and conference slide. Anthropic’s own docs describe Claude Code ...
Read more ⟶
This is the second post in a series on the AI engineering toolkit. The first one moved you into the terminal. This one teaches the agent about the project you work in, so you stop ...
Read more ⟶
This is the first post in a series on the AI engineering toolkit. It runs from terminal-curious to fairly advanced and has no planned end. The early posts will be simple, maybe too simple if ...
Read more ⟶
Engineering is hard Let me start with a couple stories. A team picks up notification preferences, the kind of feature where users choose how they want to be contacted. Brief discussion, general agreement, shipped in ...
Read more ⟶
Ode to the software engineer The plan is what separates spec-driven development from vibe coding. It is the most important lever for the long-term health of your codebase, and the place where the role of ...
Read more ⟶