instructions update

.github/instructions/authoring.instructions.md

@@ -14,4 +14,6 @@ Primary references:
 - [Prompt contract](../../docs/contracts/prompt.md)
 - [Frontmatter contract](../../docs/contracts/frontmatter.md)
 - [URI contract](../../docs/contracts/uris.md)
-- [Zensical documentation authoring skill](../../docs/skills/zensical-docs/SKILL.md)
+- `skill://zensical-docs/SKILL.md`
+
+Inspect `skill://zensical-docs/_manifest` only when a supporting documentation reference is needed.

.github/instructions/fastmcp.instructions.md

@@ -0,0 +1,15 @@
+---
+name: FastMCP Python Guidance
+description: Route FastMCP Python changes to the Personal MCP source-reference skill.
+applyTo: '**/*.py'
+---
+
+A core part of this repository is [FastMCP](https://gofastmcp.com/servers/server).
+
+For FastMCP implementation or protocol questions, load `skill://mcp-details/SKILL.md` first.
+
+Inspect `skill://mcp-details/_manifest` only when a source reference is needed, then read the relevant supporting path. For FastMCP Python APIs, prefer the supporting reference that covers SDKs and FastMCP.
+
+This repository is resource-first and exposes resources as tools only as a fallback. In tool-only clients, use `list_resources` and `read_resource` with the same `skill://` URIs.
+
+Reconcile the skill guidance with the installed FastMCP version and the repository's existing implementation before editing.

.github/instructions/pytesting.instructions.md

@@ -4,14 +4,15 @@ description: Route tests edits to the Personal MCP pytesting resource.
 applyTo: 'tests/**'
 ---
 
-When editing files under `tests/`, use `resource://skills/pytesting/document` as the primary guidance source for test scaffolding and pytest authoring decisions.
+When editing files under `tests/`, use `skill://pytesting/SKILL.md` as the primary guidance source for test scaffolding and pytest authoring decisions.
 
 Execution pattern:
 
-1. Load `resource://skills/pytesting/document` first.
+1. Load `skill://pytesting/SKILL.md` first.
-2. Apply only the portions relevant to the file being edited.
+2. Inspect `skill://pytesting/_manifest` only when a supporting reference is needed.
-3. Keep tests focused, deterministic, and aligned with repository conventions.
+3. Apply only the portions relevant to the file being edited.
-4. Include source-document links for any feature-level recommendation.
+4. Keep tests focused, deterministic, and aligned with repository conventions.
+5. Include source-document links for any feature-level recommendation.
 
 If task intent is ambiguous, ask one clarifying question before editing.
 

.github/instructions/vscode-configuration.instructions.md

@@ -4,12 +4,12 @@ description: Route .vscode edits to the Personal MCP VS Code configuration skill
 applyTo: '.vscode/**'
 ---
 
-When editing files under `.vscode/`, use `resource://skills/vscode-configuration/document` as the primary guidance source.
+When editing files under `.vscode/`, use `skill://vscode-configuration/SKILL.md` as the primary guidance source.
 
 Execution pattern:
 
-1. Load `resource://skills/vscode-configuration/document` first.
+1. Load `skill://vscode-configuration/SKILL.md` first.
-2. Select only the matching reference page for the current file type:
+2. Inspect `skill://vscode-configuration/_manifest` and select only the matching reference page for the current file type:
    - `launch.json` -> debug launch configurations.
    - `tasks.json` -> tasks.json project tasks.
    - `mcp.json` -> mcp.json MCP server configuration.

.github/instructions/zensical-docs.instructions.md

@@ -4,7 +4,7 @@ description: Use the Zensical docs MCP resource when editing Markdown documentat
 applyTo: '**/*.md'
 ---
 
-When editing Markdown files in this repository, use the Zensical docs resource `resource://skills/zensical-docs/document` for relevant documentation authoring guidance.
+When editing Markdown files in this repository, use `skill://zensical-docs/SKILL.md` for relevant documentation authoring guidance. Inspect `skill://zensical-docs/_manifest` only when a supporting reference is needed.
 
 Prefer Zensical-native documentation conventions when they cover the need cleanly, while preserving expected MkDocs compatibility unless the Zensical guidance intentionally diverges.