Probe the local Apify MCP server with mcpc during development. Use proactively after implementing features or fixing bugs to test that the implementation follows the spec, confirm requirements are met, and discover failing or missing behavior.
Emulates Michael’s PR review style. Proactively discovers the current PR (or asks), diffs against the develop branch by default, analyzes changes and related context across the repo, and produces a structured, practical markdown review with actionable feedback, tests to add, rollout/deprecation plans, generated-code…
Emulates Stefan’s PR review style. Proactively finds the related PR for the current branch (or asks), diffs against origin/develop by default, performs a deep system-aware review, and outputs an actionable Markdown document with line references, severity, and suggestions.
Use this agent when you need expert code review focusing on architectural quality, clean code principles, and best practices. Examples: Context: User has just written a new service class and wants architectural feedback. user: 'I just implemented a user authentication service. Can you review it?' assistant: 'I'll use…
Use this agent when the user requests examples for a component, asks to add stories to a component, needs documentation examples updated, or mentions creating/updating component demonstrations. Examples:\n\n \nContext: User is working on the Checkbox component and wants to add new usage examples.\nuser: "Can you…
Use this agent when you need to discover and suggest new examples for Ark UI components. This includes:\n\n \nContext: User is working on enhancing the Checkbox component documentation.\nuser: "I've just finished updating the Checkbox component API. Can you help me find what examples we should add?"\nassistant: "I'll…
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
Use this agent when the user needs markdown files created in the test-files/ directory. This includes generating test data files, sample documentation, mock content, or any markdown-formatted files for testing purposes.\n\nExamples:\n\n \nContext: User needs sample markdown files for testing a documentation…
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Pre-commit code reviewer — checks for correctness, security, and MockServer conventions. Spawn this agent when you need a focused review of staged/unstaged changes before committing.
Production debugger — investigates issues using logs, CI data, metrics, and AWS infrastructure. Spawn this agent to diagnose build failures, runtime errors, or infrastructure problems. It reports findings; it does not fix.
Buildkite pipeline failure investigator. Spawn this agent to analyse CI/CD build failures, extract root causes from logs, and cross-reference with recent commits and infrastructure. Read-only — it diagnoses, not fixes.
Use to review any change that touches PowerSync synced tables before merging — diffs that modify shared/powersync-tables.ts, a config.yaml sync rule, backend or frontend Drizzle schema, backend/drizzle migrations, the DAL/defaults/reconciliation for a synced table, sync middleware/transformers, or…
Use to review React (.tsx) changes for the project's useEffect discipline and React conventions before merging — flags effects used for derived state, prop→state syncing, parent notification, reset-on-prop, one-time init, navigation, or ref assignment, and suggests the prescribed alternative. Also checks…
Use this agent when the user wants to generate, update, or create CLAUDE.md documentation for a FormKit package. This includes when the user asks to document a specific package's architecture, wants to understand how a package works, or needs to create onboarding documentation for future LLMs working with the…
Use this agent when the user needs to create or edit changelog entries in the Docusaurus documentation. Specifically, use this agent when: 1) The user mentions adding a new changelog entry or release notes, 2) The user asks to update or modify existing changelog entries, 3) The user wants to document a new feature…
Use when requirements, an approved design, or a root cause are clear and one scoped, complete implementation is authorized. Do not use for unresolved exploration, product decisions, diagnosis-only work, or review-only requests.
Use proactively after an implementation or when an existing diff needs correctness, regression, concurrency, compatibility, and meaningful verification review. Do not use for implementation or a dedicated exploitability assessment.
4.6k▲
+1 2d agoA40 tokens
originalMIT
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: