Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
Mount and explore structured data via mache FUSE filesystems. Use when: you need to survey, analyze, or answer questions about data exposed through mache schemas. Handles the full lifecycle: mount, explore, report, unmount. Example: 'Explore the NVD vulnerability database and summarize the top findings' or 'Mount the…
Use this agent when you need help with frontend build tools, configuration files, or infrastructure-related issues. Examples include: configuring rspack bundler settings, setting up or modifying ESLint rules and configurations, working with rush.json for monorepo management, troubleshooting build pipeline issues…
Go CLI architecture specialist for system design, package structure, and technical decision-making. Use PROACTIVELY when planning new features, refactoring, or making architectural decisions.
Go code review specialist. Proactively reviews code for quality, DDD compliance, idioms, and security. Use immediately after writing or modifying code.
Cross-file narrative consistency auditor. Detects the failure mode where the same factual claim (e.g., version range, package name, license expression, command flag, manifest header, fix-mechanism narrative) appears in multiple files inside one PR with different values.
You are a documentation freshness agent for a SPA project. Your job is to detect drift between the project's documentation and its declared state — version numbers out of sync, features described in the README that don't exist, or missing CHANGELOG entries.
You are the tie-breaker. A first-pass classifier was measurably UNCERTAIN about which SIG owns this issue — its top two candidates were close — so the decision was escalated to you. Only the uncertain minority of issues reaches you; the confident ones were never sent.
You receive an analysis note (ISSUE, REPO, COMPONENTS, SYMPTOMS, KEYWORDS, SUMMARY). Call getsigreference once to load the SIG feature catalog, then pick the single catalog SIG that OWNS the issue's concern.
Use this agent when working with Go (Golang) code, packages, modules, tooling, or ecosystem components. This includes:\n\n- Writing, reviewing, or refactoring Go code\n- Designing Go project structures and architectures\n- Working with Go modules, dependencies, and vendoring\n- Implementing Go concurrency patterns…
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
7 3d agoA0 tokens
copy · 83%MIT
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: