<?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: claude-dev-suite</title>
    <description>The latest articles on DEV Community by claude-dev-suite (@claudedevsuite).</description>
    <link>https://dev.to/claudedevsuite</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%2F3859592%2Fbfd6de71-9b29-4f8a-8f1d-e9fcbe68711b.jpeg</url>
      <title>DEV Community: claude-dev-suite</title>
      <link>https://dev.to/claudedevsuite</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/claudedevsuite"/>
    <language>en</language>
    <item>
      <title>I built a toolkit that turns Claude Code into a full AI dev suite</title>
      <dc:creator>claude-dev-suite</dc:creator>
      <pubDate>Fri, 03 Apr 2026 14:18:21 +0000</pubDate>
      <link>https://dev.to/claudedevsuite/i-built-a-toolkit-that-turns-claude-code-into-a-full-ai-dev-suite-4k7m</link>
      <guid>https://dev.to/claudedevsuite/i-built-a-toolkit-that-turns-claude-code-into-a-full-ai-dev-suite-4k7m</guid>
      <description>&lt;p&gt;Claude Code is one of the most capable AI coding assistants available. But out of&lt;br&gt;
the box it starts every project knowing nothing about your stack. No framework&lt;br&gt;
context, no domain-specific tools, no way to configure what it can and can't do.&lt;/p&gt;

&lt;p&gt;I wanted something different: an assistant that already knows React 19, or Spring&lt;br&gt;
Boot with Flyway and MapStruct, or Rust with Axum — without me re-explaining it&lt;br&gt;
every session. So I built Dev-Suite.&lt;/p&gt;
&lt;h2&gt;
  
  
  What Dev-Suite is
&lt;/h2&gt;

&lt;p&gt;Dev-Suite is an open-source toolkit that extends Claude Code with three things:&lt;br&gt;
specialized agents, MCP servers, and a configuration dashboard.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/claude-dev-suite/claude-dev-suite" rel="noopener noreferrer"&gt;https://github.com/claude-dev-suite/claude-dev-suite&lt;/a&gt;&lt;br&gt;&lt;br&gt;
&lt;strong&gt;License:&lt;/strong&gt; MIT&lt;/p&gt;


&lt;h2&gt;
  
  
  The problem with "vanilla" Claude Code
&lt;/h2&gt;

&lt;p&gt;When you open a new project with Claude Code, it's a blank slate. You have to&lt;br&gt;
tell it your stack, your conventions, what tools are available, what patterns&lt;br&gt;
to follow. For a one-off task that's fine. For daily development work it gets&lt;br&gt;
old fast.&lt;/p&gt;

&lt;p&gt;What I wanted was something like specialized colleagues you can call in:&lt;br&gt;
&lt;em&gt;"@react-expert add a form with validation"&lt;/em&gt; — and it already knows you're using&lt;br&gt;
React Hook Form, Zod, and shadcn/ui. No briefing required.&lt;/p&gt;


&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;
&lt;h3&gt;
  
  
  1. Specialized agents (~43)
&lt;/h3&gt;

&lt;p&gt;Each agent is a sub-agent with deep context for a specific domain. You invoke&lt;br&gt;
them with &lt;code&gt;@agent-name&lt;/code&gt; in Claude Code, or through the orchestrator GUI.&lt;/p&gt;

&lt;p&gt;Some examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;react-expert&lt;/strong&gt; — React 19, hooks, Zustand, TanStack Query, Tailwind, shadcn/ui&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;spring-boot-expert&lt;/strong&gt; — JPA, Flyway, MapStruct, Spring Security, Lombok&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;security-expert&lt;/strong&gt; — OWASP checks, dependency scanning, secrets detection&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;playwright-expert&lt;/strong&gt; — E2E tests, page object model, assertions&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;devops-expert&lt;/strong&gt; — CI/CD pipelines, Docker, Kubernetes, GitHub Actions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;They don't bleed into each other — each one loads only its relevant context when&lt;br&gt;
invoked, keeping the main context window clean.&lt;/p&gt;
&lt;h3&gt;
  
  
  2. MCP servers (10)
&lt;/h3&gt;

&lt;p&gt;MCP (Model Context Protocol) is the standard Anthropic introduced to give AI&lt;br&gt;
assistants access to real tools. Dev-Suite ships 10 pre-built MCP servers:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Server&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;documentation&lt;/td&gt;
&lt;td&gt;Fetches framework docs on-demand from a Git-based KB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;api-tester&lt;/td&gt;
&lt;td&gt;Tests REST endpoints, validates responses&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;database-query&lt;/td&gt;
&lt;td&gt;Runs queries against PostgreSQL, MySQL, SQLite&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;docker-manager&lt;/td&gt;
&lt;td&gt;Lists containers, reads logs, manages images&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;log-analyzer&lt;/td&gt;
&lt;td&gt;Tails and pattern-matches log files&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;performance-profiler&lt;/td&gt;
&lt;td&gt;CPU/memory profiling for Node.js and Python&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;code-quality&lt;/td&gt;
&lt;td&gt;Complexity analysis, duplication detection&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;security-scanner&lt;/td&gt;
&lt;td&gt;Dependency audit, secret detection&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;git-tools&lt;/td&gt;
&lt;td&gt;Branch management, diff analysis, commit history&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;file-manager&lt;/td&gt;
&lt;td&gt;Safe file operations with backup&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are proper MCP servers — they show up in Claude's tool list and are called&lt;br&gt;
natively, not through prompt hacks.&lt;/p&gt;
&lt;h3&gt;
  
  
  3. Skills (346+)
&lt;/h3&gt;

&lt;p&gt;Skills are structured knowledge files that agents load at invocation time. Think&lt;br&gt;
of them as quick-reference guides baked into the agent's context: patterns,&lt;br&gt;
gotchas, framework idioms, best practices.&lt;/p&gt;

&lt;p&gt;The documentation MCP server fetches them from a Git-based knowledge base with&lt;br&gt;
a 2-hour cache. They stay up to date without you pulling anything manually.&lt;/p&gt;
&lt;h3&gt;
  
  
  4. The dashboard
&lt;/h3&gt;

&lt;p&gt;The Electron dashboard is the configuration layer. When you point it at a project,&lt;br&gt;
it:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Detects your stack from &lt;code&gt;package.json&lt;/code&gt;, &lt;code&gt;pom.xml&lt;/code&gt;, &lt;code&gt;Cargo.toml&lt;/code&gt;, &lt;code&gt;requirements.txt&lt;/code&gt;, etc.&lt;/li&gt;
&lt;li&gt;Pre-selects the relevant agents and MCP servers&lt;/li&gt;
&lt;li&gt;Lets you review and customize the selection&lt;/li&gt;
&lt;li&gt;Generates &lt;code&gt;.mcp.json&lt;/code&gt; and &lt;code&gt;CLAUDE.md&lt;/code&gt; for that project&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;It also has an orchestrator tab where you can submit multi-agent jobs with&lt;br&gt;
real-time streaming output. The orchestrator pauses on sensitive operations and&lt;br&gt;
asks for approval — same permission model as Claude Code itself.&lt;/p&gt;


&lt;h2&gt;
  
  
  Architecture in brief
&lt;/h2&gt;

&lt;p&gt;Agents are markdown files with YAML frontmatter:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="nn"&gt;---&lt;/span&gt;
&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;react-expert&lt;/span&gt;
&lt;span class="na"&gt;model&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;sonnet&lt;/span&gt;
&lt;span class="na"&gt;skills&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;frontend-react&lt;/span&gt;
  &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;state-zustand&lt;/span&gt;
  &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;ui-shadcn&lt;/span&gt;
&lt;span class="na"&gt;mcp_servers&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;documentation&lt;/span&gt;
  &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;code-quality&lt;/span&gt;
&lt;span class="nn"&gt;---&lt;/span&gt;
&lt;span class="c1"&gt;# React Expert Agent&lt;/span&gt;
&lt;span class="nn"&gt;...&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;MCP servers are TypeScript npm packages under &lt;code&gt;mcp-servers/&lt;/code&gt;. The dashboard is&lt;br&gt;
React + Express + Electron. Everything runs locally — nothing goes to a third-party&lt;br&gt;
server.&lt;/p&gt;




&lt;h2&gt;
  
  
  Quick start
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/claude-dev-suite/claude-dev-suite.git
&lt;span class="nb"&gt;cd &lt;/span&gt;claude-dev-suite
./init-project.sh /path/to/your/project
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The script launches the dashboard, detects your stack, and walks you through&lt;br&gt;
the setup. On Windows there's &lt;code&gt;init-project.ps1&lt;/code&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;The project is MIT licensed and actively maintained. Current focus:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Expanding the agent roster (contributions welcome)&lt;/li&gt;
&lt;li&gt;Improving the orchestrator's multi-step job handling&lt;/li&gt;
&lt;li&gt;Adding more MCP servers (browser automation, cloud providers)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you use Claude Code and want something that knows your stack from day one,&lt;br&gt;
give it a try. Issues and PRs are open.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/claude-dev-suite/claude-dev-suite" rel="noopener noreferrer"&gt;https://github.com/claude-dev-suite/claude-dev-suite&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>claudecode</category>
      <category>mcp</category>
      <category>devtools</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
