io.github.shinpr/ai-coding-project-boilerplate/typescript-testing

Applies Vitest test design and quality standards. Provides coverage requirements and mock usage guides. Use when writing unit tests.

io.github.openclaw/openclaw/browser-automation

Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

io.github.questdb/questdb/review-pr

Review a GitHub pull request against QuestDB coding standards. Use when asked to review a PR, given a PR number or URL, optionally with a review level 0..3. Performs an adversarial, blocking, mission-critical code review.

io.github.Klotzkette/claude-fuer-deutsches-recht/writing-unterlagen-luecken

Unterlagen und Lücken: sortiert Dokumente, erkennt Lücken, ordnet Beweiswert und formuliert gezielte Rückfragen.

io.github.Klotzkette/claude-fuer-deutsches-recht/writing-einstieg-routing

Einstieg und Routing: klärt Rolle, Ziel, Frist, Aktenlage und den passenden nächsten Fachpfad.

io.github.codeaholicguy/ai-devkit/security-review

AI DevKit · Review code, skills, and prompts for security vulnerabilities — OWASP Top 10, prompt injection, business logic flaws, and insecure defaults. Use when reviewing PRs, auditing modules, reviewing AI skills/prompts, or preparing for release.

io.github.browser-use/browser-harness/browser-harness

Direct browser control via CDP — automate, scrape, test, or interact with web pages by driving the user's already-running Chrome (or a Browser Use cloud browser). Use when the user wants to click, screenshot, fill forms, extract data, or navigate real web pages. Default to screenshots + coordinate clicks, not selector hunting. Requires the one-time `browser-harness` CLI install (see references/install.md).

io.github.TriliumNext/Trilium/ckeditor5-reviewing

Review or audit CKEditor 5 plugin code in the Trilium (TriliumNext Notes) monorepo, or a PR/diff touching packages/ckeditor5-* or the packages/ckeditor5 build. Use when checking a Trilium CKEditor 5 plugin for correctness and idiom: schema / conversion / command / UI / widget code, CKEditor-specific defects (asymmetric upcast/downcast, unconsumed upcast elements, missing inline-widget position mapping, command refresh/isEnabled bugs, memory leaks, t() gaps, editing/UI split violations), and Trilium integration defects (plugin not registered in plugins.ts, button missing from toolbar.ts, import/file-extension lint failures, wrong augmentation module, .po localization gaps, wrong test environment). Pairs with the ckeditor5-plugin-development and ckeditor5-testing skills and delegates their checklists.

io.github.TriliumNext/Trilium/ckeditor5-testing

Testing CKEditor 5 plugins in the Trilium monorepo. Use when adding or reviewing unit tests for a packages/ckeditor5-* package, debugging a failing test, or setting up a package's test runner. Covers the two Vitest environments Trilium uses (happy-dom and the WebdriverIO browser mode), the per-package vitest.config.ts, testing against a real ClassicEditor, the model/view helpers imported from 'ckeditor5' (_setModelData / _getModelData / _getViewData and their {}/[] selection syntax), vi spies/mocks, idiomatic patterns for schema/conversion/command/UI tests, the pnpm --filter runner, and Trilium-specific conventions and gotchas. Complements the ckeditor5-plugin-development and writing-unit-tests skills.

io.github.abhigyanpatwari/GitNexus/gitnexus-pdg-query

Use when querying or extending GitNexus's PDG control/data-dependence surface (the `pdg_query` MCP tool, CDG/REACHING_DEF edges), or reasoning about "what controls X" / "where does Y flow" / guard clauses. Examples: "what guards this statement?", "trace this variable within the function", "why is the pdg_query result empty?", "add a CDG query".

io.github.EpicenterHQ/epicenter/testing

Test file conventions: setup functions, factories, organization, type testing, naming, and pruning low-value tests. Use when: "write tests", "add a test", "fix this test", "delete tests", "prune tests", "audit tests", or modifying *.test.ts files.

io.github.biersoeckli/QuickStack/backend-testing

Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions. Use when editing backend test files under `src/server/`, `src/shared/`, or `src/__tests__/integration/`, or when the user asks for backend test coverage, mocks, Prisma test DB setup, or Kubernetes integration tests.

io.github.biersoeckli/QuickStack/backend-services

Create and update QuickStack backend services, adapters, standalone services, and server actions using the project's established singleton, adapter, caching, and error-handling patterns. Use when editing files under src/server/services, src/server/adapter, src/server/utils, src/server.ts, or related server-side actions and backend utilities.

io.github.Nevo24/leap/cursor-editor-agent-tabs

How the Leap Monitor shows read-only editor-GUI agent rows - open Cursor (the editor) Agent/Composer tabs AND VS Code Copilot Chat sessions. Covers the on-disk scans (scan_open_cursor_agents, scan_open_vscode_copilot_sessions), status mapping, jump via the shared Leap extension, synthetic row reconciliation, the close buttons (Cursor close-tab / VS Code remove-row), and the shared GUI_TAG_PREFIXES/GUI_ROW_TYPES plumbing. Use this when working on cursor_gui_scan.py, vscode_copilot_scan.py, editor-GUI agent rows, or editor chat navigation.

io.github.fuyuxiang/echo-agent/docker-manage

Manage Docker containers, images, volumes, and Compose stacks. Requires Docker CLI access.

io.github.ccusage/ccusage/testing

Guides ccusage Rust and Node tests. Use when adding or fixing cargo tests, Node test files, CLI snapshots, Claude model pricing, LiteLLM compatibility, or fixture-backed tests.

io.github.ccusage/ccusage/typescript

Guides ccusage TypeScript and JavaScript work. Use before reading or editing .ts, .tsx, .js, or .jsx files, including package launchers, Node tests, schemas, mocks, and typed fixtures.

io.github.binrogithub/1-3-Cloud-Adoption-Skills/CSS-Code-Search-MCP

Deploy a CSS/OpenSearch code-search MCP server on Huawei Cloud ECS from scratch, so that Claude Code (claude-glm) can search a GitHub repo's code and docs as native MCP tools. Use when the task is to provision a new Huawei Cloud CSS cluster and ECS, index a code repository into CSS, and expose it as a searchable MCP tool for AI coding agents.

io.github.abhigyanpatwari/GitNexus/gitnexus-exploring

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

io.github.abhigyanpatwari/GitNexus/gitnexus-refactoring

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

io.github.abhigyanpatwari/GitNexus/gitnexus-exploring

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

io.github.abhigyanpatwari/GitNexus/gitnexus-refactoring

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

io.github.abhigyanpatwari/GitNexus/gitnexus-exploring

Navigate unfamiliar code using GitNexus knowledge graph

io.github.abhigyanpatwari/GitNexus/gitnexus-refactoring

Plan safe refactors using blast radius and dependency mapping