# Project Documentation> Generated: [timestamp] | Mode: FULL
## Tech Stack- Runtime: [e.g. Node.js 20, Python 3.11]- Language: [e.g. TypeScript, Python]- Framework: [e.g. Next.js 14 App Router, FastAPI]- Database: [e.g. PostgreSQL via Prisma]- Styling: [e.g. Tailwind CSS]- State Management: [e.g. Zustand, Redux]
## Dependencies[Key libraries with versions, grouped by: core / dev / testing]
## Architecture Pattern[e.g. Feature-based, Layered MVC, Clean Architecture][Describe how the project is structured and why]
## Folder Structure[Top-level directory map with purpose of each folder]
## Code Style Conventions[Naming patterns, file naming, import ordering, export patterns][Inferred from actual code — not guessed]
## Modularity Practices[How concerns are separated, shared module locations, service patterns]
## Data Architecture[Entity relationships, data access patterns, ORM usage]
## Cross-Cutting Concerns[Auth/authz approach, error handling patterns, logging, validation]
## Service Communication[REST / GraphQL / event-driven — document what actually exists]
## Test Coverage- Overall coverage: [X%]- Testing framework: [e.g. Jest, Vitest, Pytest]- Key untested areas: [list]- Test patterns used: [unit / integration / e2e]
## Entry Points[Main files, key config files, environment setup]
## Changed Files[Only present in delta scans — list of files re-scanned]
## Last Scanned[ISO timestamp]

# AGENTS.md — [Project Name]> Auto-generated by the dev pipeline scanner. Do not edit manually.> Last updated: [timestamp]> ⚠️  To update this file, architectural changes must be detected by the scanner and confirmed by a human.
## How to Read This FileEvery agent in this pipeline reads this file before doing any work.It defines the rules, patterns, and guardrails specific to this project.
## Stack Context[One-line summary: e.g. "Next.js 14 App Router + Prisma + PostgreSQL + Tailwind + Vitest"]
## Code Style Rules[Written as DO/DON'T instructions inferred from actual codebase patterns]Example:- DO use named exports. Default exports are not used in this project.- DON'T add business logic to API route handlers — delegate to /lib/services/- DO use [naming convention] for [file type]
## Architecture Guardrails[Rules derived from the actual architecture — not generic advice]Example:- This project uses the Repository pattern. Never query the DB directly from components.- All API responses must go through the [ResponseWrapper] utility.
## Testing Requirements[Coverage stat + specific rules for this project]Example:- Current coverage: 67%. All new code must include unit tests.- QA agent: flag any feature with <80% coverage on new code.- Integration tests use [real DB / mock DB] — do not change this.
## Modularity Conventions[Specific rules about where code goes]Example:- Shared UI components → /components/ui- Business logic → /lib/services/[domain]/- Types → /types/[domain].ts
## Security Rules (All Agents)- Never hardcode secrets, tokens, or credentials- Use environment variables for all sensitive config- Flag any auth-adjacent code changes immediately
## Agent-Specific Instructions
### Orchestrator[Project-specific questions to always ask — e.g. "Does this touch the payment flow?"]
### Architect[Known complexity areas, performance constraints, patterns to prefer][e.g. "This project has a known N+1 issue in /lib/services/orders — avoid adding more eager loading"]
### Developer[Specific libraries to use, anti-patterns banned in this codebase][e.g. "Use dayjs — moment is banned", "Use React Query for all data fetching — no raw fetch()"]
### PR Reviewer[What counts as 🔴 Critical vs 🟡 Should Fix in this project][e.g. "Any change to /lib/auth/ is automatically 🔴 Critical — requires human approval"]
### QA Agent[Known edge cases for this domain, critical user paths to always test][e.g. "Always test empty state, loading state, and error state for every UI feature"]