Install
Docs, RFCs & Knowledge
Decision records, onboarding docs, runbooks, and internal wikis.
- 5 Tracked terms
- Last 30 days Feed window
What this topic collects on
An article joins this feed when it matches these terms. Each one is also a search of its own.
Related topics
Latest in Docs, RFCs & Knowledge
Zero-Signup Docs MCP: How to Query Technical Documentation Directly Inside Cursor
11+ hour, 22+ min ago (343+ words) If you use Cursor, Windsurf, or Claude Code to build software, you have inevitably encountered the "Hallucinated API" problem: The typical workaround is frustrating: you switch tabs, find the official documentation website, copy-paste 3 pages of markdown into the Cursor chat…...
How i documented a Broken codebase without losing my mind.
12+ hour, 12+ min ago (235+ words) If you want to use it straight away | Link here I believe we achieved a point in tech where having a... Tagged with documentation, github, softwareengineering....
How I keep a game companion site from lying to its readers
21+ hour, 52+ min ago (574+ words) Game companion sites have a trust problem. A build guide can be correct on Tuesday, broken by Friday's patch, and still look authoritative three weeks later. If the data lives directly in React components, nobody notices until a reader points…...
Your README Is Lying to New Contributors
1+ day, 4+ hour ago (320+ words) Here's an experiment: pick five repos you starred in the last year. Clone one. Follow the README's setup instructions exactly. I'll wait. How many worked on the first try? In my experience, maybe two. The rest have that familiar smell…...
676 published documents kept their own history. Six kept different words.
1+ day, 2+ hour ago (1351+ words) That risk is real, it is old, and it is well documented. What I could not find anywhere was a number. How often does it actually happen in documents that are already published, on real government and institutional websites, today?...
My AI wrote API docs. Then a parser fact-checked it.
1+ day, 8+ hour ago (279+ words) Let me tell you how API docs die. Nobody decides to let them rot. You ship a feature on Tuesday, promise yourself you'll update the docs on Wednesday, and by Friday something else is on fire. Six months later your…...
Draft Changelog Inventory From Git; Keep Upgrade Claims in a Reviewer Contract
1+ day, 9+ hour ago (958+ words) Generated release notes fail when they treat narrative bullets as contracts that users can follow during an upgrade. A model can inventory commits, paths, and symbols, but it cannot honestly promise a migration path. This workflow keeps those jobs in…...
Why a Searchable Database Wasn’t Enough: Building the Human Documentation Layer
1+ day, 7+ hour ago (1660+ words) How I use fixed source checkpoints, structured module pages, logical IDs, read-back verification, and resumable publication to turn searchable project evidence into documentation people can actually understand. AI assistance disclosure: This article is based on my own project experience and…...
Why You Should Not Commit Your Specs
2+ day, 6+ hour ago (1303+ words) When I say "specs" in this article I mean specs as understood in AI assisted Spec Driven Development: markdown files that describe a change before an LLM implements it. I am NOT talking about OpenAPI, AsyncAPI or similar formats, and…...
Generate How-To Skeletons From Signatures, Then Gate README Promises With a Lane File
2+ day, 11+ hour ago (491+ words) The table below is the contract. Draft text may occupy only the left column. Anything that implies a working machine, a supported version, or a legal reading belongs on the right, even if the model could phrase it smoothly. The…...