Always apply the rules defined in anti-ai-writing-style.md for writing style, tone, structure, and final cleanup.

CorebaseIT posts should be written in a professional white-paper or technical-journal style: authoritative, evidence-based, well-structured, and technically accurate.

Open posts with a structural, white-paper lede, not a personal hook. The first paragraph defines the problem class and reframes it precisely (e.g. “a state-management problem rather than a bug”); the second states the scope of the post and the concrete mechanisms it will cover. Save first-person “this is the failure that keeps me up at night” style openers for LinkedIn. First-person experience is still allowed later in the body, but only where it rides on a concrete mechanism (e.g. “Most duplicate-charge incidents I have seen come from…”).

Images (Stack theme): the front-matter image: field is rendered automatically as the featured image at the top of the post, and it also powers the OpenGraph, Twitter card, and JSON-LD image. So set image: to the hero/lead diagram and do NOT also add an inline <img> for that same image in the body — that produces a duplicate at the top. Use inline <img> only for additional in-body diagrams. Use the static path /diagrams/<file> or /images/<file>, and the file must exist under static/.