<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ESLint on Coderrob</title><link>https://coderrob.com/tags/eslint/</link><description>Recent content in ESLint on Coderrob</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 10 Feb 2026 10:00:00 -0600</lastBuildDate><atom:link href="https://coderrob.com/tags/eslint/index.xml" rel="self" type="application/rss+xml"/><item><title>Announcing ESLint Zero-Tolerance AI Anti-Slop Rules</title><link>https://coderrob.com/posts/announcing-eslint-zero-tolerance-ai-anti-slop-rules/</link><pubDate>Tue, 10 Feb 2026 10:00:00 -0600</pubDate><guid>https://coderrob.com/posts/announcing-eslint-zero-tolerance-ai-anti-slop-rules/</guid><description>&lt;p&gt;AI-assisted development has a trust problem.&lt;/p&gt;
&lt;p&gt;Generated code can look polished, type-safe, and reviewable while still smuggling in shortcuts that quietly erode a codebase over time. The faster teams move with agents, the more those shortcuts compound.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;ESLint Zero-Tolerance&lt;/strong&gt; is my attempt to put hard boundaries around those patterns in TypeScript projects: not as abstract guidance, but as enforceable rules and presets that make low-trust code harder to ship.&lt;/p&gt;
&lt;h2 id="the-announcement"&gt;The Announcement&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;ve published the &lt;strong&gt;ESLint Zero-Tolerance AI anti-slop rules&lt;/strong&gt; here:&lt;/p&gt;</description></item></channel></rss>