01
Minimal AGENTS.md
Shows how a short instruction file gives coding agents essential repository context.
View example →Browse AGENTS.md project patterns by category and difficulty.
Shows how a short instruction file gives coding agents essential repository context.
Defines reliable setup, development, and validation commands agents can run consistently.
Captures naming, formatting, and implementation conventions that help changes fit existing code.
Sets clear limits on files and directories an agent may inspect or modify.
Combines project context, commands, coding rules, and completion criteria in one concise guide.
Requires build and type checks to catch compilation and static typing problems.
Adds linting guidance that catches style and code quality issues before work is finished.
Scopes test runs to changed behavior while requiring relevant coverage before completion.
Prevents lockfile conflicts by directing agents to the package manager already used.
Orders formatting, lint, type checking, tests, and builds into a repeatable validation sequence.
Places routing, layouts, server components, and data loading within the Next.js App Router.
Organizes React features around cohesive components, hooks, and domain specific modules.
Separates Express route handling, validation, and business logic into clear service boundaries.
Defines reusable UI components with stable interfaces and limited application specific dependencies.
Guides agents to preserve module ownership and avoid dependencies across protected boundaries.
Sets expectations for focused unit tests, readable assertions, and meaningful behavior coverage.
Requires a regression test that reproduces each reported defect before its fix is accepted.
Checks API behavior across routing, validation, persistence, and response boundaries with integration tests.
Uses browser driven journeys to verify important user flows across the application interface.
Introduces characterization tests that document existing behavior before risky legacy changes.
Explains which repository wide instructions belong in the root guidance file.
Separates frontend and backend guidance so agents apply each rule to the right files.
Places shared and package specific rules at the directory levels where they apply.
Shows how nested instructions refine inherited rules while resolving direct conflicts explicitly.
Keeps legacy package exceptions local while preserving modern conventions across the monorepo.
Documents schema changes, query practices, and safeguards for a PostgreSQL backed application.
Covers Supabase client usage, migrations, row security, and generated database types.
Coordinates Prisma schema edits, migrations, generated clients, and query conventions.
Promotes reviewed, reversible database migrations that preserve data and minimize deployment risk.
Identifies related writes that must commit or roll back together to protect data consistency.
Defines secure sign in, session handling, and account recovery responsibilities for authentication code.
Requires access checks at trusted boundaries and tests that protect resources from unauthorized users.
Keeps credentials in environment configuration and prevents secret values from entering source control.
Guides careful validation, authorization, auditing, and error handling for sensitive API operations.
Checks dependency changes for advisories, license concerns, and unintended version or lockfile drift.
Directs client updates through the API schema and generator instead of editing generated output.
Treats the OpenAPI specification as the source for validated, reproducible client generation.
Keeps database schema changes aligned with generated types and their consuming application code.
Explains how to update source documentation and regenerate published artifacts through the established tooling.
Marks generated files as derived output and points agents toward their editable source inputs.
Covers native project structure, platform differences, Expo commands, and device focused validation.
Requires plan review and careful state handling before applying infrastructure configuration changes.
Documents pipeline triggers, workflow validation, deployment protections, and safe changes to CI configuration.
Adapts contribution guidance for prose, links, examples, accessibility, and documentation build checks.
Defines retry, idempotency, queue, and failure handling expectations for background processing.
Coordinates Next.js rendering, Supabase authentication, database access, and safe public environment configuration.
Aligns frontend, backend, shared packages, workspace commands, and ownership rules across a monorepo.
Encourages incremental changes that respect undocumented behavior and require targeted regression coverage.
Sets boundaries for external API credentials, timeouts, retries, response validation, and failure handling.
Combines deployment, security, testing, data, and operational guidance for a full stack application.