Cursor 多包 monorepo 上下文管理架构指南
Оригинальный заголовок: Architectural guidelines for managing context across multi-package monorepos in Cursor
Заголовок и краткое изложение на выбранном языке ожидают перевода.
Cursor 官方指南给出三步配置，解决 Composer 在大型 monorepo 中跨包串上下文、混淆前后端约定的问题。做法是在各子包放置轻量 .cursorrules 而非单一根文件，因为 Composer 会优先采用离当前打开文件最近的规则文件；提示时显式引用相对路径（如 @packages/api/src/...），避免全工作区模糊语义搜索，让提示词预算集中在当前包的 AST 上。
Полный текст на выбранном языке ожидает перевода. Пока показан оригинал.
When working in larger monorepos or multi-service projects, Composer often pulls context from the wrong package or mixes up frontend and backend conventions.
Here is a 3-step configuration that solves cross-package bleeding:
-
Root vs. Package Scoping:
Place lightweight.cursorrulesin individual subpackages rather than one massive root file. Cursor Composer prioritizes the rule file closest to the active open file. -
Strict File Invariants:
In your backend service.cursorrules:
- Backend: FastAPI / Python 3.11
- Scope: Inbound requests must extract authentication from Authorization header. Never accept tenant_id from body.
In your frontend .cursorrules:
- Frontend: Next.js 14 App Router
- Rule: Server components by default. Add 'use client' only when state hooks (useState, useEffect) are strictly required.
- Terminal Context Isolation:
When prompting Composer, reference relative file paths explicitly (@packages/api/src/...) rather than relying on fuzzy semantic search across the entire workspace. This keeps the prompt budget focused on the active package’s AST.
Источник: Cursor Forum · Guides · forum.cursor.com