{
  "id": 10435263,
  "title": "The Real Reason AI Ignores Existing Decisions — Designing an ADR Context Auto-Injection Hook",
  "url": "https://urgent.news/2026/09/28/the-real-reason-ai-ignores-existing-decisions-designing-an-adr",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-28T11:51:03.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/uehara/the-real-reason-ai-ignores-existing-decisions-designing-an-adr-context-auto-injection-hook-34e2"
  },
  "original_language": "en",
  "account": "In May 2026, the author was working on a Claude Code plugin designed to share a consistent approach across various development projects. One component of this plugin involved handling past design decisions in subsequent sessions. The journey began with the selection of a document-editing library. While one product opted for BlockNote over TipTap, the AI suggested incorporating TipTap two weeks later. The issue lay in the AI not being able to access the Architecture Decision Record (ADR) contents at the start of a session, despite the existence of the ADR.\n\nTo address this, the author crafted a script that read the project's ADRs, extracted key details like the document number, title, and status for accepted or amended records, and injected this information into the context via a Claude Code hook. Initially, the hook triggered on every turn, but this was later refined to run at the session's start, reducing the median startup time from 3,842ms to 94.7ms. Further optimizations included consolidating the process to read all ADR files in a single command, significantly speeding up the process.\n\nThe plugin's primary objective was to facilitate reusable working methods across various projects. It served as a bridge between recorded design decisions and their implementation. This was achieved by delivering a list of current design decisions into the context during the session start, but the responsibility of selecting the relevant documents and incorporating the decisions into the implementation was left to subsequent stages.\n\nThe initial attempt at implementing TipTap as an alternative to BlockNote, which was chosen due to its out-of-the-box capabilities, resulted in the AI proposing the latter just a few days after. This decision was made based on BlockNote's compatibility with the project's requirements, such as Notion-like block operations and ease of integration. Despite the AI suggesting TipTap, the project reverted to BlockNote after a brief experiment, highlighting the complexities of AI decision-making in design contexts.",
  "summary": "TL;DR (about a 15-minute read) In May 2026, I was reworking a Claude Code plugin that delivers a shared way of working to several development projects. One of its targets was a mechanism for carrying past design decisions forward into the next session. It started with a choice of document-editing library. In one product, an Architecture Decision Record (ADR, a document that captures a design…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}