<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Andrii Poluosmak</title>
    <description>The latest articles on DEV Community by Andrii Poluosmak (@croffasia).</description>
    <link>https://dev.to/croffasia</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1401423%2F6bb1bd1c-a43b-4712-985e-3d3efe7c1076.jpg</url>
      <title>DEV Community: Andrii Poluosmak</title>
      <link>https://dev.to/croffasia</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/croffasia"/>
    <language>en</language>
    <item>
      <title>From AI chaos to clean code</title>
      <dc:creator>Andrii Poluosmak</dc:creator>
      <pubDate>Fri, 17 Oct 2025 11:36:40 +0000</pubDate>
      <link>https://dev.to/croffasia/from-ai-chaos-to-clean-code-f39</link>
      <guid>https://dev.to/croffasia/from-ai-chaos-to-clean-code-f39</guid>
      <description>&lt;p&gt;&lt;strong&gt;Hey Developers!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I've been working on something that makes building with Claude Code way easier, and I wanted to share it with you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;THE PROBLEM&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I love using Claude Code for development, but I found myself repeating the same setup tasks over and over:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Creating new projects from scratch&lt;/li&gt;
&lt;li&gt;Setting up the same boilerplate&lt;/li&gt;
&lt;li&gt;Configuring TypeScript, Vue, and other tools manually&lt;/li&gt;
&lt;li&gt;Configuring AI rules&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It was getting tedious, and I thought: "There has to be a better way."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;THE SOLUTION&lt;/strong&gt;: Vibe Code Kit Plugin&lt;/p&gt;

&lt;p&gt;I built Vibe Code Kit - a plugin for Claude Code that gives you production-ready starter kits with just one command.&lt;/p&gt;

&lt;h2&gt;
  
  
  GETTING ACCESS
&lt;/h2&gt;

&lt;p&gt;First, get access to the private GitHub repository at:&lt;br&gt;
&lt;a href="https://vibecodekit.dev/?utm_source=devto" rel="noopener noreferrer"&gt;https://vibecodekit.dev/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Once you have access, installation is super simple:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/plugin marketplace add croffasia/vibecodekit-core
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  HOW TO START A NEW PROJECT
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Run the command:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/vck:init:starter:vue-spa
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;Start building! Just tell Claude what you want:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;"Add a user authentication page"&lt;br&gt;
"Create a dashboard with charts"&lt;br&gt;
"Build a blog post editor"&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Or use planning mode for complex features:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/plan Feature: "Add payment integration with Stripe"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's it! Claude will build your project while you focus on the business logic.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WHAT YOU GET OUT OF THE BOX&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Production-ready configuration (ESLint, Stylelint, TYpescript, Prettier, Husky Git hooks)&lt;/li&gt;
&lt;li&gt;Vue3 with modular architecture&lt;/li&gt;
&lt;li&gt;Docker container ready to deploy&lt;/li&gt;
&lt;li&gt;Multi-agent workflows for planning and execution&lt;/li&gt;
&lt;li&gt;Built-in AI rules for your entire tech stack&lt;/li&gt;
&lt;li&gt;Zero setup time - just start coding&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;THE SECRET SAUCE:&lt;/strong&gt; AI RULES&lt;/p&gt;

&lt;p&gt;Here's what makes Vibe Code Kit different: it comes with pre-configured AI rules for your entire tech stack. These rules teach Claude:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What it SHOULD do (best practices, patterns, conventions)&lt;/li&gt;
&lt;li&gt;What it SHOULD NOT do (anti-patterns, common mistakes)&lt;/li&gt;
&lt;li&gt;How to write maintainable, high-quality code&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The result?&lt;/strong&gt; You get clean, production-ready code that's actually maintainable, not just "it works on my machine" code.&lt;/p&gt;

&lt;h2&gt;
  
  
  MULTI-AGENT WORKFLOWS
&lt;/h2&gt;

&lt;p&gt;Vibe Code Kit includes multi-agent workflows that break down complex tasks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Planning agent: Breaks down your feature into steps&lt;/li&gt;
&lt;li&gt;Execution agent: Implements the plan&lt;/li&gt;
&lt;li&gt;Review agent: Ensures quality&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's like having a senior dev pair-programming with you.&lt;/p&gt;

&lt;p&gt;From idea to deployed app in minutes, not hours.&lt;/p&gt;

&lt;h2&gt;
  
  
  WHAT'S NEXT?
&lt;/h2&gt;

&lt;p&gt;I'm planning to add more starter kits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React + TypeScript&lt;/li&gt;
&lt;li&gt;Node.js API templates&lt;/li&gt;
&lt;li&gt;Full-stack setups&lt;/li&gt;
&lt;li&gt;And more based on what people need&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  WHY I'M SHARING THIS
&lt;/h2&gt;

&lt;p&gt;I believe the best tools come from solving your own problems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Want to try it?&lt;/strong&gt; Get access at &lt;a href="https://vibecodekit.dev/?utm_source=devto" rel="noopener noreferrer"&gt;https://vibecodekit.dev/&lt;/a&gt; and let me know what you think!&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>vibecoding</category>
      <category>webdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>Stop AI from Writing Random Code That Doesn't Fit Your Codebase 🤖</title>
      <dc:creator>Andrii Poluosmak</dc:creator>
      <pubDate>Tue, 19 Aug 2025 19:35:17 +0000</pubDate>
      <link>https://dev.to/croffasia/stop-ai-from-writing-random-code-that-doesnt-fit-your-codebase-4hmf</link>
      <guid>https://dev.to/croffasia/stop-ai-from-writing-random-code-that-doesnt-fit-your-codebase-4hmf</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Honest question: Do you also give AI minimal info and expect magic? 🪄&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;I've been coding for 20+ years, and here's what I've learned about AI-generated code: it works great... until it doesn't.&lt;/p&gt;

&lt;p&gt;Sure, AI can pump out working features in minutes. The tests pass, stakeholders are happy, you ship to production. Everyone's celebrating the "10x developer" moment.&lt;/p&gt;

&lt;p&gt;Then three months later, you need to modify that feature. Or fix a bug. Or add a new requirement.&lt;/p&gt;

&lt;p&gt;That's when the real pain starts.&lt;/p&gt;

&lt;p&gt;Nobody on your team understands how the AI code actually works. The logic is scattered across files with no clear pattern. There are mysterious functions that seem important but have zero documentation. The architecture doesn't match anything else in your codebase.&lt;/p&gt;

&lt;p&gt;What seemed like a productivity win becomes technical debt that haunts your team for months.&lt;/p&gt;

&lt;p&gt;The worst part? This is happening everywhere. Teams are shipping AI code fast, then drowning in maintenance hell later. But everyone's so focused on "ship faster with AI" that nobody talks about what happens next.&lt;/p&gt;

&lt;p&gt;There has to be a better way to work with AI - one that doesn't create unmaintainable code bombs.&lt;/p&gt;




&lt;h2&gt;
  
  
  AI Code = Technical Debt?
&lt;/h2&gt;

&lt;p&gt;The root cause? &lt;strong&gt;We're treating AI like a search engine instead of a team member.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Think about it: when you onboard a new developer, you don't just say "add authentication" and walk away. You give them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your existing patterns to follow
&lt;/li&gt;
&lt;li&gt;Architecture documentation
&lt;/li&gt;
&lt;li&gt;Reference implementations to study
&lt;/li&gt;
&lt;li&gt;Testing standards and practices
&lt;/li&gt;
&lt;li&gt;Code review guidelines&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But with AI? We type "add user authentication" and somehow expect it to magically understand our 5-year-old codebase with its custom patterns, legacy decisions, and undocumented quirks.&lt;/p&gt;

&lt;p&gt;No wonder the resulting code becomes unmaintainable! AI writes in a vacuum, without understanding how its code fits into your larger system.&lt;/p&gt;

&lt;p&gt;The solution isn't to avoid AI - it's to give AI the same context you'd give a senior developer.&lt;/p&gt;




&lt;h2&gt;
  
  
  Enter the PRP Method
&lt;/h2&gt;

&lt;p&gt;After refactoring one too many AI-generated messes, I built something that changes the game completely.&lt;/p&gt;

&lt;p&gt;Instead of vague prompts, I created a system that gives Claude Code CLI &lt;strong&gt;everything&lt;/strong&gt; it needs to write code that actually fits your project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Here's how it works:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Phase 1: Smart Analysis&lt;/strong&gt; 🧠&lt;/p&gt;

&lt;p&gt;&lt;em&gt;When you describe a task, the system doesn't just jump to coding:&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Analyzes your request&lt;/strong&gt; for missing context&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Asks clarifying questions&lt;/strong&gt; if needed
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Studies your codebase&lt;/strong&gt; to understand patterns&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Researches external docs&lt;/strong&gt; when your codebase doesn't have examples&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Phase 2: Context Assembly&lt;/strong&gt; 📋&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The system builds a comprehensive spec that includes:&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your exact naming conventions&lt;/li&gt;
&lt;li&gt;Reference implementations to mirror&lt;/li&gt;
&lt;li&gt;Integration points with existing code
&lt;/li&gt;
&lt;li&gt;Your testing patterns and requirements&lt;/li&gt;
&lt;li&gt;Validation commands specific to your project&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Phase 3: Claude Code Magic&lt;/strong&gt; ✨&lt;/p&gt;

&lt;p&gt;&lt;em&gt;With the complete context, Claude Code CLI now knows:&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How you structure components&lt;/li&gt;
&lt;li&gt;What libraries you prefer&lt;/li&gt;
&lt;li&gt;Your error handling patterns&lt;/li&gt;
&lt;li&gt;Your file organization&lt;/li&gt;
&lt;li&gt;Your commit message style&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  📊 Real Results That Actually Matter
&lt;/h2&gt;

&lt;p&gt;Here's what changed when I started using this approach:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before PRP:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;⏰ 15 minutes from idea to implementation&lt;/li&gt;
&lt;li&gt;😤 Another 1-2 hours refactoring and bug fixing&lt;/li&gt;
&lt;li&gt;🔄 Constant context switching between AI and manual fixes&lt;/li&gt;
&lt;li&gt;🐛 Code reviews always caught style issues&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;After PRP with Claude Code:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;⚡ 15 minutes from idea to implementation&lt;/li&gt;
&lt;li&gt;✅ Code matches patterns immediately&lt;/li&gt;
&lt;li&gt;🎯 One-pass development with built-in validation&lt;/li&gt;
&lt;li&gt;🚀 Code reviews focus on logic, not style&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The difference is &lt;strong&gt;dramatic&lt;/strong&gt;. One developer put it perfectly:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"3 prompts and 15 minutes, ready for feedback on something I would have agonized over for 2 hours."&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  🔧 The Technical Magic Behind It
&lt;/h2&gt;

&lt;p&gt;The PRP Generator uses a three-agent approach with Claude Opus:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Surface Discovery Agent&lt;/strong&gt; → Validates task completeness and identifies missing business logic  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Codebase Research Agent&lt;/strong&gt; → Deep pattern discovery and internal architecture analysis  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;External Research Agent&lt;/strong&gt; → Comprehensive external documentation and best practices research  &lt;/p&gt;

&lt;p&gt;This runs on Claude Opus for intelligent planning, then hands detailed specifications to Claude Code CLI for flawless implementation.&lt;/p&gt;




&lt;h2&gt;
  
  
  Getting Started (It's Easier Than You Think)
&lt;/h2&gt;

&lt;p&gt;I open-sourced the PRP Generator because this approach could change how we all work with AI.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Clone the repository&lt;/span&gt;
git clone https://github.com/croffasia/claude-code-prp-generator
&lt;span class="nb"&gt;cd &lt;/span&gt;claude-code-prp-generator

&lt;span class="c"&gt;# Copy commands to your Claude Code setup&lt;/span&gt;
&lt;span class="nb"&gt;cp&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt; claude/commands ~/.claude/commands/

&lt;span class="c"&gt;# Copy agents to your Claude Code setup&lt;/span&gt;
&lt;span class="nb"&gt;cp&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt; claude/agents ~/.claude/agents/

&lt;span class="c"&gt;# Copy templates to your project  &lt;/span&gt;
&lt;span class="nb"&gt;cp&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt; PRPs/ ./PRPs/

&lt;span class="c"&gt;# Generate a PRP&lt;/span&gt;
/generate-prp Add user authentication with OAuth2

&lt;span class="c"&gt;# Execute with Claude Code&lt;/span&gt;
/execute-prp @PRPs/my-feature.md
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;⭐ &lt;strong&gt;Don't forget to star the repo if this helps you!&lt;/strong&gt; It really motivates me to keep improving the tool.&lt;/p&gt;

&lt;p&gt;The tool works with &lt;strong&gt;any&lt;/strong&gt; programming language by automatically discovering your project's patterns.&lt;/p&gt;




&lt;h2&gt;
  
  
  🎯 Why This Actually Matters
&lt;/h2&gt;

&lt;p&gt;This isn't just about faster coding. It's about solving the &lt;strong&gt;context gap&lt;/strong&gt; between human intent and AI execution.&lt;/p&gt;

&lt;p&gt;Teams that figure out how to give Claude Code proper context will have a massive advantage:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;🚀 Ship faster without sacrificing quality&lt;/li&gt;
&lt;li&gt;🎨 Maintain consistent architecture &lt;/li&gt;
&lt;li&gt;👥 Onboard AI like a proper team member&lt;/li&gt;
&lt;li&gt;🔧 Avoid technical debt from random AI code&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  🔮 The Future is Context-Rich AI
&lt;/h2&gt;

&lt;p&gt;I believe we're at an inflection point. Claude Code CLI and similar tools are incredibly powerful, but most of us are using them wrong.&lt;/p&gt;

&lt;p&gt;The PRP method is my contribution to that future - where AI doesn't just generate code, but generates code that &lt;strong&gt;belongs&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Try It Yourself 🚀
&lt;/h2&gt;

&lt;p&gt;Want to stop refactoring AI code? Check out the &lt;a href="https://github.com/croffasia/claude-code-prp-generator" rel="noopener noreferrer"&gt;PRP Generator on GitHub&lt;/a&gt; and let me know what you think!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Follow me for more insights on AI-assisted development and systematic approaches to coding with Claude Code CLI&lt;/strong&gt; 👋&lt;/p&gt;




&lt;p&gt;&lt;em&gt;What's your biggest AI coding frustration? Drop it in the comments - I read every single one! 💬&lt;/em&gt;&lt;/p&gt;

</description>
      <category>vibecoding</category>
      <category>claudecode</category>
      <category>opensource</category>
      <category>coding</category>
    </item>
  </channel>
</rss>
