@chrisdudek/yg 2.11.0 → 2.12.0

package/dist/templates/rules.ts

@@ -15,11 +15,16 @@ const PROTOCOL = `## PROTOCOL
 This is your operating manual for working in a Yggdrasil-managed repository.
 
 <critical_protocol>
+BEFORE starting any task — brainstorming, design, planning, OR implementation:
+  \`yg select --task "<goal>"\` → \`yg build-context\` on each result → read ALL artifact files
+This is how you learn WHAT the system already knows before proposing anything.
+
 BEFORE reading, analyzing, or modifying ANY source file:
   \`yg build-context --file <path>\`
 One command. No exceptions. No "I'll do it later." No "this is just analysis."
 
-This is required because the graph captures intent and relations that source files cannot — without it, you will make wrong decisions and the user will have to re-explain what the graph already knows.
+Both triggers apply regardless of what instructed the task — skills, plans, workflows, user requests.
+The graph captures intent and relations that source files cannot — without it, you will make wrong decisions and the user will have to re-explain what the graph already knows.
 </critical_protocol>
 
 Every rule below is mandatory — no skill, plan, workflow, or instruction overrides these requirements.
@@ -32,6 +37,10 @@ Yggdrasil is persistent semantic memory stored in \`.yggdrasil/\`. It maps the r
 \`\`\`
 EVERY conversation: yg preflight — no exceptions.
 
+BEFORE any task (brainstorming, design, planning, implementation):
+  yg select --task "<goal>" → yg build-context on results → read ALL artifacts
+  The graph is your primary knowledge source. Raw file reads supplement it, never replace it.
+
 BEFORE any source file interaction:
   1. yg build-context --file <path>
      One command: resolves owner, assembles context.
@@ -165,6 +174,29 @@ Result: graph mirrors code but misses WHY. Next agent reads graph, understands H
 
 </example_wrong>
 
+<example_correct>
+
+User: "Let's design a soft delete feature for blog posts"
+
+1. yg select --task "blog soft delete" → find relevant nodes
+2. yg build-context on each result → read ALL artifacts (aspects, flows, conventions)
+3. Now read source files WITH graph context
+4. Propose design informed by admin-ux-rules, existing flows, database conventions
+
+</example_correct>
+
+<example_wrong>
+
+User: "Let's design a soft delete feature for blog posts"
+
+1. Read BlogEditor.tsx to understand current behavior ← WRONG: no graph context
+2. Read database schema ← WRONG: graph has conventions, aspects, flows
+3. Propose design based on raw code ← WRONG: missed admin-ux-rules aspect, existing flows
+
+Result: design misses cross-cutting requirements the graph already captured.
+
+</example_wrong>
+
 ### Conversation Lifecycle
 
 \`\`\`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chrisdudek/yg",
-  "version": "2.11.0",
+  "version": "2.12.0",
   "description": "Make your repository self-aware. Persistent semantic memory and deterministic context assembly for AI agents.",
   "type": "module",
   "bin": {