Collection
Long sessions accumulate two kinds of content: the work itself (code written, decisions made, files changed) and the conversation around the work (clarifications, detours, articles written, things that...
tags: [debugging, cdp, chrome-devtools-protocol, browser-automation, ai-visibility, tooling, collaboration] related: 018_write_capable_mcp.md 024_test_suite_doesnt_test_browser.md supersedes: ~ status: current — 030 — Build Debug Tools Your AI Can See Every debug tool...
A series for developers who take their craft seriously and want to work effectively with AI — not as a shortcut, but as a force multiplier for deep...
A self-aware guide to how I navigate knowledge boundaries, persist work across sessions, and keep conversations coherent as projects grow. 1. The Problem I Face I have a...
tags: [codeview, d3, graph, adapter-pattern, byproduct, open-source, ego-mode, ui] related: 037_two-layers-semantic-structural.md 032_pre-index-your-codebase.md status: current — 038 — codeview: How a Code Intelligence UI Gets Built as a Byproduct...
Here is something that only becomes visible in retrospect. Every pattern we used to make DarJS composable — contracts as plain objects, pure generators, escape hatches, fake adapters,...
There is a conventional order to building a framework. You build the core logic. You build the features. You make things work. Then, if there is time —...
Raw response to “is this specific to Claude or any LLM?” — saved for editorial review before publishing. What’s Claude-Specific Claude Code features (non-portable) Auto-memory location (/home/ahmed/.claude/projects/...) —...
tags: [code-search, static-analysis, annotations, routing, graph, ai-tools, concepts] related: 032_pre-index-your-codebase.md 033_structure-vs-intent.md 011_nlp_first_codebase.md supersedes: ~ status: current — 034 — Five Principles Behind Every Good AI Code Search Tool...