@chrisdudek/yg 2.1.0 → 2.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/bin.js +6 -0
- package/dist/bin.js.map +1 -1
- package/dist/templates/rules.ts +6 -0
- package/package.json +1 -1
package/dist/templates/rules.ts
CHANGED
|
@@ -25,6 +25,11 @@ Yggdrasil is persistent semantic memory stored in \`.yggdrasil/\`. It maps the r
|
|
|
25
25
|
|
|
26
26
|
\`\`\`
|
|
27
27
|
BEFORE reading, researching, planning, OR modifying ANY mapped file:
|
|
28
|
+
0. Don't know which file or node to start from? If a semantic search
|
|
29
|
+
tool is available, search for your intent — the graph contains
|
|
30
|
+
responsibility, flow, and aspect files with rich natural-language
|
|
31
|
+
descriptions that match goal-oriented queries. Use the results
|
|
32
|
+
to identify relevant nodes, then proceed to step 1.
|
|
28
33
|
1. yg owner --file <path>
|
|
29
34
|
2. Choose the right graph tool for your task:
|
|
30
35
|
- Understanding how/why it works → yg build-context --node <owner>
|
|
@@ -99,6 +104,7 @@ What matters is the ACTION you are performing, not what instructed it. If the ac
|
|
|
99
104
|
| "I'm brainstorming, not implementing" | Brainstorming about mapped code needs graph context |
|
|
100
105
|
| "I'm only grepping for references" | Grep finds text; yg impact finds structural dependencies. Use both. |
|
|
101
106
|
| "I'll use the graph later when I modify" | Graph-first means BEFORE reading, not before modifying |
|
|
107
|
+
| "I'll grep the codebase to find where to start" | If semantic search is available, search by intent first — graph files are designed to match natural-language goals. Then \`yg owner\` on results. |
|
|
102
108
|
|
|
103
109
|
### Failure States
|
|
104
110
|
|