484 boosters for "dev" — open source, verified from GitHub, ready to install
Claude Code Workflow is a JSON-driven multi-agent development framework that orchestrates AI-powered CLI workflows across multiple LLM providers (Gemini, Qwen, Codex) for automated code development tasks. It benefits developers and teams seeking to automate complex development workflows with intelligent context management and multi-agent coordination.
This command enforces test-driven development methodology for GROWI. 1. ALL phases of TDD MUST be followed: RED → GREEN → REFACTOR 2. Tests MUST be written BEFORE any implementation code (RED phase)
Heuristic scoring (no AI key configured).
A hands-on course teaching developers how to build AI-powered agents using Foundry Local with modern SDK patterns, function calling, and hybrid cloud designs. Benefits beginners and intermediate developers wanting to prototype agentic applications quickly on edge devices.
"name": "edmunds-claude-code", "description": "Edmund's personal Claude Code setup with 14 productivity commands and 11 specialized AI agents for modern web development", "path": ".claude/commands/new-task.md",
Retrieve current documentation and code examples for any library using the Context7 CLI. Make sure the CLI is up to date before running commands: Or run directly without installing:
"email": "zbeyens@udecode.dev" "description": "Claude Code plugins for AI-powered development workflows", "source": "./.claude-plugin/plugins/dotai",
This module focuses on learning the language transition from JavaScript to Python, helping developers quickly master Python programming through comparative teaching. console.log("Hello World"); print("Hello World")
Tangle is a skill-based booster that guides multi-AI implementation for the development phase using Double Diamond methodology, with built-in quality gates for code validation and security checks. It benefits developers building features, prototypes, and complex systems who want structured, multi-perspective implementation approaches.
A structured debugging methodology that guides developers through systematic root-cause analysis before implementing fixes, compatible with Claude Code and Cursor. Developers benefit by reducing debugging time and avoiding hasty code changes.
  Awesome Claude Code plugins — a curated list of slash commands, subagents, MCP servers, and hooks for Claude Code
Extract non-obvious discoveries into reusable skills that persist across sessions. Invoke when you encounter: Before creating a skill, answer these questions:
You are a senior maintainer-level reviewer for NNStreamer (GStreamer plugins + related libs). Prefer small, reviewable diffs; do not refactor unrelated code. ===============================================================================
You are helping a developer implement a new feature. Follow a systematic approach: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, then implement. Initial request: $ARGUMENTS 1. Create todo list with all phases
You are a trading strategy hypothesis ideation engine. Produce 1-5 falsifiable hypothesis cards from structured evidence.
"name": "iothackbot", "description": "IoT security testing toolkit with skills for firmware analysis, network reconnaissance, UEFI security, and device exploitation", "name": "BrownFineSecurity"
You are a CLI development specialist focused on building excellent command-line tools. You understand terminal conventions, argument parsing, and creating tools that feel native to the shell environment. 1. Define interface - Commands, flags, arguments 2. Implement core logic - Business functionalit
"name": "dotnet-skills", "description": "Comprehensive .NET development skills and agents for Claude Code - covering C#, F#, Akka.NET, Aspire, testing frameworks, and specialized tools", "name": "Aaron Stannard",
"name": "spec-driven-develop", "name": "zhu1090093659" "description": "Automates pre-development workflow for large-scale complex tasks"
<div align="center">  
Use this agent when documentation in the `architecture/` directory needs to be updated or created for a specific file after implementing a feature, fix, refactor, or behavior change. Launch one instance of this agent per file that needs updating. This agent maintains the *contents* of architecture documentation files — it does not decide which files exist or how the directory is organized.\n\nExamples:\n\n- Example 1:\n Context: A developer just finished implementing OPA policy evaluation in the sandbox system.\n user: "I just finished implementing the OPA engine in crates/openshell-sandbox/src/opa.rs. Update architecture/sandbox.md to reflect the new policy evaluation flow."\n assistant: "I'll launch the arch-doc-writer agent to update the sandbox architecture documentation with the new OPA policy evaluation details."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/sandbox.md>\n\n- Example 2:\n Context: A refactor changed how the HTTP CONNECT proxy handles allowlists.\n user: "The proxy allowlist logic was refactored. Please update architecture/proxy.md."\n assistant: "Let me use the arch-doc-writer agent to synchronize the proxy documentation with the refactored allowlist logic."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/proxy.md>\n\n- Example 3:\n Context: After implementing a new CLI command, the assistant proactively updates docs.\n user: "Add a --rego-policy flag to the CLI."\n assistant: "Here is the implementation of the --rego-policy flag."\n <implementation complete>\n assistant: "Now let me launch the arch-doc-writer agent to update the CLI architecture documentation with the new flag."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/cli.md>\n\n- Example 4:\n Context: A user wants high-level overview documentation for a non-engineering audience.\n user: "Update architecture/overview.md with a non-engineer-friendly explanation of the sandbox system."\n assistant: "I'll launch the arch-doc-writer agent to create an accessible overview of the sandbox system for non-technical readers."\n <uses Task tool to launch arch-doc-writer with audience=non-engineer directive>\n\n- Example 5:\n Context: Multiple files need updating after a large feature lands.\n user: "I just landed the network namespace isolation feature. Update architecture/sandbox.md and architecture/networking.md."\n assistant: "I'll launch two arch-doc-writer agents — one for each file — to update the documentation in parallel."\n <uses Task tool to launch arch-doc-writer for architecture/sandbox.md>\n <uses Task tool to launch arch-doc-writer for architecture/networking.md>
Use this agent to review existing code, audit plans, evaluate product requirements, or get architectural guidance that balances pragmatism, user experience, and security. This includes code reviews, plan audits, architecture reviews, security assessments, or when building engineering and development plans from requirements. Use proactively after significant code changes or before merging.
"name": "antigravity-skills", "description": "Professional Agent Skills collection for full-stack development, logic planning, and multimedia processing.", "email": "guanyangsunlight@gmail.com",
