AI Context Template
A filled example for docs/AI_CONTEXT.md so agents understand purpose, stack, and risks quickly.
Copilot ✓Cursor ✓Kilo ✓
AuthorNeexoCore
Updated
contextonboardingguardrails Purpose
Each active repository should have a short docs/AI_CONTEXT.md (1–2 pages).
Example (anonymous)
# AI Context
## Purpose
Multi-tenant SaaS dashboard for managing widgets per organization.
## Stack
- Next.js 16 App Router, TypeScript strict
- Drizzle ORM + PostgreSQL (Neon)
- Clerk organizations
- Zod v4, shadcn/ui v4, Tailwind 4
## Playbook
saas-multi-tenant — https://awesome.neexo.dk/api/playbooks/saas-multi-tenant
## Important folders
- `src/app/` — routes and UI
- `src/db/` — schema and migrations
- `src/lib/auth/` — Clerk helpers
## High-risk areas
- Tenant isolation on all queries
- Database migrations (always ship SQL with code)
- Billing webhooks (idempotent handlers)
## Avoid by default
- `drizzle/migrations/*.sql` unless explicitly working on migrations
- `.env.keys`, production dumps
- Large `.glb` / render assets
## Validation
npm run lint
npm run build
npx drizzle-kit check
## Manual verification
- Org switch still scopes data after auth changes
Keep project-specific names internal; use playbook slugs on the public hub.
Raw content
Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md
## Purpose
Each active repository should have a short `docs/AI_CONTEXT.md` (1–2 pages).
## Example (anonymous)
```markdown
# AI Context
## Purpose
Multi-tenant SaaS dashboard for managing widgets per organization.
## Stack
- Next.js 16 App Router, TypeScript strict
- Drizzle ORM + PostgreSQL (Neon)
- Clerk organizations
- Zod v4, shadcn/ui v4, Tailwind 4
## Playbook
saas-multi-tenant — https://awesome.neexo.dk/api/playbooks/saas-multi-tenant
## Important folders
- `src/app/` — routes and UI
- `src/db/` — schema and migrations
- `src/lib/auth/` — Clerk helpers
## High-risk areas
- Tenant isolation on all queries
- Database migrations (always ship SQL with code)
- Billing webhooks (idempotent handlers)
## Avoid by default
- `drizzle/migrations/*.sql` unless explicitly working on migrations
- `.env.keys`, production dumps
- Large `.glb` / render assets
## Validation
npm run lint
npm run build
npx drizzle-kit check
## Manual verification
- Org switch still scopes data after auth changes
```
Keep project-specific names internal; use playbook slugs on the public hub.