sfcc-dev-mcp 1.0.16 → 1.0.20

package/.github/skills/skill-authoring/references/PATTERNS.md

@@ -1,384 +0,0 @@
-# Skill Authoring Patterns
-
-Patterns and lessons learned from creating B2C Commerce skills.
-
-## Content Organization
-
-### Main SKILL.md Structure
-
-Effective skills follow this structure:
-
-```markdown
----
-name: skill-name
-description: One-line description
----
-
-# Skill Title
-
-Brief overview (2-3 sentences).
-
-## Overview / Quick Reference
-
-Tables or bullet points for quick scanning.
-
-## Core Concepts
-
-Key information the user needs to understand.
-
-## Patterns / How To
-
-Step-by-step instructions with examples.
-
-## Examples
-
-Complete, runnable examples.
-
-## Detailed References
-
-Links to reference files for deep dives.
-
-## Script API Classes (if applicable)
-
-Table of relevant classes/methods.
-```
-
-### Reference File Structure
-
-Reference files should be focused on one topic:
-
-```markdown
-# Topic Reference
-
-Brief intro.
-
-## Subtopic A
-
-Details with examples.
-
-## Subtopic B
-
-Details with examples.
-
-## Complete Example
-
-Full working example if applicable.
-```
-
-## Effective Tables
-
-Tables provide quick reference without consuming much context:
-
-### Command Reference Table
-
-```markdown
-| Command | Description |
-|---------|-------------|
-| `b2c cmd1` | Does X |
-| `b2c cmd2` | Does Y |
-```
-
-### Parameter Table
-
-```markdown
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `name` | string | Yes | The item name |
-| `count` | int | No | Number of items |
-```
-
-### Feature Matrix Table
-
-```markdown
-| Feature | Supported | Notes |
-|---------|-----------|-------|
-| Feature A | Yes | Full support |
-| Feature B | Partial | Only in v2+ |
-| Feature C | No | Use workaround |
-```
-
-## Code Examples
-
-### Inline Code
-
-For short snippets, use inline code:
-
-```markdown
-Use `Logger.getLogger('category')` to get a logger instance.
-```
-
-### Code Blocks
-
-For complete examples, use fenced code blocks with language:
-
-````markdown
-```javascript
-var Logger = require('dw/system/Logger');
-var log = Logger.getLogger('checkout');
-log.info('Order {0} placed', orderNo);
-```
-````
-
-### Multi-file Examples
-
-When showing related files, use headers:
-
-````markdown
-**package.json:**
-```json
-{ "name": "my-package" }
-```
-
-**index.js:**
-```javascript
-module.exports = function() {};
-```
-````
-
-## XML Examples
-
-When documenting XML formats:
-
-1. **Always validate against XSD schemas** if available
-2. **Show namespace declarations** in first example
-3. **Use realistic but simple data**
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<root xmlns="http://example.com/schema/2024">
-    <element attribute="value">content</element>
-</root>
-```
-
-## Referencing Official Documentation
-
-### When to Reference
-
-- API details that may change
-- Complete specification documents
-- Platform-specific configurations
-
-### How to Reference
-
-```markdown
-For complete API documentation, see the [Official Guide](https://docs.example.com).
-
-The `Logger` class is documented in the [Script API Reference](https://docs.example.com/api/Logger).
-```
-
-### When to Inline
-
-- Frequently used patterns
-- Information not easily found in docs
-- Synthesized knowledge from multiple sources
-
-## Progressive Complexity
-
-Structure content from simple to complex:
-
-### Basic Pattern First
-
-```markdown
-## Basic Usage
-
-```javascript
-Logger.info('Simple message');
-```
-```
-
-### Then Add Complexity
-
-```markdown
-## With Parameters
-
-```javascript
-Logger.info('Order {0} for customer {1}', orderNo, customerId);
-```
-```
-
-### Finally Show Advanced Cases
-
-```markdown
-## Custom Log Files
-
-```javascript
-var log = Logger.getLogger('prefix', 'category');
-log.info('Goes to custom-prefix-*.log');
-```
-```
-
-## Common Skill Patterns
-
-### CLI Command Skill
-
-```markdown
----
-name: tool-command
-description: Guide for using the tool command
----
-
-# Tool Command
-
-Brief description of what the command does.
-
-## Quick Reference
-
-| Command | Description |
-|---------|-------------|
-| `tool cmd1` | Does X |
-| `tool cmd2` | Does Y |
-
-## Examples
-
-### Basic Usage
-
-\`\`\`bash
-tool command --flag value
-\`\`\`
-
-### Common Workflows
-
-\`\`\`bash
-# Workflow description
-tool step1
-tool step2
-\`\`\`
-```
-
-### API/Framework Skill
-
-```markdown
----
-name: framework-feature
-description: Guide for implementing feature with framework
----
-
-# Feature Name
-
-Overview of the feature and when to use it.
-
-## Core Concepts
-
-| Concept | Description |
-|---------|-------------|
-| Concept A | What it is |
-| Concept B | What it is |
-
-## Basic Pattern
-
-\`\`\`javascript
-// Basic implementation
-\`\`\`
-
-## Configuration
-
-| Setting | Default | Description |
-|---------|---------|-------------|
-| setting1 | value | What it does |
-
-## Detailed References
-
-- [Advanced Patterns](references/ADVANCED.md)
-- [Configuration Options](references/CONFIG.md)
-```
-
-### XML/Configuration Skill
-
-```markdown
----
-name: config-format
-description: Guide for XML/config file format
----
-
-# Configuration Format
-
-Overview of the configuration file.
-
-## File Structure
-
-\`\`\`
-project/
-├── config/
-│   └── settings.xml
-└── data/
-    └── values.xml
-\`\`\`
-
-## XML Schema
-
-\`\`\`xml
-<?xml version="1.0" encoding="UTF-8"?>
-<root xmlns="http://example.com/schema">
-    <!-- elements -->
-</root>
-\`\`\`
-
-## Element Reference
-
-| Element | Required | Description |
-|---------|----------|-------------|
-| `<elem1>` | Yes | Purpose |
-| `<elem2>` | No | Purpose |
-
-## Complete Example
-
-[Full example with realistic data]
-```
-
-## Skill Maintenance
-
-### Version Control
-
-- Keep skills in version control with the codebase
-- Update skills when features change
-- Review skills during code reviews
-
-### Testing Skills
-
-- Manually test instructions work as documented
-- Validate XML examples against schemas
-- Verify links to references work
-
-### Updating Skills
-
-When updating:
-1. Check if existing content is still accurate
-2. Add new content in appropriate section
-3. Update examples if APIs changed
-4. Verify reference links still work
-
-## Anti-Patterns to Avoid
-
-### Too Much Content in SKILL.md
-
-**Bad:** 2000+ line SKILL.md with everything inlined
-
-**Good:** < 500 line SKILL.md with references for details
-
-### Missing Context
-
-**Bad:**
-```markdown
-Use `cmd --flag` to do the thing.
-```
-
-**Good:**
-```markdown
-Use `cmd --flag` to enable feature X, which allows Y:
-
-\`\`\`bash
-cmd --flag value
-\`\`\`
-```
-
-### Outdated Examples
-
-**Bad:** Examples using deprecated APIs or old syntax
-
-**Good:** Examples validated against current documentation/schemas
-
-### Deeply Nested References
-
-**Bad:** SKILL.md → ref1.md → ref2.md → ref3.md
-
-**Good:** SKILL.md → ref1.md (one level deep)

package/.github/workflows/ci.yml

@@ -1,103 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches: [ main, develop ]
-  pull_request:
-    branches: [ main, develop ]
-
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v6
-
-    - name: Setup Node.js
-      uses: actions/setup-node@v5
-      with:
-        node-version: '20'
-        cache: 'npm'
-
-    - name: Install dependencies
-      run: npm ci
-
-    - name: Run linting
-      run: npm run lint:check
-
-  security:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      security-events: write
-
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v6
-
-    - name: Setup Node.js
-      uses: actions/setup-node@v5
-      with:
-        node-version: '20'
-        cache: 'npm'
-
-    - name: Install dependencies
-      run: npm ci
-
-    - name: Run security audit
-      run: npm audit --audit-level=moderate
-
-  test:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-
-    strategy:
-      matrix:
-        node-version: [18, 20, 22, 24]
-
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v6
-
-    - name: Setup Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v5
-      with:
-        node-version: ${{ matrix.node-version }}
-        cache: 'npm'
-
-    - name: Install dependencies
-      run: npm ci
-
-    - name: Run build
-      run: npm run build
-
-    - name: Setup SFCC mock server
-      run: |
-        cd tests/servers/sfcc-mock-server
-        npm install
-        npm run setup:logs
-        node server.js --port 3000 &
-        sleep 5
-
-    - name: Run tests
-      run: npm test
-
-    - name: Stop SFCC mock server
-      if: always()
-      run: |
-        # Kill SFCC mock server process
-        pkill -f "node.*server.js" || true
-        # Fallback: kill any remaining server processes on port 3000
-        lsof -ti :3000 | xargs kill -9 2>/dev/null || true
-
-    - name: Upload coverage reports (Node.js 20 only)
-      if: matrix.node-version == 20
-      uses: codecov/codecov-action@5a1091511ad55cbe89839c7260b706298ca349f7 # v3
-      with:
-        fail_ci_if_error: false
-        verbose: true
-        files: ./coverage/lcov.info

package/.github/workflows/deploy-pages.yml

@@ -1,59 +0,0 @@
-name: Deploy Docs (VitePress)
-
-on:
-  push:
-    branches: [ main ]
-    paths:
-      - 'docs-site-v2/**'
-      - '.github/workflows/deploy-pages.yml'
-  pull_request:
-    branches: [ main ]
-    paths:
-      - 'docs-site-v2/**'
-  workflow_dispatch:
-
-permissions:
-  contents: read
-  pages: write
-  id-token: write
-
-concurrency:
-  group: "pages"
-  cancel-in-progress: false
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v6
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v5
-        with:
-          node-version: '18'
-
-      - name: Install docs dependencies
-        run: npm --prefix docs-site-v2 install
-
-      - name: Build docs
-        run: npm --prefix docs-site-v2 run build
-
-      - name: Setup Pages
-        uses: actions/configure-pages@v5
-
-      - name: Upload artifact
-        uses: actions/upload-pages-artifact@v4
-        with:
-          path: ./docs-site-v2/.vitepress/dist
-
-  deploy:
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    runs-on: ubuntu-latest
-    needs: build
-    steps:
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v4

package/.github/workflows/publish.yml

@@ -1,112 +0,0 @@
-name: Publish to NPM
-
-on:
-  release:
-    types: [published]
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      id-token: write
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          fetch-depth: 0
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v5
-        with:
-          node-version: '20'
-          registry-url: 'https://registry.npmjs.org'
-          cache: 'npm'
-
-      - name: Configure Git
-        run: |
-          git config --global user.name "github-actions[bot]"
-          git config --global user.email "github-actions[bot]@users.noreply.github.com"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Build project
-        run: npm run build
-
-      - name: Setup SFCC mock server
-        run: |
-          cd tests/servers/sfcc-mock-server
-          npm install
-          npm run setup:logs
-          node server.js --port 3000 &
-          sleep 5
-
-      - name: Run tests
-        run: npm test
-
-      - name: Run linting
-        run: npm run lint:check
-
-      - name: Final build for publishing
-        run: npm run build
-
-      - name: Extract version and create release branch
-        run: |
-          # Extract version from the release tag (remove 'v' prefix if present)
-          VERSION=${GITHUB_REF#refs/tags/}
-          VERSION=${VERSION#v}
-          echo "Setting package version to: $VERSION"
-          
-          # Create and switch to release branch
-          BRANCH_NAME="release/v$VERSION"
-          echo "Creating release branch: $BRANCH_NAME"
-          git checkout -b $BRANCH_NAME
-
-          # Update package version
-          npm version $VERSION --no-git-tag-version
-
-          # Commit the version update
-          git add package.json package-lock.json
-          git commit -m "chore: bump version to $VERSION for release"
-
-          # Push the release branch
-          git push origin $BRANCH_NAME
-
-      - name: Stop SFCC mock server
-        if: always()
-        run: |
-          # Kill SFCC mock server process
-          pkill -f "node.*server.js" || true
-          # Fallback: kill any remaining server processes on port 3000
-          lsof -ti :3000 | xargs kill -9 2>/dev/null || true
-
-      - name: Publish to NPM
-        run: npm publish
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-      - name: Install MCP Publisher
-        run: |
-          curl -L "https://github.com/modelcontextprotocol/registry/releases/download/latest/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
-
-      - name: Update server.json version
-        run: |
-          # Extract version from the release tag (remove 'v' prefix if present)
-          VERSION=${GITHUB_REF#refs/tags/}
-          VERSION=${VERSION#v}
-          echo "Updating server.json version to: $VERSION"
-          
-          # Update server.json version to match the release
-          jq --arg v "$VERSION" '.version = $v | .packages[0].version = $v' server.json > tmp && mv tmp server.json
-
-      - name: Validate server.json
-        run: npm run validate:server-json
-
-      - name: Login to MCP Registry
-        run: ./mcp-publisher login github-oidc
-
-      - name: Publish to MCP Registry
-        run: ./mcp-publisher publish