Independent second-opinion code review using Codex CLI. Use when: wanting an external AI reviewer's perspective, cross-validating before push, getting a second pair of eyes. Triggers on: '/peer-review', 'codex review', 'second opinion', 'peer review my changes'.
Use when reviewing a plan or spec for developer-facing API, CLI, SDK, MCP, plugin, integration guide, getting-started documentation, or developer onboarding design before implementation.
Use when reviewing a plan from a founder or product-ceo perspective and you need to challenge premises, choose scope expansion vs hold vs reduction, and push for the best product outcome.
Use when reviewing an execution plan and you need engineering scrutiny across architecture, data flow, diagrams, edge cases, test coverage, and performance.
Use when the user asks for a report-only browser QA pass on a web application, live site, preview URL, authenticated app flow, or release candidate without making code changes.
Use when the user explicitly requests security best practices guidance, a security review or report, or secure-by-default coding help for Python, JavaScript or TypeScript, or Go code.
Use when auditing the live design quality of a site without changing code. Trigger on "site-design-audit", design audit, visual QA, AI slop detection, typography review, spacing review, hierarchy review, or requests to review a rendered site and optionally infer DESIGN.md.
Use when auditing a live site's design and then fixing the issues in source code. Trigger on "site-design-fix", design fix loop, visual QA with fixes, AI slop cleanup, frontend polish from screenshots, or requests to audit then repair live UI issues.
Research → Plan → Code workflow. Enforces evidence-based reasoning, codebase research, and structured planning before code modifications. Applied automatically for moderate+ tasks.
Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design. Reference these guidelines when: - Writing SQL queries or designing schemas - Implementing indexes or query optimization - Reviewing database performance issues - Configuring connection pooling or scaling - Optimizing for Postgres-specific features - Working with Row-Level Security (RLS) Read individual rule files for detailed explanations and SQL examples: Each rule file contains: - Brief…
Use when writing, reviewing, or optimizing Supabase or Postgres queries, schema designs, indexes, row-level security policies, or database configuration for performance and correctness.
Version 1.0.0 Vercel Engineering January 2026 Note: This document is mainly for agents and LLMs to follow when maintaining, generating, or refactoring React and Next.js codebases. Humans may also find it useful, but guidance here is optimized for automation and consistency by AI-assisted workflows. Comprehensive performance optimization guide for React and Next.js applications, designed for AI agents and LLMs. Contains 40+ rules across 8 categories, prioritized by impact from critical (eliminating waterfalls, reducing bundle size) to incremental (advanced patterns). Each…
Use when writing, reviewing, or refactoring React or Next.js code and you need performance-oriented guidance for components, data fetching, rendering, or bundle size decisions.
Delegate a complete implementation, investigation, or debugging unit to Cursor CLI, then let Codex accept and finish the result. Use when the user wants to use Cursor capacity or reduce Codex work through delegation, with resumable sessions and explicit task boundaries.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.