@precisionutilityguild/liquid-shadow 1.0.6 → 1.0.7

package/dist/skills/shadow_sync/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sync
-description: Sync index and mission state after external changes. Day-to-day: index + NanoRepair run automatically when MCP tools (search, inspect, etc.) trigger reindex. Use trace after git pull/checkout/merge (or rely on hooks); use index deep:true for full rebuild.
+description: 'Sync index and mission state after external changes. Day-to-day: index + NanoRepair run automatically when MCP tools (search, inspect, etc.) trigger reindex. Use trace after git pull/checkout/merge (or rely on hooks); use index deep:true for full rebuild.'
 ---
 
 # Repository Synchronization

package/dist/web-manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.6",
+  "version": "1.0.7",
   "toolsByPrefix": {
     "RECON": {
       "subcommands": [
@@ -86,63 +86,63 @@
   "skills": [
     {
       "slug": "shadow_audit",
-      "name": "SHADOW_AUDIT",
-      "description": "name: audit"
+      "name": "AUDIT",
+      "description": "Perform codebase health audits to identify dead code, circular dependencies, and technical debt. Use when auditing code quality, finding unused code, detecting circular dependencies, or when the user asks about codebase health, technical debt, or code cleanup."
     },
     {
       "slug": "shadow_chronicle",
-      "name": "SHADOW_CHRONICLE",
-      "description": "name: chronicle"
+      "name": "CHRONICLE",
+      "description": "Retrieve and analyze the repository's narrative archive as recorded in Git-native memory. Use when you need to understand historical decisions, catch up on repository progress, review recently completed missions, or when the user asks for a project history, changelog, or chronological overview of architectural changes."
     },
     {
       "slug": "shadow_continue",
-      "name": "SHADOW_CONTINUE",
-      "description": "name: continue"
+      "name": "CONTINUE",
+      "description": "Get briefing, pick one mission from next_work_candidates, then work that mission to completion with all remaining steps in one run. Use when continuing work on missions, executing mission steps, or when the user asks to continue work, finish a mission, or proceed with development tasks."
     },
     {
       "slug": "shadow_crystallize",
-      "name": "SHADOW_CRYSTALLIZE",
-      "description": "name: crystallize"
+      "name": "CRYSTALLIZE",
+      "description": "Compress a mission's intent logs into a dense crystal summary for token-efficient briefings. Use when a mission has accumulated many raw logs, when briefings are too verbose, or when the user asks about log compression, crystallization, or context reduction."
     },
     {
       "slug": "shadow_mission",
-      "name": "SHADOW_MISSION",
-      "description": "name: mission"
+      "name": "MISSION",
+      "description": "Define the objective, strategy, and success criteria for a new development mission. Use when planning strategic initiatives, creating missions, setting up development goals, or when the user asks about mission planning, strategic alignment, or outcome contracts."
     },
     {
       "slug": "shadow_onboard",
-      "name": "SHADOW_ONBOARD",
-      "description": "name: onboard"
+      "name": "ONBOARD",
+      "description": "Initialize and analyze a new repository for deep intelligence by building semantic index, syncing state, activating git hooks, and establishing missions. Use when onboarding to a new repository, initializing Shadow Engine, setting up git hooks, or when the user asks about repository setup, initialization, or first-time configuration."
     },
     {
       "slug": "shadow_research",
-      "name": "SHADOW_RESEARCH",
-      "description": "name: research"
+      "name": "RESEARCH",
+      "description": "Conduct high-signal research for external dependencies by combining local context, web search, and Context7 documentation. Use when researching libraries, checking integration examples, verifying versions, or when the user asks about external dependencies, library documentation, or integration patterns."
     },
     {
       "slug": "shadow_sync",
-      "name": "SHADOW_SYNC",
-      "description": "name: sync"
+      "name": "SYNC",
+      "description": "Sync index and mission state after external changes. Day-to-day: index + NanoRepair run automatically when MCP tools (search, inspect, etc.) trigger reindex. Use trace after git pull/checkout/merge (or rely on hooks); use index deep:true for full rebuild."
     },
     {
       "slug": "shadow_synthesize",
-      "name": "SHADOW_SYNTHESIZE",
-      "description": "name: synthesize"
+      "name": "SYNTHESIZE",
+      "description": "Distill mission logs into Architectural Decision Records (ADRs) and persist them to the Shadow Engine and Git Notes. Use when completing missions, creating ADRs, synthesizing architectural decisions, or when the user asks about decision records, mission completion, or architectural documentation."
     },
     {
       "slug": "shadow_trace_impact",
-      "name": "SHADOW_TRACE_IMPACT",
-      "description": "name: trace-impact"
+      "name": "TRACE-IMPACT",
+      "description": "Map the blast radius of a change by analyzing impact, flow traces, cross-repo dependencies, and boundary maps. Use when analyzing change impact, assessing risk, tracing dependencies, or when the user asks about change impact, blast radius, or dependency analysis."
     },
     {
       "slug": "shadow_understand",
-      "name": "SHADOW_UNDERSTAND",
-      "description": "name: understand"
+      "name": "UNDERSTAND",
+      "description": "Find the high-signal path to understanding complex logic through intent retrieval, topological placement, relational analysis, and mechanics inspection. Use when understanding architecture, analyzing complex code, tracing logic flow, or when the user asks about how something works, architectural patterns, or code comprehension."
     },
     {
       "slug": "shadow_workspace",
-      "name": "SHADOW_WORKSPACE",
-      "description": "name: workspace"
+      "name": "WORKSPACE",
+      "description": "Manage multi-repository workspaces and cross-repo mission links using the Shadow Engine. Use when working with multiple repositories, federated search across repos, linking missions across repos, or when the user asks about workspace management, multi-repo workflows, or cross-repository dependencies."
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@precisionutilityguild/liquid-shadow",
-  "version": "1.0.6",
+  "version": "1.0.7",
   "description": "Tactical Repository Intelligence Operative - Liquid Shadow Ecosystem",
   "homepage": "https://liquidshadow.pugcorp.online/",
   "repository": {

package/skills/shadow_sync/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sync
-description: Sync index and mission state after external changes. Day-to-day: index + NanoRepair run automatically when MCP tools (search, inspect, etc.) trigger reindex. Use trace after git pull/checkout/merge (or rely on hooks); use index deep:true for full rebuild.
+description: 'Sync index and mission state after external changes. Day-to-day: index + NanoRepair run automatically when MCP tools (search, inspect, etc.) trigger reindex. Use trace after git pull/checkout/merge (or rely on hooks); use index deep:true for full rebuild.'
 ---
 
 # Repository Synchronization