implemented steps 1-5

docs/usage.md

@@ -9,7 +9,7 @@ icon: lucide/workflow
 This page explains practical usage mechanics for the GitHub Copilot extension in VS Code when `personal-mcp` is configured as an MCP server:
 
 1. explicit `/` command flows when you want deterministic control
-2. automatic skill context loading when relevance can be inferred
+2. guided skill loading when relevance can be inferred
 
 The goal is to show how Copilot behaves as a client and how to shape that behavior.
 
@@ -26,18 +26,17 @@ In this repository, skill guidance is exposed as MCP resources, not as server-ow
 
 ### What the server publishes
 
-`personal-mcp` mounts skill modules and a catalog module. The catalog exposes discovery resources:
+`personal-mcp` registers resources from the validated docs registry and exposes catalog discovery resources:
 
 1. `resource://catalog/skills_index`
-2. `resource://catalog/skills_details`
-3. `resource://catalog/patterns`
-4. `resource://catalog/patterns_by_id`
+2. `resource://catalog/skills/{skill_id}`
 
 Each skill publishes a canonical Markdown document resource:
 
 1. `resource://skills/<skill-id>/document`
+2. `resource://skills/<skill-id>/references/<ref-id>`
 
-The document payload is loaded from `docs/skills/<slug>/SKILL.md` and returned with metadata.
+The document payload is loaded from `docs/skills/<skill-id>/SKILL.md` and returned with metadata.
 
 ### What Copilot does as the client
 
@@ -177,8 +176,10 @@ When a task may match a documented implementation pattern from `personal-mcp`:
 
 Preferred resource order:
 
-1. `resource://catalog/skills_index` or `resource://catalog/patterns`
-2. `resource://skills/<skill-id>/document`
+1. `resource://catalog/skills_index`
+2. `resource://catalog/skills/{skill_id}`
+3. `resource://skills/<skill-id>/document`
+4. `resource://skills/<skill-id>/references/<ref-id>` when needed
 
 Preferred tool fallback order: