<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OMGfixMD — Blog</title>
    <link>https://omgfixmd.com/blog</link>
    <description>A field manual for giving LLMs precise, multi-point feedback. Diagnoses, playbooks, and per-tool recipes for Claude, ChatGPT, Cursor, Gemini, and AI-builder surfaces like Lovable.</description>
    <language>en-us</language>
    <copyright>© 2026 Elad Diamant</copyright>
    <lastBuildDate>Sun, 26 Apr 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://omgfixmd.com/rss.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://omgfixmd.com/og.png</url>
      <title>OMGfixMD — Blog</title>
      <link>https://omgfixmd.com/blog</link>
    </image>

    <item>
      <title>Why typing feedback to the AI stops working at five corrections</title>
      <link>https://omgfixmd.com/blog/why-typing-feedback-into-the-chat-stops-working</link>
      <guid isPermaLink="true">https://omgfixmd.com/blog/why-typing-feedback-into-the-chat-stops-working</guid>
      <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
      <description>The chat box doesn't fail at five corrections. It fails at three. By the fourth, the reviewer is knowingly shipping a message they expect the model to mis-target — some shipped feedback beats none — and the fifth correction lives its entire life inside their head. A close-read diagnostic of the typing-the-feedback failure mode, scene by scene.</description>
    </item>

    <item>
      <title>Why ChatGPT rewrites the whole document when you only asked for one fix</title>
      <link>https://omgfixmd.com/blog/chatgpt-rewrites-whole-document-when-i-ask-for-edits</link>
      <guid isPermaLink="true">https://omgfixmd.com/blog/chatgpt-rewrites-whole-document-when-i-ask-for-edits</guid>
      <pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate>
      <description>You asked for one small edit. It came back as a different document. Not your prompt — the chat box has no target selection, so every ask reopens the whole file. Here's what's actually happening and the format that stops it.</description>
    </item>

    <item>
      <title>A prompt that gets Claude to only edit the passages you named</title>
      <link>https://omgfixmd.com/blog/prompt-to-edit-only-specific-passages</link>
      <guid isPermaLink="true">https://omgfixmd.com/blog/prompt-to-edit-only-specific-passages</guid>
      <pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate>
      <description>Every "only edit X, leave the rest alone" prompt ranked by reliability, with the honest answer about why none of them work on their own — and the paired-passage format that does. Copy-pasteable templates included.</description>
    </item>

    <item>
      <title>Claude Projects vs attaching a doc: which actually keeps your edits scoped?</title>
      <link>https://omgfixmd.com/blog/claude-projects-vs-attaching-doc-scoped-edits</link>
      <guid isPermaLink="true">https://omgfixmd.com/blog/claude-projects-vs-attaching-doc-scoped-edits</guid>
      <pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate>
      <description>Projects promise persistent context. Attachments promise fresh reads. Neither scopes your edits. A frank comparison of both, plus the format that does keep Claude editing only the passages you named.</description>
    </item>

    <item>
      <title>How to give Cursor feedback on a long Markdown file (without it rewriting half the README)</title>
      <link>https://omgfixmd.com/blog/give-cursor-feedback-long-markdown-file</link>
      <guid isPermaLink="true">https://omgfixmd.com/blog/give-cursor-feedback-long-markdown-file</guid>
      <pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate>
      <description>Cursor's tools are tuned for code, where ambiguity is rare. Long Markdown prose has more ambiguity per line — and Cursor edits it like code, which is why the README keeps coming back rewritten. The playbook for keeping prose edits scoped.</description>
    </item>

    <item>
      <title>Lovable feedback: how to edit one component without regenerating the app</title>
      <link>https://omgfixmd.com/for/lovable</link>
      <guid isPermaLink="true">https://omgfixmd.com/for/lovable</guid>
      <pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate>
      <description>Lovable is great at the first screen and harder at the fifth edit. Here is the feedback pattern that keeps scope tight — quote the exact span of the generated Markdown or copy that needs a change, pair it with a note, send the whole batch in one turn. Works from the chat box, works better with a tool.</description>
    </item>

    <item>
      <title>How to give Claude or ChatGPT feedback on 5 things at once (without it rewriting everything)</title>
      <link>https://omgfixmd.com/blog/give-llm-feedback-multiple-passages</link>
      <guid isPermaLink="true">https://omgfixmd.com/blog/give-llm-feedback-multiple-passages</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <description>The chat box loses at multi-point feedback. Every LLM user hits this wall around comment five. Here is the pattern that actually works — paired passages with notes — with a manual recipe for anyone, and a tool for anyone tired of doing it by hand.</description>
    </item>

    <item>
      <title>The Comment Box Your LLM Doesn't Have — The OMGfixMD Manifesto</title>
      <link>https://omgfixmd.com/manifesto</link>
      <guid isPermaLink="true">https://omgfixmd.com/manifesto</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <description>Every LLM user hits the same wall around the fifth comment: the chat box is a text area, and structured feedback on a 1,800-word answer is not prose input. A manifesto for why LLM answers need a feedback layer — and what it looks like when somebody bothers to build one.</description>
    </item>

<item>
      <title>How to add comments to a Markdown file (2026 edition — with the LLM case the old methods don't cover)</title>
      <link>https://omgfixmd.com/blog/how-to-comment-on-markdown</link>
      <guid isPermaLink="true">https://omgfixmd.com/blog/how-to-comment-on-markdown</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <description>Markdown has no native comment syntax. Every practical method — HTML comments, Google Docs, Notion, GitHub PR, Slack, purpose-built comment layers — ranked, with the 2026 case that matters most: giving the file back to the language model that wrote it.</description>
    </item>

  </channel>
</rss>
