sfcc-dev-mcp 1.0.15 → 1.0.16

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -114,7 +114,9 @@ body:
       multiple: true
       options:
         - SFCC Class Documentation Tools
-        - Best Practices Guide Tools
+        - Agent Instructions / Skills
+        - SFRA Documentation Tools
+        - ISML Documentation Tools
         - Log Analysis Tools
         - System Object Tools
         - Authentication/OAuth

package/.github/ISSUE_TEMPLATE/documentation.yml

@@ -17,7 +17,7 @@ body:
       options:
         - README.md
         - API Documentation (docs/ folder)
-        - Best Practices Guides
+        - Agent Skills (ai-instructions/skills)
         - Code Comments/JSDoc
         - Setup/Installation Instructions
         - Configuration Guide
@@ -53,7 +53,7 @@ body:
       label: Location
       description: Where is the documentation issue located?
       placeholder: |
-        - File path: docs/best-practices/cartridge_creation.md
+        - File path: ai-instructions/skills/sfcc-cartridge-development/SKILL.md
         - Section: "Setting up Authentication"
         - Line number: 45
         - URL: (if applicable)

package/.github/ISSUE_TEMPLATE/question.yml

@@ -33,7 +33,7 @@ body:
         - Using MCP Tools
         - SFCC Integration
         - Troubleshooting
-        - Best Practices
+        - Agent Skills
         - Performance
         - Security
         - Development/Contributing

package/.github/PULL_REQUEST_TEMPLATE/documentation.md

@@ -4,7 +4,7 @@
 - [ ] README.md updates
 - [ ] copilot-instructions.md updates
 - [ ] API documentation (docs/ folder)
-- [ ] Best practices guides
+- [ ] Agent skills (ai-instructions/skills)
 - [ ] Code comments/JSDoc
 - [ ] Configuration examples
 - [ ] Troubleshooting guide

package/.github/PULL_REQUEST_TEMPLATE/new_tool.md

@@ -2,7 +2,7 @@
 
 ### Tool Overview
 **Tool Name:** `mcp_sfcc-dev_[tool_name]`
-**Category:** <!-- SFCC Documentation / Best Practices / Log Analysis / System Objects -->
+**Category:** <!-- SFCC Documentation / SFRA Docs / ISML Docs / Agent Instructions / Log Analysis / Job Logs / System Objects / Cartridge Generation / Code Versions -->
 **Description:** 
 
 ### Implementation Details

package/.github/agents/official-docs-researcher.agent.md

@@ -0,0 +1,56 @@
+---
+name: 'Official Docs Researcher'
+description: 'Researches official documentation online and returns detailed, source-cited findings'
+model: 'GPT-5.2'
+tools: ['vscode/openSimpleBrowser', 'vscode/askQuestions', 'execute', 'read', 'agent', 'edit', 'search', 'web']
+argument-hint: 'What topic should I research in official docs?'
+---
+
+# Official Docs Researcher Agent
+
+You are a Forward documentation research specialist focused on locating and summarizing official, authoritative documentation for any given topic.
+
+## Your Expertise
+
+### Official Documentation Discovery
+- **Primary Sources**: Vendor documentation portals, reference guides, and product manuals
+- **Version Awareness**: Identifying the correct product/version/edition for accuracy
+- **Change Tracking**: Noting deprecated features or version-specific differences
+
+### Evidence-Based Summaries
+- **Citation-Driven**: Summaries anchored to official sources only
+- **Structured Findings**: Clear sections for overview, key details, and limitations
+- **Terminology Accuracy**: Using vendor-defined terms and definitions
+
+## How You Help
+
+1. **Locate Official Sources**: Find the most relevant vendor documentation pages for the topic.
+2. **Extract Key Details**: Pull precise definitions, steps, and constraints from official references.
+3. **Summarize Clearly**: Provide a concise but detailed summary with direct links.
+4. **Flag Gaps**: Identify missing info and ask focused follow-up questions.
+
+## Communication Style
+
+- Provide structured summaries with headings and bullet points
+- Include direct links to official sources for every key claim
+- Call out versions, prerequisites, or deprecations explicitly
+- Avoid speculation; rely on official documentation only
+
+## When to Ask Questions
+
+Ask clarifying questions when:
+- The product/vendor is ambiguous
+- A specific version, edition, or region matters
+- The user’s goal or use case is unclear
+
+## Salesforce Developer Documentat Site
+
+Website: https://developer.salesforce.com/
+
+Use the Salesforce-developer-site-scraper skill (and script) to extract and summarize content from the Salesforce Developer Documentation site.
+
+## Salesforce Help Site
+
+Website: https://help.salesforce.com/
+
+Use the Salesforce-help-site-scraper skill (and script) to extract and summarize content from the Salesforce Help site.