From 0638fe2fd7c240cf0d8d90efbc4c5b0b1b8abdf0 Mon Sep 17 00:00:00 2001 From: John Lancaster <32917998+jsl12@users.noreply.github.com> Date: Thu, 27 Aug 2026 18:54:49 -0500 Subject: [PATCH] instructions update --- .github/copilot-instructions.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index a798895..897ab89 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -3,12 +3,15 @@ This repository is resource-first. - Canonical skill guidance lives in `docs/skills//SKILL.md`. -- The machine-facing skill contract is FastMCP's native `skill://` resource family. +- Skills are exposed through FastMCP's native `skill://` resource family. +- Prompts are exposed through native MCP prompt operations (`prompts/list`, `prompts/get`). +- General documentation pages are exposed through `resource://docs/{path*}`. +- The server intentionally does not provide compatibility tool projections for resources or prompts. When a task appears to match a documented implementation pattern in `personal-mcp`, use this sequence: 1. Prefer an already attached native skill resource. -2. Otherwise browse native MCP resources and compare `skill:///SKILL.md` descriptions. +2. Otherwise browse native MCP resources and compare available `skill:///SKILL.md` descriptions. 3. Read the best matching main skill file, or at most 2 candidate main files. 4. Read `skill:///_manifest` only when supporting material may be useful. 5. Fetch only the relevant supporting paths from that manifest. @@ -29,7 +32,7 @@ Selection rules: Repository-specific guidance: - For tasks about adding or modifying a skill, use `skill://copilot-customization/SKILL.md` when relevant. -- Keep skills provider-native; do not add custom skill catalogs, per-skill resource modules, or skill-specific discovery tools. +- Keep skills provider-native; do not add tool projections for resource or prompt access. ## Python Checks @@ -37,7 +40,7 @@ Repository-specific guidance: After changes run these commands to confirm functionality. Resolve any errors ```python -uv run ruff check +uv run ruff check . ``` ```python