Patch: Add Copilot instructions

[JCKING1278]

Patch:\n\n
From cb3c42e Mon Sep 17 00:00:00 2001
From: jck jck@syn-2603-8080-cb00-5100-c0de-0fee-ca5e-c1ae.search.charter.net
Date: Mon, 23 Mar 2026 15:57:04 -0500
Subject: [PATCH] Update Copilot instructions: document filesystem MCP servers
and usage

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

.github/copilot-instructions.md | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
index 8ba239f..465a053 100644
--- a/.github/copilot-instructions.md
+++ b/.github/copilot-instructions.md
@@ -79,7 +79,21 @@ After the front matter, add Markdown content for the store's main body text.

• Don't edit _site/: This is the build output and regenerates on each build
• URL base path: Always use {{ site.baseurl }} when linking assets or pages
• YAML fields in stores: Respect the existing front matter structure; add fields when needed, but maintain consistency across store pages
  -- Live reload: jekyll serve watches for file changes and rebuilds automatically
  +- Live reload: bundle exec jekyll serve --livereload --baseurl '/cloudfront' watches for changes and serves the site from /cloudfront
  +- Deployment branch & CI: Deploys on push to master via .github/workflows/jekyll.yml. CI uses Ruby 3.1 and runs bundle install then bundle exec jekyll build.
  +- Preview a single store page locally:

• 1. Run bundle exec jekyll serve --livereload --baseurl '/cloudfront'
• 2. Open http://localhost:4000/cloudfront/stores/<slug>/ (slug = filename without extension)
• For quicker iteration, use bundle exec jekyll build --incremental or bundle exec jekyll serve --incremental to rebuild only changed pages.

+- Adding a new store:

• 1. Create _stores/your-tool.md with front matter (see 'Creating New Store Pages' above)
• 2. Add any images to assets/images/ and reference them via image: filename.svg
• 3. Commit and push to master — GitHub Action will build and deploy

+- Content authoring notes (repo-specific):

• • Use name: (not title:) in store front matter — layouts use page.name
• • Keep front matter arrays (features, metrics, steps) as shown; the layout expects those keys

MCP Servers (Model Context Protocol)

@@ -99,3 +113,4 @@ The filesystem MCP server is configured to assist with content management ta

• Organizing content across knowledge.md, money.md, and store pages

The filesystem tools are pre-authorized for this project and require no additional setup.
+

2.53.0