<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Design-Doc on Gene Gi's Blog</title><link>https://genegi.github.io/tags/design-doc/</link><description>Recent content in Design-Doc on Gene Gi's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://genegi.github.io/tags/design-doc/index.xml" rel="self" type="application/rss+xml"/><item><title>How to write a design doc in the AI era</title><link>https://genegi.github.io/posts/how-to-write-a-design-doc-in-ai-era/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>https://genegi.github.io/posts/how-to-write-a-design-doc-in-ai-era/</guid><description>AI can draft a design doc cheaply, but iterating on it means reviewing your own document — and attention fades. Why design docs still matter for alignment, and my workflow: research with AI, write your own ideas, let AI polish and cross-reference.</description></item></channel></rss>