Never include untrusted inputs into the model context. This includes asking Gemini CLI to process mail, documents, or other resources from unverified sources.

Pour un modèle aussi grand que le GPT-120B, il ne faut plus qu’un minimum de quatre machines équipées d’une carte graphique standard. Le coût unitaire de ces GPU est d’environ 2 300 CHF (environ 2 400 €).

Peux tu récupérer le contenu des fichiers affichés dans cette vidéo ? (claude.md) https://www.youtube.com/watch?v=kkkQKAPxna8

## Core Commands
- `pnpm dev`: Start development server with Turbopack
- `pnpm build`: Build the application
- `pnpm start`: Start production server
- `pnpm tsc`: Run TypeScript type checking
- `pnpm lint`: Run ESLint without auto-fix for CI
- `pnpm lint:fix`: Run ESLint with auto-fix
- `pnpm format`: Format code with Prettier
 
## Testing Commands
- **CRITICAL**: ALWAYS use CI commands for testing (non-interactive mode)
- `pnpm test:ci`: Run unit tests in CI mode (located in `__tests__`)
- `pnpm e2e:ci`: Run e2e tests in CI mode (headless) (located in `e2e`)
 
## Styling preferences
- Use the shared typography components in `src/components/ui/typography.tsx` for paragraphs and headings (instead of creating custom `p`, `h1`, `h2`, etc.).
- Prefer the card container `src/components/ui/card.tsx` for styled wrappers rather than adding custom styles directly to `div` elements.
 
## Shadcn/UI Component Usage
- **ALWAYS** use `src/components/ui/input-group.tsx` when you need to add icons, buttons, or text addons to an input field.
    - inputs with prefix/suffix text or labels
    - inputs with toggle buttons (search, password visibility toggle, etc.)
- **ALWAYS** use `src/components/ui/button-group.tsx` when elements or buttons are positioned side by side.
    - For grouped actions (Cancel/Submit, Previous/Next, etc.)
    - inputs combined with submit buttons (`Input + Button`)
- **NEVER** create custom wrapper divs with manual styling for these patterns -- use the provided components for consistent styling.
 
## Utilities and Reusable Logic
- **FIRST** search existing code with `grep/fzf` for similar implementations.
- **ALWAYS** prefer established libraries over custom solutions for common patterns.
- Example: Use `lodash` utilities instead of recreating array/object helpers.
- Custom implementations should only exist for project-specific business logic.
 
## TypeScript Imports
Important: when you import thing try to always use Typescript paths:
- `@/*` is link to `@src`
- `@mail/*` is link to `@emails`
- `@app/*` is link to `@app`
 
## Workflow modification
- **CRITICAL RULE -- ALWAYS FOLLOW THIS**
- **BEFORE editing any files, you MUST Read at least 3 files** that will help you to understand how to make a coherent and consistency...
- This is **NON-NEGOTIABLE**. Do not skip this step under any circumstances. Reading existing files ensures:
    1. Code consistency with project patterns
    2. Understand the patterns, conventions, and API usage
    3. Only then proceed with creating/editing files
 
## Debug Github Action
When you debug Github action and you need to download artifact, please download inside `ci-artifacts/<run-id>`.
 
## UI Component Rules (MANDATORY)
- **ALWAYS** use `src/components/ui/typography.tsx` --> NEVER use raw `<p>`, `<h1>`, `<h2>` tags
- **ALWAYS** use `src/components/ui/card.tsx` and `src/components/ui/item.tsx` --> NEVER create custom wrappers
- **NEVER** create custom components++ when existing UI components exist -- ALWAYS search first
 
# Known Limitations
- macOS only (uses Keychain)
- Requires `git` CLI for git status
- Requires Claude Code OAuth (not API key)
- Transcript must be accessible (permissions)
 
# Memory
- Always use camelCase