• agentfiles, dotfiles but for agents

    Sometimes I want to refer to my agents setup or people ask me what my configuration looks like. For general system configuration dotfiles are used so I am going to share my agent configuration in what I'll just call "agentfiles". I do have a private dotfiles repository but I am n…

  • Creating architecture diagrams with C4 and coding agents

    LLMs can draw diagrams, but you get better results with a conceptual model, a validation loop, and a lightweight verification pass against the codebase than with free-form diagramming. I used the C4 model extensively to map architecture landscapes. Last week I saw an opportunity …

  • A skill to support TIL creation

    Skills are a great way to introduce capabilities in your agent flows. To support my "The Day I Learned" repository and website, I created a skill to extract learnings from coding and LLM sessions. The skill below is installed in my global agent settings (AGENTS.md), and from each…

  • Experience report: Site update using coding agents and Beads

    This is an experience report on updating my (this!) website using coding agents and Beads ('a distributed, git-backed graph issue tracker for AI agents.'). Site update using coding agents Over the past week, I used coding agents to update my website. The result is, at least I hop…

  • Harness Engineering

    Today I heard the term “harness engineering” for the first time: Harness engineering is the practice of building tooling, tests, and automation that let coding agents execute tasks safely and reliably. If code is written more and more by LLMs, the focus seems to be shifting to …

  • Combining agent skills

    A short post on combining skills. It's not always clear when a skill will be called or triggered. The easiest way is to put instructions and directly invoke the skill you want by name. For example, for my Today I Learned mini blog site, I have two skills to keep my TILs focussed …

  • Experience Report: Building a time-tracking AI assistant

    This is a short experience report about using skills (with Codex and its models) to build a personal AI assistant that helps me maintain my time-tracking log. To set expectations: the assistant does not manage my calendar or tasks. It helps me keep a time-tracking log that lives …

  • Agent Chisels: My LLM Agent Skills and Workflows

    I have been meaning to share more about my LLM workflows and tooling for a while, partly to have a reference for conversations, but mostly to learn in public. Agent Chisels is where I will be sharing the custom artefacts (primarily skills, with commands and agents to follow) that…

  • Grounded decision records from AI conversations

    If you've read some of my posts before or worked with me, you know I like using Architectural Decision Records (ADRs) for lots of reasons. To me the most important one is documenting the why of a decision. If you've worked with AI models before, you've probably asked them for opt…

  • Using Code Coverage as a Check for Test Refactoring

    TLDR: Use code coverage reports to verify that test refactorings haven't accidentally changed what functionality you're testing. Same coverage percentage before and after refactoring gives confidence your tests still cover the same code paths. If we refactor code, tests should co…