<?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>AI on Severin Bucher | Blog</title><link>https://severinbucher.com/tags/ai/</link><description>Recent content in AI on Severin Bucher | Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 18 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://severinbucher.com/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Teaching Your AI to Use Your Component Library</title><link>https://severinbucher.com/posts/teaching-your-ai-to-use-your-component-library/</link><pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate><guid>https://severinbucher.com/posts/teaching-your-ai-to-use-your-component-library/</guid><description>&lt;p>AI coding assistants keep hallucinating EUI props. You paste in documentation, it gets ignored thirty messages later. You end up debugging code where half the props don&amp;rsquo;t exist.&lt;/p>
&lt;p>The fix is an MCP server, about 200 lines of TypeScript that gives any MCP-compatible AI direct access to the EUI source.&lt;/p>
&lt;h2 id="what-eui-is">What EUI is&lt;/h2>
&lt;p>EUI (Elastic UI) is Elastic&amp;rsquo;s open-source React component library. It powers Kibana and the rest of the Elastic product suite. The library is large, over 100 components spanning basic buttons and forms, complex data grids, drag-and-drop interfaces, and charting primitives. Each component ships with TypeScript types, MDX documentation, and Storybook stories.&lt;/p></description></item></channel></rss>