2,166 tagged ai-coding, measured the same way as everything else here.
Browse within: agentic-coding 191claude-ai 125agent-orchestration 120code-quality 120copilot 117agentic-workflow 116claude-code-agents 93Code Generation 87ai-coding-assistant 80ai-coding-agent 64ai-skills 63claude-code-hooks 63agentic-engineering 60ai-agent-templates 60
GantisStorm/essentials-claude-code
Agent
Architectural Code Quality Agent (LSP-Powered) - Creates comprehensive architectural improvement plans suitable for loop or swarm executors (/implement-loop, /tasks-loop or /tasks-swarm, /beads-loop or /beads-swarm). Uses Claude Code's built-in LSP for semantic code understanding. This agent thoroughly analyzes code…
Agent
Implement a SPECIFIC, well-defined plan or plan-step with Codex. Use ONLY when the user has a written plan, plan-step, named files, or acceptance criteria to execute ("execute this via codex", "implement this plan", "/codex:execute", or a --plan file is in context). Do NOT use when the user is stuck/exploring (use…
Agent
Delegate a SPECIFIC, well-defined implementation task or plan step to Cursor in agent mode on the Auto model. Cursor is the fast lane for mechanical writing — long file writes (200+ lines), pattern-following across many files, bulk refactors. Supports autonomous multi-step runs via --until-done. Pair with…
Agent
Delegate read-only EXTERNAL web/documentation research to Cursor. Use when the user wants current library/API/docs research, "what's the current way to…", or to compare approaches — and you'd rather not spend Claude's context on web reading. Cursor runs read-only (ask mode) with web search + fetch and returns findings…
Agent Cursor
Designs and executes efficient cross-project and long-term memory so agents build apps better. Use when adding or improving memory that spans projects, sessions, or runs; when defining what to remember, how to scope it, and how to retrieve it for agent context.
Agent Cursor
GOAL: One document per domain. Minimum tokens for maximum clarity.
Agent Cursor
Evaluates app fidelity and completion against docs/SYSTEMARCHITECTURE.md and domain references. Serves as voice of customer: defines user workflows and outcomes, then validates implementation against them. Use proactively before releases, after major changes, or when validating feature completeness.
Agent Claude Code
Read-only Truthmark claim verifier for checking canonical truth against checkout evidence.
Agent Claude Code
Write-capable Truthmark doc worker for one parent-leased truth-document shard.
Agent Claude Code
Read-only Truthmark route auditor for bounded routing and ownership verification.
Agent
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Agent
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
Agent
Heavyweight reasoning agent. Runs at high effort on the caller's model. For revising plans, auditing specs/designs, reasoning through hard problems, and surfacing hidden assumptions or tradeoffs. Read-only. Does not implement, does not gate diffs, does not locate code. Use when the question is "is this the right…
claude-world/director-mode-lite
Agent
Decision-making agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase DECIDE — after the validator writes validation.json, when an iteration cycle completes, or at a manual decision point. Applies the SHIP/FIX/EVOLVE/ABORT threshold rule against verified evidence and writes reports/decision.json.…
claude-world/director-mode-lite
Agent
Learning agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase LEARN — after completion-judge decides EVOLVE, when iterations fail with similar issues, before the evolve phase, or on SHIP to record success patterns. Runs evidence-based root-cause analysis, extracts patterns, writes learning.json…
claude-world/director-mode-lite
Agent
Evolution agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase EVOLVE — after experience-extractor produces learning.json, when completion-judge decides EVOLVE, on an --evolve request, or on SHIP for lifecycle review. Applies verified learning to produce improved skill versions and manages…
Agent
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
Agent
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
Agent
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
Agent Claude Code
Proves a change on the maintainer's real local corpus — what number moved, by how much, and that nothing else did. Use before calling any measurement change done. Never writes to the real store.
Agent Claude Code
Reviews a change for the product-critical honesty rules — provenance, confidence, layer labels, scope denominators, error bars, and the refusals. Use on any change that adds, renames, or reshapes a number a user reads. Read-only.
Agent Claude Code
Drives a release end to end per RELEASING.md — green gate, public-surface audit, price-table refresh, changelog preparation, and the tag command to run. Stops before anything is pushed.
entropy-cloud/attractor-guided-engineering-template
Agent
You are the execution agent for a mission-driver step. mission-driver is an Attractor-Guided Engineering (AGE) loop engine that drives you through one step of a state machine: CHECK → REVIEWPLANS → EXECPLANS → DRAFTPLANS → DEEPAUDIT.
entropy-cloud/attractor-guided-engineering-template
Agent
You are the execution agent for a mission-driver step. mission-driver is an Attractor-Guided Engineering (AGE) loop engine that drives you through one step of a state machine: CHECK → REVIEWPLANS → EXECPLANS → DRAFTPLANS → DEEPAUDIT.