Global development guidelines for the LangChain monorepo
This document provides context to understand the LangChain Python project and assist with development.
## Corridor security analysis
When Corridor's `analyzePlan` tool
crates for Next.js SWC bindings
├── test/ # All test suites
├── examples/ # Example Next.js applications
├── docs/ # Documentation
└── scripts/ # Build and maintenance scripts
```
### Core Package: `packages/next`
The main Next.js framework lives in `packages/next
file selector and pass the remaining files.
Preserve exit status through logging. Use the documented detached runner and
eval lock. Review the final launcher after edits; preparation and `--list`
modes
methods, newtypes, or other idiomatic Rust API shapes when they keep the callsite self-documenting.
- When you cannot make that API change and still need a small positional-literal callsite
explanation of the current behavior.
- Keep implementations/docstrings aligned unless a divergence is intentional and documented.
Practical check:
- After edits, sanity-check that docs mention only APIs/behavior that exist in code
Code με την επέκταση Jupyter
```
### Εργασία με Διάφορους Τύπους Μαθημάτων
- **Μαθήματα "Μάθε"**: Εστίαση στο documentation README.md και στις έννοιες
- **Μαθήματα "Κατασκευή"**: Περιλαμβάνουν λειτουργικά παραδείγματα κώδικα σε Python και TypeScript
- Κάθε
Configuration Node.js/TypeScript
```bash
# Installer les dépendances au niveau root (pour les outils de documentation)
npm install
# Pour les exemples TypeScript de chaque leçon, naviguez vers la leçon spécifique
naamgevingsconventie: `{provider}-{voorbeeld-naam}.{py|ts|js}`
4. Test met daadwerkelijke API-gegevens
5. Documenteer nieuwe omgevingsvariabelen in les README
### Documentatie Bijwerken
1. Bewerk README.md in de lesmap
2. Volg
inside
pip install -r requirements.txt
```
### Node.js/TypeScript Setup
```bash
# Install root-level dependencies (for documentation tooling)
npm install
# For individual lesson TypeScript examples, make you waka go di specific lesson
provider}-{nome-exemplo}.{py|ts|js}`
4. Teste com credenciais reais da API
5. Documente novas variáveis de ambiente no README da aula
### Atualizando Documentação
1. Edite README.md no diretório
pentru traduceri
- Comunitate activă pe Discord pentru întrebări și suport
---
**Declinare a responsabilității**:
Acest document a fost tradus folosind serviciul de traducere AI [Co-op Translator](https://github.com/Azure/co-op-translator).
Prefer returning `ActionResult` with structured content to help the agent reason better.
- Follow the documentation in : some docs have been truncated, if unsure, you can visit or request the information
Structure
| Directory | Purpose |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| `apps/studio` | Supabase Studio/Dashboard — has its own `apps/studio/AGENTS.md` (see below) |
| `apps/docs` | Documentation site — Next.js app router, MDX (port 3001, served under `/docs`) — has its own `apps/docs/AGENTS.md` |
| `apps/www` | Marketing
length, brevity
- `style-guide/02-elements.md` — admonitions, code blocks, procedures, tabs, images
- `style-guide/03-page-structure.md` — document type, section grouping, chunking
Load the file you need rather than the whole directory
directory of the project
pnpm dev:kb
# From the apps/kb directory
pnpm dev
```
### Astro documentation
Full documentation: https://docs.astro.build
Consult these guides before working on related tasks:
- [Adding pages, dynamic