Engineering Team Context File
Engineering Team Context File
ClaudeChatGPTGemini
Health
0/100
▲ 49
📋 346 copies
Trigger Phrase
Use our team context
Prompt
150 words## Team Context
**Stack:** [YOUR STACK — e.g. Next.js 14, FastAPI, PostgreSQL 15, Redis, deployed on AWS ECS]
**Code Style:**
- TypeScript strict mode, no any
- Function components only, no class components
- Async/await over promise chains
- Errors always logged before re-thrown
- All API routes validated with Zod
**Our Conventions:**
- Branch naming: feat/TICKET-description, fix/TICKET-description
- Commit style: conventional commits (feat:, fix:, chore:)
- PR size: aim for under 400 lines changed
- Tests required for: all API routes, all utility functions, any bug fix
**What We Don't Do:**
- No direct database access from frontend
- No secrets in code (use env vars, never committed)
- No skipping code review for 'quick fixes'
**Current Focus:** [FILL IN — e.g. migrating from REST to GraphQL, improving test coverage from 40% to 80%]
Paste this at the start of any AI coding session. Update the bracketed sections for your team.
**Stack:** [YOUR STACK — e.g. Next.js 14, FastAPI, PostgreSQL 15, Redis, deployed on AWS ECS]
**Code Style:**
- TypeScript strict mode, no any
- Function components only, no class components
- Async/await over promise chains
- Errors always logged before re-thrown
- All API routes validated with Zod
**Our Conventions:**
- Branch naming: feat/TICKET-description, fix/TICKET-description
- Commit style: conventional commits (feat:, fix:, chore:)
- PR size: aim for under 400 lines changed
- Tests required for: all API routes, all utility functions, any bug fix
**What We Don't Do:**
- No direct database access from frontend
- No secrets in code (use env vars, never committed)
- No skipping code review for 'quick fixes'
**Current Focus:** [FILL IN — e.g. migrating from REST to GraphQL, improving test coverage from 40% to 80%]
Paste this at the start of any AI coding session. Update the bracketed sections for your team.
Install Instructions
Paste this file at the start of any AI coding conversation. Fill in the bracketed sections with your actual stack and conventions. Keep it under 500 words.
Test It
Test command:
Start a coding session with this context, then ask a stack-specific question
Expected output:
AI should respect the stated conventions in its code suggestions
Pass criteria:
- Suggests TypeScript. Doesn't use class components. Respects the error handling convention.
⚠️ Guardrails
- Update this file when your stack or conventions change. Stale context is worse than no context.