Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By c0x12c
Run 100+ specialized AI commands, skills, and agents via /spartan to scaffold Kotlin Micronaut backends and Next.js apps, provision Terraform AWS infra, automate PR reviews/gates/tests/QA, manage startup pipelines from idea validation to investor pitches, with safety locks, multi-agent coordination, and deep codebase analysis.
npx claudepluginhub c0x12c/ai-toolkit --plugin ai-toolkitSmart entry point for the Spartan AI Toolkit. Detects project context, routes to the right workflow or command. Use this when you're not sure where to start.
Structured brainstorming — generate ideas, filter fast, rank the top 3
Analyze an existing codebase and generate a structured context map + onboarding spec before making any changes. Use when joining a legacy project or unfamiliar service.
Build a new feature end-to-end — backend, frontend, or full-stack with auto-detection
Activate destructive operation warnings. Claude will detect and require explicit confirmation before running dangerous commands like rm -rf, DROP TABLE, force-push, git reset --hard, overwriting migrations, or deleting production resources.
UI/UX designer that uses external AI (Gemini) for design ideation and asset generation, then produces design docs and prototypes. Reads project design-config.md for brand context.
Design reviewer that catches AI-generic patterns, checks brand compliance, accessibility, and responsive behavior. Works with the designer in a discussion loop for the Design Gate. <example> Context: Designer just created a design doc for a new dashboard screen. user: "Review this design for the Design Gate" assistant: "I'll use the design-critic agent to evaluate the design for AI-generic patterns and brand compliance." </example> <example> Context: /spartan:ux prototype command needs a second opinion on the UI. user: "Run the design critic on this feature" assistant: "I'll spawn the design-critic to review the design doc and give a verdict." </example>
The harshest idea critic. Tries to kill your idea before the market does. Use when you need someone to find every flaw.
Use this agent when you need expert guidance on AWS infrastructure with Terraform, including VPC design, EKS/ECS clusters, RDS databases, ElastiCache, S3, IAM, and OIDC patterns. This agent excels at reviewing Terraform code, designing infrastructure modules, optimizing cloud architecture, and troubleshooting deployment issues. Examples: <example> Context: User needs help designing a service's infrastructure user: "I need to set up RDS and Redis for a new microservice" assistant: "I'll use the infrastructure-expert agent to design the database and cache infrastructure following Spartan conventions." <commentary> Since this involves AWS infrastructure design with Terraform, the infrastructure-expert agent should be used. </commentary> </example> <example> Context: User is debugging a Terraform state issue user: "Terraform plan shows resources being recreated unexpectedly" assistant: "Let me engage the infrastructure-expert agent to diagnose the state drift and recommend a fix." <commentary> State management issues require deep Terraform expertise from the infrastructure-expert agent. </commentary> </example> <example> Context: User needs help with EKS IRSA configuration user: "How should I set up IAM roles for my service pods?" assistant: "I'll use the infrastructure-expert agent to design the IRSA configuration following security best practices." <commentary> IRSA and IAM patterns require the infrastructure-expert agent's security expertise. </commentary> </example>
Use this agent when you need expert guidance on backend development with the Micronaut framework, database design decisions, API architecture, or when bridging backend and frontend concerns. This agent excels at reviewing Micronaut-specific code, optimizing database schemas, designing RESTful APIs, implementing microservices patterns, and providing full-stack architectural recommendations. Examples: <example> Context: User needs help with a Micronaut controller implementation user: "I need to create a new endpoint for user authentication" assistant: "I'll use the micronaut-backend-expert agent to help design and implement this authentication endpoint properly." <commentary> Since this involves Micronaut-specific backend work, the micronaut-backend-expert agent should be used. </commentary> </example> <example> Context: User is working on database optimization user: "Can you review my database schema for the user_profiles table?" assistant: "Let me engage the micronaut-backend-expert agent to analyze your database schema and suggest optimizations." <commentary> Database design review requires the specialized knowledge of the micronaut-backend-expert agent. </commentary> </example> <example> Context: User needs help with Micronaut dependency injection user: "How should I structure my service layer with Micronaut's DI?" assistant: "I'll use the micronaut-backend-expert agent to provide guidance on Micronaut's compile-time dependency injection patterns." <commentary> Micronaut-specific DI patterns require the framework expertise of the micronaut-backend-expert agent. </commentary> </example>
Creates RPC-style endpoint following layered architecture (Controller → Manager → Repository). Use when creating new API endpoints or CRUD operations.
Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.
Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.
Run a structured brainstorm session for startup ideas. Takes a theme or problem and generates ideas with quick gut-checks. Use when the user wants to explore a space or generate new ideas.
Run real browser QA with Playwright. Use when testing a frontend feature, verifying UI before PR, smoke testing after deploy, or investigating reported visual bugs.
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Full-stack agents — frontend, backend, API, DevOps architects
Autonomous multi-agent development framework with spec-driven sprints and convergent iteration
External tools integration skills for CLI utilities, APIs, and third-party services
Use Claude Code As Is - native plugin leveraging built-in architecture
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
Self-orchestrating multi-agent development system — 8 specialized AI agents, parallel quality gates, and automated workflows. You say WHAT, the AI decides HOW.
Uses bash pre-commands but Bash not in allowed tools
Uses bash pre-commands but Bash not in allowed tools
Share bugs, ideas, or general feedback.
Stop AI coding agents from shipping sloppy code.
Structured workflows · Configurable rules · Quality gates · Any stack
AI coding agents are fast. They're also careless. They skip tests, ignore your coding standards, push without review, and forget everything between sessions.
Spartan fixes that. One command runs a full engineering workflow — spec, plan, TDD, code review, PR — with quality gates between each step. Your rules, your standards, enforced every time.
npx @c0x12c/ai-toolkit@latest --local
Works with Claude Code, Codex, Cursor, Windsurf, and Copilot. Rules are plain markdown — works with any AI tool.
| Without Spartan | With Spartan |
|---|---|
| "Build this feature" → jumps straight to code, no plan, no tests, pushes broken code | /spartan:build → writes spec, plans tasks, TDD for each, code review, then PR |
| "Fix this bug" → guesses a fix, no repro, no test, hopes for the best | /spartan:debug → reproduces first, finds root cause, writes test, then fixes |
| 5 devs on the team → AI writes different code style for each person | Configurable rules → same standards for everyone, checked automatically |
| 3-week feature → AI forgets all context between sessions | /spartan:project → agent memory carries decisions across sessions |
| Code review catches AI slop → back-and-forth for days | Quality gates → review happens before PR, not after |
# 1. Install (30 seconds, interactive menu)
npx @c0x12c/ai-toolkit@latest --local
# 2. Set up rules for your stack
/spartan:init-rules
# 3. Build something
/spartan:build "add user authentication"
That's it. The /spartan:build command handles the full pipeline:
spec → design (if UI) → plan → TDD → code review → PR
| | | | | |
Gate 1 Design Gate Gate 2 Gate 3 Gate 3.5 Gate 4
Nothing ships without passing every gate.
| What | Count | Description |
|---|---|---|
| Slash commands | 73 | End-to-end workflows, not just prompts |
| Coding rules | 28 | Your standards, enforced automatically |
| Skills | 34 | Domain knowledge (Kotlin, React, Python, DB, security, etc.) |
| Agents | 10 | Specialized reviewers, researchers, planners |
| Stack profiles | 8 | Pre-built configs for Go, Python, Java, Kotlin, React, etc. |
| Quality gates | 5 | Automated checkpoints between every step |
| Agent memory | 3 layers | Index → topics → transcripts (grep-only archive) |
Each leader runs a full pipeline. One command — it handles the rest.
| Leader | Command | What happens |
|---|---|---|
| Build | /spartan:build "feature" | spec → design → plan → TDD → review → PR |
| Debug | /spartan:debug "symptom" | reproduce → root cause → test-first fix → PR |
| Startup | /spartan:startup "idea" | brainstorm → validate → research → pitch |
| Onboard | /spartan:onboard | scan codebase → map architecture → save to memory |
| Research | /spartan:research "topic" | frame question → gather sources → analyze → report |
Or just type /spartan — the smart router figures out what you need.
Pick a built-in profile or write your own rules in markdown: