Run a bounded adversarial sweep of an existing test suite. Use to harden a suite or subsystem against malformed inputs, boundaries, invalid state, races, dependency/resource failures, weak or redundant tests, flakes, and missing durable regressions. Skip ordinary test additions, load, chaos, and penetration testing.
Draft local Azure DevOps work item packets from loose context using the known project process, with Scrum PBI as the fallback when type and process are unknown. Inspect repo context when present. Do NOT use for live REST/CLI creation, migration, wiki, or status reporting.
Write, fix, or review Azure DevOps wiki Markdown, Mermaid, TOC, TOSP, details blocks, query tables, mentions, work-item links, KaTeX, videos, and code fences. Use for Azure DevOps surface quirks. Do NOT use for GitHub-only or non-Azure docs.
Draft, rewrite, review, humanise, or adapt prose without losing facts, voice, or uncertainty. Use for technical docs, wikis, product, editorial, marketing, personal, or AI-like writing. Skip code-only tasks.
Turn git commits and diffs into a non-technical client report grouped by feature. Use for client updates, weekly progress, stakeholder recaps, or high-level git-history summaries; resolve the date range from reliable context or ask when ambiguous.
Explains codebases and feature flows in accessible language with grounded analogies. Use for simple walkthroughs or mental models; skip bug triage, code review, and code changes.
Google-grounded SEO/GEO implementation for Search, AI Overviews, AI Mode, crawlability, indexability, snippets, structured data, ecommerce/local details, and agent browsing. Do NOT use for paid ads, rank tracking, non-Google directory tactics, or link schemes.
Convert repeated heuristics into deterministic behavior: validator scripts, normalizer tools, generators, fixtures, manifests, CI jobs, and hook-ready checks. Use to codify learnings and prevent future guessing. Do NOT use for pure brainstorming or one-off edits.
Selects sufficient, low-noise local shell commands for repository exploration, git inspection, tests, and container checks. Use when choosing command scope or output detail, especially for token savings or terse workflows; not for incidental tool mentions or requests for full output.
Design high-quality product apps, marketing sites, dashboards, and desktop UI. Use for art direction, critique, redesign, hierarchy, layout, typography, color, motion, or lightweight design systems. Do NOT use for logos, illustration-only work, image prompts, or backend-only tasks.
Audit a repo against Cloudflare/isitagentready signals for AI agent readiness: robots.txt, llms.txt, Markdown negotiation, MCP/API catalogs, OAuth discovery, WebMCP, and browser-agent usability. Includes explicitly scoped readiness audits; not generic SEO or standalone standards documentation questions.
Guide maintainable tests as behavior documentation with isolated side effects, compatibility coverage, and reliable assertions. Use for tests, fixtures, mocks, regressions, reviews, and testability changes. Skip disposable work.
Use markdown.new for Cloudflare Markdown for Agents, URL/file/PDF-to-Markdown, crawl-to-Markdown, the markdown.new API, or hosted editor workflows. Do NOT use for generic scraping/search or local Markdown editing that does not need markdown.new.
Create infographic prompts and render workflows with Nano Banana 2.1, with adaptable low-noise presets for posts, decks, reports, and explainers. Trigger on infographic, Nano Banana, Gemini image, executive visual, blog diagram, or presentation visual. Do NOT use for logos, memes, raw dashboards, or non-infographic…
Run ambitious one-shot websites, web apps, games, simulations, clones, motion pieces, or benchmarks through fresh isolated subagents. Use for one-shot web artifacts, catalogue ideas, or parallel model/harness variants.
Answer product, PM, stakeholder, or non-engineer questions about app behavior by inspecting code and returning a share-ready plain-English answer. Trigger on product question, PM question, stakeholder answer, how a feature works, or why the app behaves that way. Do NOT use for code changes.
Create or improve concise, useful, agent-safe repository READMEs. Use for new README drafts, rewrites, quickstarts, local setup, getting started, contributor docs, or README reviews. Do NOT use for API reference, full product docs, changelogs, or landing pages.
Uses ripgrep (rg) for local text and path search, including code symbols, literals, regexes, filename discovery, and machine-readable matches. Use when searching repository files or local logs; not for web search, full-file reads, or structured JSON queries better handled by jq.
★not rated 55
changed 23d agoA60 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: