<?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>Claude on Mohammed Fayasuddin</title><link>https://fayasuddin.blog/tags/claude/</link><description>Recent content in Claude on Mohammed Fayasuddin</description><generator>Hugo -- 0.151.0</generator><language>en-us</language><lastBuildDate>Sat, 15 Aug 2026 12:00:00 +0530</lastBuildDate><atom:link href="https://fayasuddin.blog/tags/claude/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Custom AI Skills and Pipelines: A Practical Guide</title><link>https://fayasuddin.blog/posts/building_custom_ai_skills_and_pipelines/</link><pubDate>Sat, 15 Aug 2026 12:00:00 +0530</pubDate><guid>https://fayasuddin.blog/posts/building_custom_ai_skills_and_pipelines/</guid><description>&lt;p&gt;If you&amp;rsquo;ve spent any time working with AI coding assistants, you&amp;rsquo;ve probably hit the same wall: they&amp;rsquo;re great at generating one-off snippets, but trying to use them for a real project that spans days or weeks? It falls apart. Context gets lost. Plans drift. You end up repeating yourself over and over. The dream of &amp;ldquo;just tell the AI what to build and ship it&amp;rdquo; dies somewhere between the third context reset and the tenth broken import.&lt;/p&gt;</description></item></channel></rss>