From 99d68a5135dff9eb8c0ffbdddf2614692f2cb858 Mon Sep 17 00:00:00 2001 From: CroneKorkN Date: Sun, 10 May 2026 21:36:59 +0200 Subject: [PATCH] =?UTF-8?q?AGENTS.md:=20soften=206th=20rule=20=E2=80=94=20?= =?UTF-8?q?ccc=20is=20an=20option,=20not=20a=20mandate?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.7 (1M context) --- AGENTS.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 4e6052b..d5564a5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -38,12 +38,15 @@ Six rules; follow these and you won't break things: 5. **Prefer adding helpers to `libs/`** over duplicating logic across bundles. Repo-wide helpers go in [`libs/`](libs/AGENTS.md), reachable as `repo.libs.`. -6. **Search semantically.** This repo is indexed with - [`ccc`](https://github.com/cocoindex-io/cocoindex-code) — try - `ccc search '' --path '**'` before `grep` for - "where is X / which bundle does Y" questions. Without - `--path '**'`, results are filtered to the current working - directory's subtree. +6. **`ccc` is available for semantic search.** This repo is indexed + with [`ccc`](https://github.com/cocoindex-io/cocoindex-code). + Reach for it on conceptual questions ("where is X used / which + bundles do Y / what are the contexts of Z"), where a keyword + grep would miss indirect usage: + `ccc search '' --path '**'`. Pass `--path '**'` — + without it, results are filtered to the current working + directory's subtree. `grep`/`rg`/`find` remain fine for + exact-string lookups; pick whichever fits the question. ## Layout