@roarpeng/graphflow 1.7.0 → 1.7.5

package/src/surfaces/antigravity-rules/graphflow.md

@@ -19,8 +19,9 @@ Before code exploration, implementation, debugging, review, planning, or archite
 Code symbols are mostly English. For Chinese user questions:
 
 1. **Proactive:** Translate intent to English **file/class/component names** and pass **`englishQuery`** (e.g. `PoseDetectionPage`, `BattlePage`, `shieldEffect`). Avoid generic `exercise` when the user means UI/camera.
-2. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en`, answer the JSON prompt, then retry with `englishQuery`.
-3. Keep `query` as the original Chinese text.
+2. **Module families (store/slices):** Prefer file stems (`useGameStore companionSlice dailySlice`), not bare domain words like `monster` (often hits `data/monsters` instead of `monsterSlice`).
+3. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en`, answer the JSON prompt, then retry with `englishQuery`.
+4. Keep `query` as the original Chinese text.
 
 ```typescript
 graphflow_context({

package/src/surfaces/copilot-instructions/graphflow.md

@@ -46,8 +46,9 @@ Do **not** hardcode `GRAPHFLOW_WORKSPACE_ROOT` — let the MCP server detect the
 Code symbols are mostly English. For Chinese user questions:
 
 1. **Proactive:** Before or with `graphflow_context`, translate intent to English **file/class/component names** (e.g. `PoseDetectionPage`, `BattlePage`, `shieldEffect`) and pass `englishQuery`. Avoid generic terms like `exercise` when the user means UI/camera — they often match data/types layers.
-2. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en` (low `anchorCount`), answer the JSON prompt with your model, then retry preview with `englishQuery`.
-3. Keep `query` as the original Chinese text; use `englishQuery` for search terms only.
+2. **Module families (store/slices):** Prefer file stems (`useGameStore companionSlice dailySlice inventorySlice`), not bare domain words like `monster` (often hits `data/monsters` instead of `monsterSlice`).
+3. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en` (low `anchorCount`), answer the JSON prompt with your model, then retry preview with `englishQuery`.
+4. Keep `query` as the original Chinese text; use `englishQuery` for search terms only.
 
 ## High-frequency MCP tools
 

package/src/surfaces/cursor-rules/graphflow.mdc

@@ -32,8 +32,9 @@ Do not scan the whole repository, recursively inspect many files, or read large
 Code symbols are mostly English. For Chinese user questions:
 
 1. **Proactive:** Before or with `graphflow_context`, translate intent to English **file/class/component names** (e.g. `PoseDetectionPage`, `BattlePage`, `shieldEffect`) and pass `englishQuery`. Avoid generic terms like `exercise` when the user means UI/camera — they often match data/types layers.
-2. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en` (low `anchorCount`), answer the JSON prompt with your model, then retry preview with `englishQuery`.
-3. Keep `query` as the original Chinese text; use `englishQuery` for search terms only.
+2. **Module families (store/slices):** Prefer file stems (`useGameStore companionSlice dailySlice inventorySlice`), not bare domain words like `monster` (often hits `data/monsters` instead of `monsterSlice`).
+3. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en` (low `anchorCount`), answer the JSON prompt with your model, then retry preview with `englishQuery`.
+4. Keep `query` as the original Chinese text; use `englishQuery` for search terms only.
 
 ```typescript
 graphflow_context({

package/src/surfaces/trae-rules/graphflow.md

@@ -26,8 +26,9 @@ Before code exploration, implementation, debugging, review, planning, or archite
 Code symbols are mostly English. For Chinese user questions:
 
 1. **Proactive:** Translate intent to English **file/class/component names** and pass **`englishQuery`** (e.g. `PoseDetectionPage`, `BattlePage`, `shieldEffect`). Avoid generic `exercise` when the user means UI/camera.
-2. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en`, answer the JSON prompt, then retry with `englishQuery`.
-3. Keep `query` as the original Chinese text.
+2. **Module families (store/slices):** Prefer file stems (`useGameStore companionSlice dailySlice`), not bare domain words like `monster` (often hits `data/monsters` instead of `monsterSlice`).
+3. **Reactive:** If preview returns `agentWorkItems` with `query-translate-en`, answer the JSON prompt, then retry with `englishQuery`.
+4. Keep `query` as the original Chinese text.
 
 ```typescript
 graphflow_context({

package/src/surfaces/trae-skill/graphflow/SKILL.md

@@ -193,6 +193,8 @@ Step 3: Use summary + anchors
 
 Use **exact file/class/component names** (PascalCase stems). Avoid generic words like `exercise` when the user means camera/pose UI — that word often hits data/types layers instead of pages.
 
+For **module families** (Zustand store + `slices/`): put file stems in `englishQuery` (`useGameStore companionSlice dailySlice inventorySlice`), not bare domain words like `monster` (often ranks `data/monsters` over `monsterSlice`).
+
 **Fallback:** If `anchorCount < 3` and `agentWorkItems` includes `query-translate-en`, answer JSON prompt and retry with `englishQuery`.
 
 ---