Review dependency/runtime updates, vulnerability remediation or dependency-update PRs with release-note, compatibility and CI evidence. Use for explicit or configured maintenance jobs; auto-merge only under an established eligible-update policy.
Design UI interactions, backend contracts or architecture for a requested change before implementation. Use for flows, navigation, shared components, API/data/state behavior or consequential design alternatives; produce concise text and useful wireframes/mockups when needed.
Take a rough business idea, feature, refactor or improvement through clarification, design, implementation, testing and review in one requested engagement. Use for end-to-end development with consequential questions and explicit assumptions, not a promise of zero interaction or automatic deployment.
Organize application knowledge and update affected PRDs, architecture, schemas, plans, decisions and runbooks when implementation or accepted decisions change. Use during planning, feature changes, migrations, deployment changes or documentation reviews.
Develop a feature in an isolated Git worktree, make Conventional Commits and publish a concise pull request to the correct repository. Apply by default when starting feature work, continuing a feature branch, committing changes or preparing a PR; respect plan-only requests and existing contribution conventions.
Assess and address security/privacy weaknesses in the supplied feature, diff or repository. Use for a scoped hardening task with evidence-backed fixes and verification, preserving accepted architecture and task authority.
Assess codebase improvement opportunities or implement a specified improvement objective. Use for architecture, performance, reliability, testability, UX consistency or developer-experience work; bare invocation discovers prioritized evidence-backed opportunities.
Define, automate, explore and evaluate user journeys across web, desktop and mobile applications. Use for UI/API/persistence changes, interaction and visual consistency, authentication, authorization, lifecycle behavior and failing journey checks.
Design, implement, run or review k6 load and performance checks for application journeys locally, against an application started on a CI runner, or against a deployed non-production environment. Use for latency, concurrency, throughput, saturation and performance regressions; preserve target authority and existing…
Plan implementation of agreed work using repository context, dependencies, verification and release consequences. Use for a bounded feature/refactor plan; do not turn a small fix into a mandatory planning workflow.
Refine a rough idea, brief, conversation or optional tracker item into repository-aware actionable work. Use to establish scope, acceptance criteria, affected UX/API/data boundaries and material questions before implementation, including unattended refinement jobs.
Prepare or execute a named application release/deployment with artifact, configuration, compatibility and recovery verification. Use for deployment readiness or an explicitly authorized target action; bare invocation prepares and reports rather than deploying.
Design, implement, run or review controlled failure tests for application journeys, dependency outages, delays, worker loss and resource exhaustion. Use to verify bounded failure handling and recovery in an authorized isolated or non-production target; choose proportionate fixtures or experiments without requiring a…
Review a PR, branch or current diff against its intended behavior and engineering standards, checking appropriate test evidence. Use for explicit reviews or configured PR-review jobs; default to assessment rather than source changes, publication or merge.
Design, implement or review features with security and privacy built into data flows, authorization and integrations. Apply to changes involving identities, user data, external inputs, dependencies or new trust boundaries; revisit protections as the application evolves.
Establish a new application or adopt an existing repository, discover working commands and accepted constraints, and prepare a useful first slice. Use for explicit project setup or adoption; preserve an existing project layout and tooling.
Discover and document an application's services, dependencies, deployment topology and user/request/data journeys from repository, documentation and runtime evidence for setup, feature analysis or recurring architecture updates.
Explain this plugin toolkit, available task entry points and supporting skills by SDLC phase or requested outcome. Use for help, command discovery, invocation syntax, automation examples and choosing a next development activity without starting it.
Create or refine responsive, theme-aware HTML architecture diagrams for structural, runtime, data and deployment explanations. Use when a portable HTML diagram is requested or chosen; preserve existing notation and accepted visual direction.
Build an explorable, standalone HTML architecture and message-flow explorer from repository evidence or a proposed design. Use when users want to explore a service or repository's architecture, capabilities, dataflow, request lifecycle, sequence messages, or C4 context/container/component views; also use for…
Define and verify frontend user journeys, navigation, menus, dialogs, forms and shared interaction patterns before meaningful UI implementation. Use for new UX, cross-screen redesigns, global component changes or inconsistent behavior; inventory all affected surfaces and states instead of improvising each page.
Explain and maintain a software system's architecture through structural views, runtime and lifecycle scenarios, interface analysis, deployment boundaries and evidence. Use for architecture documentation, system breakdowns and technical architecture reviews; preserve current versus target design and existing project…
Write and review clear, accurate, useful product and engineering documentation, including PRDs, requirements, architecture, decisions, feature specifications and operational guides. Use for new documents and substantive documentation revisions, adapting explanations, examples and presentation to readers.
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: