Auto GPT

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

This file provides guidance to Claude Code when working with the direct benchmark harness.

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Address PR review comments and loop until CI green and all comments resolved. TRIGGER when user asks to address comments, fix PR feedback, respond to reviewers, or babysit/monitor a PR.

Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them. TRIGGER when user asks to write frontend tests, add test coverage, or 'write tests for my changes'.

Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment",

Set up a new git worktree for parallel development. Creates the worktree, copies .env files, installs dependencies, and generates Prisma client. TRIGGER when user asks to set up a worktree, work on a branch in isolation, or needs a separate environment for a branch or PR.

Open a pull request with proper PR template, test coverage, and review workflow. Guides agents through creating a PR that follows repo conventions, ensures existing behaviors aren't broken, covers new behaviors with tests, and handles review via bot when local testing isn't possible. TRIGGER when user asks to "open a PR", "create a PR", "make a PR", "submit a PR", "open pull request", "push and cr

E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls. TRIGGER when user asks to manually test a PR, test a feature end-to-end, or run integration tests against a running system.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Version 1.0.0 Vercel Engineering January 2026

Meta-agent supervisor that manages a fleet of Claude Code agents running in tmux windows. Auto-discovers spare worktrees, spawns agents, monitors state, kicks idle agents, approves safe confirmations, and recycles worktrees when done. TRIGGER when user asks to supervise agents, run parallel tasks, manage worktrees, check agent status, or orchestrate parallel work.

Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.

Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.

Load large data or modules only when a feature is activated.

Preload heavy bundles before they're needed to reduce perceived latency.

Early Length Check for Array Comparisons

Move await operations into the branches where they're actually used to avoid blocking code paths that don't need them.

Instead of awaiting data in async components before returning JSX, use Suspense boundaries to show the wrapper UI faster while data loads.

Use React's <Activity to preserve state/DOM for expensive components that frequently toggle visibility.

Prevent Waterfall Chains in API Routes

Extract static JSX outside components to avoid re-creation.

For operations with partial dependencies, use better-all to maximize parallelism. It automatically starts each task at the earliest possible moment.

Finding the smallest or largest element only requires a single pass through the array. Sorting is wasteful and slower.

Animate SVG Wrapper Instead of SVG Element

Return early when result is determined to skip unnecessary processing.

Build Index Maps for Repeated Lookups

React.cache() only works within one request. For data shared across sequential requests (user clicks button A then button B), use an LRU cache.

When updating state based on the current state value, use the functional update form of setState instead of directly referencing the state variable. This prevents stale closures, eliminates unnecessary dependencies, and creates stable callback references.

Pass a function to useState for expensive initial values. Without the function form, the initializer runs on every render even though the value is only used once.

Store callbacks in refs when used in effects that shouldn't re-subscribe on callback changes.

Use Next.js's after() to schedule work that should execute after a response is sent. This prevents logging, analytics, and other side effects from blocking the response.

Use useSWRSubscription() to share global event listeners across component instances.

Mark frequent, non-urgent state updates as transitions to maintain UI responsiveness.

Use toSorted() Instead of sort() for Immutability

SWR enables request deduplication, caching, and revalidation across component instances.

Use React.cache() for server-side request deduplication. Authentication and database queries benefit most.

Use next/dynamic to lazy-load large components not needed on initial render.

When rendering content that depends on client-side storage (localStorage, cookies), avoid both SSR breakage and post-hydration flickering by injecting a synchronous script that updates the DOM before React hydrates.

The React Server/Client boundary serializes all object properties into strings and embeds them in the HTML response and subsequent RSC requests. This serialized data directly impacts page weight and load time, so size matters a lot. Only pass fields that the client actually uses.

Extract expensive work into memoized components to enable early returns before computation.

Avoid changing styles one property at a time. Group multiple CSS changes together via classes or cssText to minimize browser reflows.

Use a module-level Map to cache function results when the same function is called repeatedly with the same inputs during render.

Use explicit ternary operators (? :) instead of && for conditional rendering when the condition can be 0, NaN, or other falsy values that render.

Import directly from source files instead of barrel files to avoid loading thousands of unused modules. Barrel files are entry points that re-export multiple modules (e.g., index.js that does export from './module').

When updating manual sections ( ) in block documentation files (e.g., docs/integrations/basic.md), follow these formats:

This file provides guidance to coding agents when working with the frontend.

Type Tool Speed Purpose --------------- --------------------- --------------- -------------------------------- E2E Playwright Slow (~5s/test) Real browser, full user journeys Integration Vitest + RTL Fast (~100ms) Component + mocked API Unit Vitest + RTL Fastest (~10ms) Individual functions/components Visual Storybook + Chromatic N/A UI appearance, design system

This directory contains the Graphiti-backed memory integration for CoPilot. This file is developer documentation only — it is NOT injected into LLM prompts. Runtime prompt instructions live in prompting.py:getgraphitisupplement().

This file provides guidance to coding agents when working with the backend.

This file provides guidance to coding agents when working with code in this repository.

This guide provides context for coding agents when updating the autogptplatform folder.