<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Narrative on Top AI Skills</title><link>https://topaiskills.com/tags/narrative/</link><description>Recent content in Narrative on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/narrative/index.xml" rel="self" type="application/rss+xml"/><item><title>I Let AI Agents Refactor My React Codebase — The Results Were Brutally Honest</title><link>https://topaiskills.com/tutorials/guides/ai-agent-refactoring-experience/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/ai-agent-refactoring-experience/</guid><description>&lt;h2 id="most-ai-refactoring-advice-is-useless-without-context"&gt;Most AI Refactoring Advice Is Useless Without Context&lt;/h2&gt;
&lt;p&gt;I spent three weeks letting AI coding agents refactor a medium-sized React app — about 15K lines across 80 components. The results: some genuinely clever improvements, a few WTFs, and one incident that dropped our test coverage by 12%. Here is the raw breakdown.&lt;/p&gt;
&lt;h2 id="the-setup-why-my-codebase-needed-a-strangers-opinion"&gt;The Setup: Why My Codebase Needed a Stranger&amp;rsquo;s Opinion&lt;/h2&gt;
&lt;p&gt;My team&amp;rsquo;s React app started life as a quick prototype. Two years and six developers later, it is a production app with 80+ components, a custom design system that nobody documented, and a test suite that started at 92% coverage but had been slowly bleeding. We knew the code needed love, but nobody had the time to audit every component.&lt;/p&gt;</description></item><item><title>I Let AI Handle My Team's Approval Workflow for a Week — Here's What Happened</title><link>https://topaiskills.com/tutorials/guides/ai-approval-workflow-experiment/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/ai-approval-workflow-experiment/</guid><description>&lt;p&gt;I handed my AI agent control over our team&amp;rsquo;s approval workflow for five days. Expense reports, leave requests, purchase orders — all processed through an AI skill. Here is what went right, what broke, and whether I would do it again.&lt;/p&gt;
&lt;h2 id="why-i-decided-to-try-this"&gt;Why I Decided to Try This&lt;/h2&gt;
&lt;p&gt;Our team runs on Lark. I manage a group of fifteen engineers, a couple of product managers, and a rotating cast of interns. Every week brings a steady stream of approval requests. Leave applications, hardware purchase requests, conference travel approvals, expense reports from team lunches — the kind of administrative overhead that is simple but constant.&lt;/p&gt;</description></item><item><title>I Let My AI Agent Manage Lark Documentation for a Week — Here's What Happened</title><link>https://topaiskills.com/tutorials/guides/lark-doc-narrative-experience/</link><pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/lark-doc-narrative-experience/</guid><description>&lt;h2 id="why-i-put-documentation-on-the-chopping-block"&gt;Why I Put Documentation on the Chopping Block&lt;/h2&gt;
&lt;p&gt;Our team lives inside Lark (Feishu). Meeting notes, technical specs, project briefs, onboarding guides — it is all in Lark documents. And like most teams that use collaborative docs heavily, we have a mess: 40+ documents scattered across spaces with inconsistent naming conventions, outdated meeting notes that nobody archived, and a growing pile of &amp;ldquo;untitled document&amp;rdquo; orphans that were created during a call and never revisited.&lt;/p&gt;</description></item><item><title>I Generated 100 AI Images From My Coding Assistant</title><link>https://topaiskills.com/tutorials/guides/ai-image-generation-experiment/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/ai-image-generation-experiment/</guid><description>&lt;h2 id="why-i-went-down-this-rabbit-hole"&gt;Why I Went Down This Rabbit Hole&lt;/h2&gt;
&lt;p&gt;Thursday afternoon, 3 PM. I was building a landing page for a side project and needed a hero image. Not a placeholder — something that actually looked like the product. My usual workflow is: write a prompt in ChatGPT, download the image, drag it into the project folder. Then tweak the prompt, repeat. Every iteration costs a context switch.&lt;/p&gt;
&lt;p&gt;I remembered the &lt;a href="https://topaiskills.com/skills/image/ai-image-generation/"&gt;ai-image-generation&lt;/a&gt; skill sitting in my installed list from when I first set up inference.sh. I had never actually used it. The idea of generating images without leaving the terminal seemed convenient in theory, but I was skeptical about output quality compared to Midjourney or the ChatGPT web interface.&lt;/p&gt;</description></item></channel></rss>