← ClaudeAtlas

cce-routinglisted

Use Cursor Bridge's read-only cursor_context_engine for unfamiliar project understanding when the exact code location is unknown or the task requires tracing behavior, symbols, callers and callees, data flow, registrations, interface implementations, ownership boundaries, or cross-module relationships. Trigger for questions such as where something is implemented, what owns state, how a project flow works, or when local search would otherwise guess paths or repeat blind queries; for these semantic questions, try CCE before generic context-mode or grep discovery. Do not use when a known exact file or symbol can answer the question through direct reading or exact search, for content already loaded in context, trivial single-file edits, tests, logs, builds, Git work, external documentation, or when the user opts out of Cursor. Verify returned path:line evidence in the real files.
Vanyangyang/cursor-bridge · ★ 83 · Code & Development · score 86
Install: claude install-skill Vanyangyang/cursor-bridge
# CCE Routing `cursor_context_engine` automatically inherits the persistent CCE model and reasoning-effort default configured through `cursor_model`. Do not change or reset that default unless the user explicitly asks; if selection cannot be confirmed, report the pre-send failure instead of retrying with Auto. Route project-understanding questions to the cheapest evidence surface that can answer them without guessing. ## Choose CCE for project semantics Call `cursor_context_engine` when one or more of these are true: - The implementation location is unknown and finding it locally would require guessing directories or repeating broad searches. - The question asks where or how a project behavior is implemented, what owns a state or responsibility, or why a flow behaves as it does. - The answer requires tracing callers and callees, producer-consumer flow, configuration and registration, interface implementations, data ownership, or relationships across modules. - An unfamiliar indexed project needs semantic context before a safe edit or review can begin. Prefer one CCE investigation over starting an Explore subagent merely to locate or understand project code. Let Cursor choose focused or extended depth from what it discovers. When these semantic conditions match, make CCE the first project-discovery surface. Do not establish the answer through generic context-mode, grep, or blind local exploration before trying CCE. If Claude Code denies an initial context-mode collectio