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
loulanyue/awesome-claude-notes
Agent
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
loulanyue/awesome-claude-notes
Agent
When the user asks how to use a library, framework, or API or needs up-to-date code examples, use Context7 MCP to fetch current documentation and return answers with examples. Invoke for docs/API/setup questions.
loulanyue/awesome-claude-notes
Agent
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
Agent
Match the right skills, tools, and capability packages for a MetaKim agent or workflow.
Agent
Discover external tools and skills to close MetaKim capability gaps.
Agent
Design security boundaries, hooks, permissions, and rollback rules for MetaKim agents.
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase. This is a single-context repo.
Agent
Issues and PRDs for this repo live as tasks on the dev-3.0 Kanban board, managed through the dev3 CLI (the same board this project ships). There is no separate issue tracker — a task is an issue. External GitHub PRs are pulled in as a secondary triage surface (see below).
Agent
The skills speak in terms of five canonical triage roles. On this repo the tracker is the dev-3.0 Kanban board (see docs/agents/issue-tracker.md), so each role is a dev3 label applied to the task. dev3 statuses/columns (todo, in-progress, user-questions, review-by-ai, review-by-user) are managed by hooks and are NOT…
Agent
Implementation work that needs local judgment - feature work, bug fixes, design-sensitive refactors, integrations. The default executor for real development that is more than mechanical but doesn't need the frontier model. Give it the goal, the constraints, and the done-criteria; it owns the local design decisions…
Agent
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.
Agent
Security-sensitive implementation after approval - authentication and authorization, secrets handling, cryptography usage, input validation, hardening, dependency remediation. Give it only an approved, stable contract to execute; all pre-approval analysis belongs to the security-review role instead.
Agent
Use when a phase has ambiguities, gray areas, or unresolved decisions that need adaptive interrogation before SPEC can lock. Dispatched by ijfw-spec-phase, but can be called directly when the user says 'discuss this phase', 'what's unclear', 'interrogate the ambiguities', 'help me decide', '/ijfw-discuss-phase'.…
Agent
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
Agent
Use when auditing implemented frontend code or visual artifacts against UI-SPEC.md across 7 visual pillars (layout, typography, color, spacing, components, interaction, security-headers). Produces UI-REVIEW.md with per-pillar PASS / FLAG / BLOCK verdicts and evidence.
Agent
Senior Backend Engineer specialized in Go for high-demand financial systems. Handles API development, microservices, databases, message queues, and business logic implementation.
Agent
Reviews correct usage of Lerian lib-commons non-observability packages (lifecycle, tenancy, http, idempotency, security, database, messaging, outbox-repo side), identifies reinvented-wheel opportunities, and enforces version consistency. Runs in parallel with other reviewers.
Agent
Dead Code Review: identifies code that became orphaned, unreachable, or unnecessary as a consequence of changes. Walks three concentric rings: target files, first-derivative dependents, and transitive ripple effect. Runs in parallel with other reviewers at Gate 8.
Agent
Read-only investigation engine: codebase exploration, auditing, research, and runtime evidence gathering for a failure. Cannot modify files. Use before planning, to answer a question that requires grounding findings in evidence (file:line, config value, schema fact), or to reproduce a failure and capture its runtime…
Agent
Implements all files listed in an approved plan. Writes production code, configuration, and updates test implementations. Use after test skeleton approval.
Agent
Reviews an implementation diff in two passes (spec-compliance first, then code quality). Read-only. Returns structured findings. Replaces the separate spec/code-quality reviewers.
digipulse-engineering/GAAI-framework
Agent
Each agent has a curated set of skills defined in its agent definition file.
digipulse-engineering/GAAI-framework
Agent
Mission: Initialize and converge a governed, structured project context for GAAI.
digipulse-engineering/GAAI-framework
Agent
The Discovery Agent is responsible for deciding what should be built — and why.