| name | ai-coding-tools-stinger |
| description | AI coding tool advisor for Cursor, Claude Code, Aider, Cline, Windsurf, Devin, and Bolt. Use when picking, comparing, or configuring an AI coding tool, or debugging one that misbehaves. |
| license | MIT |
AI Coding Tools Stinger
When to use this skill
Covers the vibe-coder's AI coding tool landscape: Cursor, Claude Code, Aider, Cline, Windsurf/Cascade, Continue.dev, Replit Agent, Devin, and Bolt. Covers tool-tier classification, the selection rubric (autonomy, context, budget, language), SWE-bench benchmark data, model-routing patterns (including Aider's 3-5x cost-reducing architect/editor split), per-tool prompt and context discipline, and a documented footgun catalog.
Use when the user says "which AI coding tool should I use", "Cursor vs Claude Code vs Aider", "set up Aider", "Cline keeps breaking", "is Devin worth it", "which tool for autonomous tasks", "how do I reduce AI coding costs", "prompt discipline for Aider/Claude Code/Cline", or any question comparing or configuring AI-assisted development tools.
Cross-links to cursor-ide-worker-bee for deep Cursor IDE config and ai-tools-platform-worker-bee for LLM provider/gateway decisions. Do NOT use for Cursor IDE configuration (cursor-ide-worker-bee owns that), CI/CD pipelines that run agents (devops-worker-bee), or LLM provider gateway architecture beyond tool-specific routing (ai-tools-platform-worker-bee).
Purpose
This Stinger equips ai-coding-tools-worker-bee to recommend, compare, configure, and debug AI coding tools across the 2026 ecosystem. Every factual claim in this skill traces to a file in research/: see research/index.md for the full source manifest.
The Stinger is organized around the six guides that mirror the Bee's ACTION list. Read the guide that matches the user's question. All guides reference each other and cite their research sources.
