content-article-draftlisted

# content-article-draft — Article draft Goal: turn material into a **first working draft** of a 3-10k character article. Not a final version — the user polishes that themselves. The draft needs the right skeleton and tone. Before starting, read: - `~/.claude/rules/content-voice.md` - `~/.claude/rules/content-formatting.md` — the articles section ## Step 1. Context Ask: - **the topic** in one sentence - **the audience**: technical specialists at a certain level? Managers? Beginners? - **the platform**: Habr / Medium / dev.to / personal blog / Telegraph? - **the source material**: notes, experience, a project, an existing draft? - **the article's goal**: teach something / share experience / break down a case / a provocative essay? ## Step 2. Formulate the thesis An article's thesis is **a single claim** that the author defends or illustrates. Not a topic, but a claim. | Topic (bad) | Thesis (good) | |--------------|----------------| | "Microservices" | "Microservices are only worth the complexity when you genuinely have different release cycles or languages" | | "Postgres vs Mongo" | "For most startups, Postgres covers 95% of the needs, and the remaining 5% don't justify a second database" | | "My experience with k8s" | "After a year running k8s in production, I realized the main risk isn't complexity, but the blurring of SRE vs. dev responsibility" | Show the thesis to the user and **ask them to confirm or correct it**. The thesis is the foundation. ## Step 3. Build