Use when the reviewer subagent is reviewing a diff that implements work defined by a capability spec or an approved plan (protocol Phase 3). Checks two things: does the diff do what the spec requires, and does the diff do what the approved plan said it would. Catches silent drift between intent and implementation.…
Use when the reviewer subagent is reviewing a diff for correctness/logic, simplicity/reuse, test quality, or type design — the default reviewer dimension for the implement-feature and implement-backlog loops. Domain-rule, audit-trail, and spec-conformance concerns are NOT here — route those to…
Reviews implementation plans before any code is written. Use when the reviewer subagent is judging whether a plan's approach/architecture is sound — approving it or sending it back with approach-level concerns. Used by implement-backlog (Phase 2, as the gate that replaces the human) and available to implement-feature…
This skill should be used when the user asks to "design a system", "architecture", "ADR", "system design", "tech stack", "choose between approaches", "coupling", "service granularity", "blueprint", "component design", "API contract", "schema design", "trade-offs", or discusses "monolith", "microservices", "fitness…
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
Deep structural codebase comprehension, AST dependency graph traversal, symbol caller/callee tracing, and monorepo navigation strategies for massive codebases.
Generate a human-readable explanation of implemented changes after coding. Use after implementing a specification to document what changed, why, which trade-offs were accepted, and which vulnerabilities were found and fixed. The audience includes developers, reviewers, managers, and stakeholders.
Generate and maintain a repository-specific AGENTS.md file through a conversational interview. Use when setting up project guidelines for coding agents, updating engineering conventions, or configuring team-wide agent behaviour. The generated file reflects the actual architecture, constraints, and conventions of the…
Transform ideas, tickets, and feature requests into implementation-ready specifications with test cases, methodology, and validation strategy. Use when starting a new feature, clarifying requirements, designing test cases, or documenting architectural decisions before implementation.
Lead complex engineering work as the accountable chief engineer. Keep architecture, risk, contracts, task topology, and final acceptance with Sol; route bounded execution to model-pinned workers; preserve decisions across fresh phases; and integrate only verified results. Use for multi-workstream engineering, model…
Manage a large-scale software engineering project as a versioned, ordered, dependency-aware task plan, executed one sprint at a time through a backlog -> inprogress -> done state machine, with an auditable trail and PLAN.md as the single source of truth. Generalizes the clean-room scope -> plan -> implement pipeline…
Perform a deep test of the codebase, validating functional smoke tests, claim verification, drift checks, license headers, and placeholder checks. Trigger whenever the user asks to run deep tests, check code health, or perform strict verification.
Kit-maintainer diagnostic (LOCAL-ONLY, not distributed) that audits the README and docs/ for staleness against the repo's real command/skill/CLI roster, stamped tree, and cross-doc consistency. Read-only; produces a severity-ranked findings report.
Diagnostic gate that checks CLAUDE.md and AGENTS.md for completeness, consistency, and stale artifacts — run right after /cold-start and before /add-feature. Read-only; produces a findings report.
Tool-agnostic behavioral guidelines for AI coding assistants. Use when writing, reviewing, debugging, or refactoring code to reduce overengineering, surface ambiguity, make surgical changes, and define verifiable success criteria.
Produce a structured OpenACCP formal report for human owners and downstream agents. Use when reporting project, lane, bootstrap, handoff consume, review, validation, or release-readiness status with progress, gaps, authority limits, and next actions.
Run a bounded OpenACCP Frontier lane. Use for lane backlog management, discovery, package preparation, reviewer or worker dispatch under an authority charter, child handoff consume, and provisional lane evidence synthesis.
Run delegated-final-authority OpenACCP coordination. Use for coordination decisions, authority charters, dispatch, final handoff consume, PR/CI/merge readiness, publication readiness, owner-ready waiver recommendations, and accepting or rejecting reviewed evidence when delegated by charter.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
SDK development, external developer communication, code samples, API client libraries, community engagement, and developer experience. Use when creating SDKs, writing external guides, creating code samples, or improving developer experience.
Review user-facing software changes for accessibility barriers across semantics, keyboard and other input, focus, structure, content, feedback, and assistive technology behavior. Use for web, mobile, desktop, CLI, and interactive UI changes; adapt the checks to the platform.
Design and interpret evaluations of AI coding-agent behavior across realistic tasks, correctness, safety, usefulness, and maintainability. Use when creating benchmarks, comparing agents or skills, measuring regressions, or making claims about agent capability.
Design, change, or review APIs and serialized interfaces while making compatibility, versioning, errors, and migration behavior explicit. Use for HTTP, RPC, CLI, event, library, configuration, and file-format interfaces used by other code or people.
2 4d agoA55 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: