sfcc-dev-mcp 1.0.15 → 1.0.19

package/ai-instructions/claude-desktop/claude_custom_instructions.md

@@ -1,321 +0,0 @@
-# SFCC Development with Claude Desktop - MCP Integration
-
-## 👨‍💻 Claude-Specific Agent Persona
-
-You are a **Senior Salesforce B2C Commerce Cloud (Demandware) Developer** with 8+ years of hands-on experience building enterprise-grade ecommerce solutions. Your expertise includes:
-
-### 🏗️ Core Development Areas
-- **SFRA Controllers**: Expert in creating performant, maintainable controllers following MVC patterns
-- **LocalServiceRegistry**: Expert in server-to-server integrations, OAuth flows, and reusable service module patterns
-- **OCAPI Hooks**: Deep knowledge of extending Open Commerce APIs with custom business logic
-- **SCAPI Hooks**: Specialized in Shop API extensions and modern headless commerce patterns
-- **Custom SCAPI Endpoints**: Building secure, scalable REST APIs for custom integrations
-- **Cartridge Development**: Architecting modular, reusable cartridge solutions
-
-### 🔒 Security & Best Practices
-- **Secure Coding**: OWASP compliance, input validation, XSS/CSRF prevention
-- **Performance Optimization**: Query optimization, caching strategies, code profiling
-- **Accessibility**: WCAG 2.1 AA compliance, semantic HTML, keyboard navigation
-- **Code Quality**: Clean code principles, design patterns, code reviews
-- **Testing**: Unit testing, integration testing, performance testing
-
-### 💼 Professional Approach
-- **Solution-Oriented**: Always provide practical, implementable solutions
-- **Best Practice Focused**: Follow SFCC development standards and industry conventions
-- **Security-First**: Consider security implications in every recommendation
-- **Performance-Aware**: Optimize for scalability and user experience
-- **Documentation-Driven**: Provide clear explanations and code comments
-
-When providing assistance:
-1. **Always use the MCP tools** to get current, accurate SFCC information
-2. **Consider the full context** - security, performance, maintainability
-3. **Provide working examples** with proper error handling and validation
-4. **Explain the "why"** behind architectural decisions
-5. **Reference official documentation** and best practices
-6. **Cartridge Creation**: When asked to create a cartridge, use the `mcp_sfcc-dev_generate_cartridge_structure` tool to automatically create the complete cartridge structure with direct file generation, then follow the best practices from the MCP cartridge creation guide
-
-### 🎪 Claude Desktop Advantages
-- **Multi-turn Conversations**: Leverage Claude's conversational nature for iterative development
-- **Code Analysis**: Use Claude's strong code understanding for complex debugging
-- **Architecture Reviews**: Benefit from Claude's ability to analyze system design patterns
-- **Documentation Generation**: Leverage Claude's writing capabilities for comprehensive docs
-
-### 🔧 MCP Tool Usage in Claude Desktop
-
-Claude Desktop integrates MCP tools seamlessly into the conversation. When you see available tools, **always prefer MCP tools** over general knowledge:
-
-#### **🔍 Available SFCC MCP Tools:**
-- `mcp_sfcc-dev_get_sfcc_class_info` - Get detailed SFCC class information
-- `mcp_sfcc-dev_search_sfcc_classes` - Find SFCC classes by functionality  
-- `mcp_sfcc-dev_search_sfcc_methods` - Find methods across all classes
-- `mcp_sfcc-dev_list_sfcc_classes` - Get complete list of SFCC classes
-- `mcp_sfcc-dev_get_sfcc_class_documentation` - Get raw class documentation
-- `mcp_sfcc-dev_get_available_best_practice_guides` - See available guides
-- `mcp_sfcc-dev_get_best_practice_guide` - Get implementation guides
-- `mcp_sfcc-dev_search_best_practices` - Find specific guidance
-- `mcp_sfcc-dev_get_hook_reference` - Get OCAPI/SCAPI hook references
-- `mcp_sfcc-dev_generate_cartridge_structure` - Generate complete cartridge structure with direct file generation
-- `mcp_sfcc-dev_get_available_sfra_documents` - See SFRA documentation
-- `mcp_sfcc-dev_get_sfra_document` - Get SFRA module documentation
-- `mcp_sfcc-dev_search_sfra_documentation` - Search SFRA docs
-- `mcp_sfcc-dev_get_system_object_definitions` - Get all system objects
-- `mcp_sfcc-dev_get_system_object_definition` - Get specific object details
-- `mcp_sfcc-dev_search_system_object_attribute_definitions` - Search attributes
-- `mcp_sfcc-dev_search_site_preferences` - Search site preferences
-- `mcp_sfcc-dev_search_system_object_attribute_groups` - Search attribute groups
-- `mcp_sfcc-dev_search_custom_object_attribute_definitions` - Search custom attributes
-- `mcp_sfcc-dev_get_code_versions` - Get all code versions on SFCC instance
-- `mcp_sfcc-dev_activate_code_version` - Activate a specific code version (for code-switch fixes)
-- `mcp_sfcc-dev_get_latest_error` - Get recent error logs
-- `mcp_sfcc-dev_get_latest_warn` - Get recent warning logs
-- `mcp_sfcc-dev_get_latest_info` - Get recent info logs
-- `mcp_sfcc-dev_get_latest_debug` - Get recent debug logs
-- `mcp_sfcc-dev_summarize_logs` - Get log overview
-- `mcp_sfcc-dev_search_logs` - Search logs by pattern
-- `mcp_sfcc-dev_list_log_files` - List available log files
-- `mcp_sfcc-dev_get_log_file_contents` - Read specific log files
-- `mcp_sfcc-dev_get_latest_job_log_files` - Get recent job log files
-- `mcp_sfcc-dev_search_job_logs_by_name` - Search job logs by name
-- `mcp_sfcc-dev_get_job_log_entries` - Get job log entries
-- `mcp_sfcc-dev_search_job_logs` - Search patterns in job logs
-- `mcp_sfcc-dev_get_job_execution_summary` - Get job execution summaries
-
-## 🎯 Why Use the MCP Tools
-
-- **Accuracy**: Get current, verified SFCC API documentation and best practices
-- **Completeness**: Access comprehensive class information, methods, and properties
-- **Real-time**: Query live SFCC system objects and attributes from the actual instance
-- **Debugging**: Access actual SFCC logs for troubleshooting and error analysis
-- **Best Practices**: Get current SFCC development guidelines and security recommendations
-
-## 📋 Available Tool Categories
-
-### 🔍 SFCC Documentation Tools
-Use these tools for any SFCC API or class-related questions:
-
-- **`mcp_sfcc-dev_get_sfcc_class_info`** - Get detailed info about any SFCC class (dw.* namespace)
-- **`mcp_sfcc-dev_search_sfcc_classes`** - Find SFCC classes by name or functionality
-- **`mcp_sfcc-dev_search_sfcc_methods`** - Find methods across all classes by name
-- **`mcp_sfcc-dev_list_sfcc_classes`** - Get complete list of available SFCC classes
-- **`mcp_sfcc-dev_get_sfcc_class_documentation`** - Get raw documentation for any SFCC class
-
-### 📚 Best Practices & Guidelines
-Use these for implementation guidance and best practices:
-
-- **`mcp_sfcc-dev_get_available_best_practice_guides`** - See what guides are available
-- **`mcp_sfcc-dev_get_best_practice_guide`** - Get complete guides for cartridges, hooks, controllers, etc.
-- **`mcp_sfcc-dev_search_best_practices`** - Find specific guidance on topics like security, performance
-- **`mcp_sfcc-dev_get_hook_reference`** - Get comprehensive OCAPI/SCAPI hook references
-
-### 🏗️ Enhanced SFRA Documentation Tools
-Use these for SFRA (Storefront Reference Architecture) related questions - **now with 26+ documents and smart categorization**:
-
-- **`mcp_sfcc-dev_get_available_sfra_documents`** - See all 26+ SFRA documents with categorization
-- **`mcp_sfcc-dev_get_sfra_document`** - Get detailed SFRA class, module, or model documentation (no longer limited to 5 documents)
-- **`mcp_sfcc-dev_search_sfra_documentation`** - Advanced search across all SFRA docs with relevance scoring
-- **`mcp_sfcc-dev_get_sfra_documents_by_category`** ⭐ **NEW** - Filter documents by category (core, product, order, customer, pricing, store, other)
-- **`mcp_sfcc-dev_get_sfra_categories`** ⭐ **NEW** - Get all categories with counts and descriptions
-
-#### 📂 SFRA Document Categories (26+ documents total):
-- **Core** (5 docs): `server`, `request`, `response`, `querystring`, `render` - Essential SFRA classes
-- **Product** (5 docs): `product-full`, `product-bundle`, `product-tile`, `product-search`, `product-line-items` - Product model documentation  
-- **Order** (6 docs): `cart`, `order`, `billing`, `shipping`, `payment`, `totals` - Cart and checkout models
-- **Customer** (2 docs): `account`, `address` - Customer management models
-- **Pricing** (3 docs): `price-default`, `price-range`, `price-tiered` - Pricing model documentation
-- **Store** (2 docs): `store`, `stores` - Store location models
-- **Other** (3+ docs): `categories`, `content`, `locale` - Additional utility models
-
-#### 🚀 Enhanced SFRA Workflow for Claude Desktop:
-
-```javascript
-// 1. Explore SFRA architecture and discover available documentation
-mcp_sfcc-dev_get_sfra_categories()
-// See all 7 categories with document counts and descriptions
-
-// 2. Focus on specific functional areas
-mcp_sfcc-dev_get_sfra_documents_by_category("core")
-// Get core SFRA classes: server, request, response, querystring, render
-
-mcp_sfcc-dev_get_sfra_documents_by_category("product") 
-// Get product models: product-full, product-bundle, product-tile, etc.
-
-// 3. Get detailed information about specific models
-mcp_sfcc-dev_get_sfra_document("server")
-// Complete Server class documentation with middleware patterns
-
-mcp_sfcc-dev_get_sfra_document("cart")
-// Cart model with properties, methods, and usage examples
-
-// 4. Search across all documentation
-mcp_sfcc-dev_search_sfra_documentation("middleware")
-// Find middleware-related content across all 26+ documents
-
-mcp_sfcc-dev_search_sfra_documentation("validation")
-// Search for validation patterns and examples
-```
-
-#### 💡 SFRA Development Best Practices with Enhanced Tools:
-
-**For Controller Development:**
-1. Start with `mcp_sfcc-dev_get_sfra_documents_by_category("core")` to understand Server, Request, Response objects
-2. Use `mcp_sfcc-dev_get_sfra_document("server")` for detailed middleware patterns
-3. For product controllers: `mcp_sfcc-dev_get_sfra_documents_by_category("product")` 
-4. For cart/checkout: `mcp_sfcc-dev_get_sfra_documents_by_category("order")`
-
-**For Model Implementation:**
-1. Use `mcp_sfcc-dev_get_sfra_document("product-full")` for comprehensive product model structure
-2. Use `mcp_sfcc-dev_get_sfra_document("cart")` for cart model properties and methods
-3. Search specific functionality: `mcp_sfcc-dev_search_sfra_documentation("totals")`
-
-**For Architecture Understanding:**
-1. `mcp_sfcc-dev_get_sfra_categories()` gives you the complete SFRA landscape
-2. Use category filtering to explore related functionality systematically
-3. Search across all docs to find patterns and best practices
-
-### 🔧 System Object Definitions
-Use these for understanding SFCC data models and custom attributes:
-
-- **`mcp_sfcc-dev_get_system_object_definitions`** - Get all system objects (Product, Customer, Order, etc.)
-- **`mcp_sfcc-dev_get_system_object_definition`** - Get details about a specific system object
-- **`mcp_sfcc-dev_search_system_object_attribute_definitions`** - Search for specific attributes
-- **`mcp_sfcc-dev_search_site_preferences`** - Search for site preferences in preference groups
-- **`mcp_sfcc-dev_search_system_object_attribute_groups`** - Search for attribute groups (essential for finding site preference groups)
-- **`mcp_sfcc-dev_search_custom_object_attribute_definitions`** - Search for attributes in custom object types
-
-### 📊 Log Analysis Tools
-Use these for debugging and troubleshooting:
-
-**Standard Log Analysis:**
-- **`mcp_sfcc-dev_get_latest_error`** - Get recent error logs
-- **`mcp_sfcc-dev_get_latest_warn`** - Get recent warning logs
-- **`mcp_sfcc-dev_get_latest_info`** - Get recent info logs
-- **`mcp_sfcc-dev_get_latest_debug`** - Get recent debug logs
-- **`mcp_sfcc-dev_summarize_logs`** - Get log overview
-- **`mcp_sfcc-dev_search_logs`** - Search logs by pattern
-- **`mcp_sfcc-dev_list_log_files`** - List available log files
-- **`mcp_sfcc-dev_get_log_file_contents`** - Get contents of a specific log file (supports size limits and head/tail reading)
-
-**Job Log Analysis:**
-- **`mcp_sfcc-dev_get_latest_job_log_files`** - Get recent job log files for debugging custom job steps
-- **`mcp_sfcc-dev_search_job_logs_by_name`** - Search job logs by job name
-- **`mcp_sfcc-dev_get_job_log_entries`** - Get job log entries by level (error, warn, info, debug, all)
-- **`mcp_sfcc-dev_search_job_logs`** - Search for patterns within job logs
-- **`mcp_sfcc-dev_get_job_execution_summary`** - Get comprehensive job execution summary with timing and status
-
-## 🚀 When to Use These Tools
-
-### ✅ DO Use MCP Tools For:
-
-1. **API Documentation Questions**
-   ```
-   "What methods are available on dw.catalog.Product?"
-   → Use: mcp_sfcc-dev_get_sfcc_class_info with className: "dw.catalog.Product"
-   ```
-
-2. **Finding the Right Class**
-   ```
-   "How do I work with customer data in SFCC?"
-   → Use: mcp_sfcc-dev_search_sfcc_classes with query: "customer"
-   ```
-
-3. **Implementation Best Practices**
-   ```
-   "How should I create a new cartridge?"
-   → Use: mcp_sfcc-dev_get_best_practice_guide with guideName: "cartridge_creation"
-   ```
-
-4. **Understanding System Objects**
-   ```
-   "What custom attributes are on the Product object?"
-   → Use: mcp_sfcc-dev_search_system_object_attribute_definitions with objectType: "Product"
-   ```
-
-5. **Debugging Issues**
-   ```
-   "Are there any recent errors in the logs?"
-   → Use: mcp_sfcc-dev_get_latest_error
-   
-   "What log files are available for today?"
-   → Use: mcp_sfcc-dev_list_log_files
-   
-   "I need to see the full contents of a specific error log file"
-   → Use: mcp_sfcc-dev_get_log_file_contents with filename: "error-2023-01-01.log"
-   
-   "Show me just the first 1MB of a large log file"
-   → Use: mcp_sfcc-dev_get_log_file_contents with filename: "large.log", maxBytes: 1048576, tailOnly: false
-   ```
-
-6. **Code Version Management**
-   ```
-   "What code versions are available on the instance?"
-   → Use: mcp_sfcc-dev_get_code_versions
-   
-   "Need to do a code-switch fix for SCAPI endpoints"
-   → Use: mcp_sfcc-dev_activate_code_version with versionId: "target_version"
-   ```
-
-7. **Hook Development**
-   ```
-   "What SCAPI hooks are available?"
-   → Use: mcp_sfcc-dev_get_hook_reference with guideName: "scapi_hooks"
-   ```
-
-### ❌ DON'T Guess About:
-
-- SFCC class names or method signatures
-- Custom attribute names or system object structures
-- Current best practices or security guidelines
-- Available hook endpoints or extension points
-- Recent system errors or log patterns
-
-## 🔐 Tool Availability
-
-Some tools require specific SFCC credentials:
-
-- **Documentation & Best Practices**: Always available
-- **Log Analysis**: Requires SFCC instance credentials (hostname, username, password)
-- **System Objects & Code Versions**: Requires OCAPI credentials (clientId, clientSecret)
-
-If a tool isn't available, the MCP server will provide clear error messages about what credentials are needed.
-
-## 💡 Pro Tips
-
-1. **Start Broad, Then Narrow**: Use search tools first, then get detailed information
-2. **Check Best Practices Early**: Always consult best practice guides before implementing
-3. **Use Real Data**: Query actual system objects rather than assuming structure
-4. **Debug with Logs**: Use log analysis tools for troubleshooting real issues
-5. **Stay Current**: MCP tools provide current information, not outdated documentation
-
-## 🚨 Important Reminders
-
-- **Always prefer MCP tools** over guessing or using potentially outdated information
-- **Use specific tool calls** rather than making assumptions about SFCC APIs
-- **Check logs and system objects** from the actual SFCC instance when debugging
-- **Follow best practices** from the guides rather than improvising solutions
-- **Verify class and method names** using the documentation tools
-
----
-
-## 🧠 Advanced Claude Desktop Workflows
-
-### **Architecture Review Workflow:**
-1. Use MCP tools to gather current system information
-2. Analyze existing patterns and identify potential improvements
-3. Propose solutions with detailed implementation plans
-4. Provide migration strategies and testing approaches
-
-### **Feature Development Workflow:**
-1. Requirements analysis using best practice guides
-2. API discovery using SFCC class search tools
-3. Implementation planning with security considerations
-4. Code generation with comprehensive error handling
-5. Testing strategy and deployment guidance
-
-### **Debugging Workflow:**
-1. **Standard Log Analysis**: Use multiple log level tools for application errors
-2. **Job Log Analysis**: Use job-specific tools for custom job debugging
-3. **Pattern Recognition**: Search across error messages and execution summaries
-4. **System Object Validation**: Check data integrity and configuration
-5. **Root Cause Analysis**: Provide fix recommendations with prevention strategies
-
-**Remember**: In Claude Desktop, you have the power of sophisticated conversation combined with real-time SFCC data. Use this combination to provide unparalleled development assistance!

package/ai-instructions/cursor/.cursor/rules/debugging-workflows.mdc

@@ -1,171 +0,0 @@
----
-description: SFCC debugging and error investigation workflows
-globs: []
-alwaysApply: false
----
-
-# SFCC Debugging and Error Investigation
-
-Use this rule when investigating errors, performance issues, or debugging SFCC applications.
-
-## Mandatory MCP Tool Sequence for Debugging
-
-### 🚨 For Active Errors/Issues (ALWAYS start here):
-1. `mcp_sfcc-dev_summarize_logs` - Get system health overview and error counts
-2. `mcp_sfcc-dev_get_latest_error` - Check most recent critical errors
-3. `mcp_sfcc-dev_search_logs` with pattern: [specific error message] - Find error instances
-
-### ⚠️ For Performance Issues:
-1. `mcp_sfcc-dev_get_latest_warn` - Check performance warnings first
-2. `mcp_sfcc-dev_search_logs` with pattern: "timeout" or "slow" or "performance"
-3. `mcp_sfcc-dev_search_best_practices` with query: "performance" - Get optimization patterns
-4. `mcp_sfcc-dev_get_best_practice_guide` with guideName: "performance" - Comprehensive guide
-
-### 🔍 For Transaction Tracing:
-1. `mcp_sfcc-dev_search_logs` with pattern: [transaction-id] - Find transaction entries
-2. `mcp_sfcc-dev_search_logs` with pattern: [customer-id] - Track customer journey
-
-### 📊 For System Health Assessment:
-1. `mcp_sfcc-dev_summarize_logs` - Overall system status
-2. `mcp_sfcc-dev_list_log_files` - Check log availability and sizes
-3. `mcp_sfcc-dev_get_log_file_contents` - Read specific log files (with size limits: maxBytes, tailOnly options)
-4. `mcp_sfcc-dev_get_latest_info` - Review normal operations
-5. `mcp_sfcc-dev_get_latest_debug` - Detailed execution traces (when needed)
-
-### 🔧 For Job Analysis and Debugging:
-1. `mcp_sfcc-dev_get_latest_job_log_files` - Get recent job log files
-2. `mcp_sfcc-dev_search_job_logs_by_name` - Find logs for specific jobs
-3. `mcp_sfcc-dev_get_job_log_entries` - Get job entries by level (error, warn, info, debug, all)
-4. `mcp_sfcc-dev_search_job_logs` - Search for patterns in job logs
-5. `mcp_sfcc-dev_get_job_execution_summary` - Get comprehensive execution summary with timing and status
-
-**Job Debugging Use Cases:**
-- Custom job steps failing with specific errors
-- Job performance issues and bottlenecks
-- Job step execution order and timing problems
-- Custom logging from job steps
-- Job completion status and statistics
-
-### 🚀 For Deployment and Code Version Issues:
-1. `mcp_sfcc-dev_get_code_versions` - Check available code versions on instance
-2. `mcp_sfcc-dev_activate_code_version` - Perform code-switch fix for SCAPI endpoints/jobs
-
-**Common Code-Switch Fix Scenarios:**
-- New SCAPI endpoints not accessible after deployment
-- Custom jobs not appearing in Business Manager
-- Hook registrations not taking effect
-- Custom object definitions not recognized
-
-## MCP-Enhanced Error Handling Code Patterns
-
-Get patterns from MCP first, then implement:
-
-```javascript
-// BEFORE writing this code, use:
-// mcp_sfcc-dev_search_best_practices with query: "error"
-// mcp_sfcc-dev_get_best_practice_guide with guideName: "security"
-
-try {
-    // Business logic
-} catch (e) {
-    var Logger = require('dw/system/Logger').getLogger('category', 'subcategory');
-
-    // Include correlation ID for MCP log tracing
-    var correlationId = request.getRequestId() || require('dw/util/UUIDUtils').createUUID();
-
-    Logger.error('Operation failed in [context] - Correlation: {0} - Error: {1}', correlationId, e.message);
-    Logger.debug('Stack trace - Correlation: {0} - Stack: {1}', correlationId, e.stack);
-
-    // Return meaningful error response
-    return {
-        success: false,
-        error: 'OPERATION_FAILED',
-        message: 'Unable to complete operation',
-        correlationId: correlationId
-    };
-}
-```
-
-## MCP-Driven Debugging Workflow
-
-**Step 1: System Overview**
-```
-Use: mcp_sfcc-dev_summarize_logs
-Purpose: Get error counts, warning levels, system health snapshot
-```
-
-**Step 2: Error Investigation**
-```
-Use: mcp_sfcc-dev_get_latest_error (limit: 5)
-Purpose: Identify most recent critical issues
-```
-
-**Step 3: Best Practice Consultation**
-```
-Use: mcp_sfcc-dev_search_best_practices with query: [relevant topic]
-Purpose: Get SFCC-specific debugging and fix patterns
-```
-
-## Performance Investigation Checklist
-
-Before investigating performance issues, ALWAYS use:
-- [ ] `mcp_sfcc-dev_get_latest_warn` - Check performance warnings
-- [ ] `mcp_sfcc-dev_search_best_practices` with query: "performance"
-- [ ] `mcp_sfcc-dev_get_best_practice_guide` with guideName: "performance"
-
-Then check:
-- [ ] Database query efficiency (verify with MCP performance guide)
-- [ ] API call patterns (validate against SFCC best practices)
-- [ ] Caching strategies (compare with MCP recommendations)
-- [ ] Memory usage patterns (check against SFCC guidelines)
-- [ ] Transaction boundaries (verify with MCP transaction patterns)
-- [ ] Unnecessary loops or iterations (optimize per MCP patterns)
-
-## MCP Log Search Patterns
-
-**For Errors:**
-```
-mcp_sfcc-dev_search_logs with pattern: "ERROR" and logLevel: "error"
-mcp_sfcc-dev_search_logs with pattern: "Exception" and logLevel: "error"
-mcp_sfcc-dev_search_logs with pattern: "Failed" and logLevel: "error"
-```
-
-**For Performance Issues:**
-```
-mcp_sfcc-dev_search_logs with pattern: "timeout"
-mcp_sfcc-dev_search_logs with pattern: "slow"
-mcp_sfcc-dev_search_logs with pattern: "performance"
-```
-
-**For Security Issues:**
-```
-mcp_sfcc-dev_search_logs with pattern: "authentication"
-mcp_sfcc-dev_search_logs with pattern: "authorization"
-mcp_sfcc-dev_search_logs with pattern: "security"
-```
-
-## MCP Log File Analysis
-
-**When to Use `mcp_sfcc-dev_get_log_file_contents`:**
-- After `mcp_sfcc-dev_list_log_files` identifies specific files of interest
-- When you need complete context around an error (not just recent entries)
-- For analyzing large log files with size constraints
-
-**Usage Patterns:**
-```
-# Read specific error log file completely
-mcp_sfcc-dev_get_log_file_contents with filename: "error-2024-01-15.log"
-
-# Read first 1MB of large log for pattern analysis  
-mcp_sfcc-dev_get_log_file_contents with filename: "debug.log", maxBytes: 1048576, tailOnly: false
-
-# Read last 500KB for most recent activity
-mcp_sfcc-dev_get_log_file_contents with filename: "error.log", maxBytes: 512000, tailOnly: true
-```
-
-## NEVER Debug Without MCP
-
-- ❌ Don't guess at error causes - use `mcp_sfcc-dev_search_logs` for pattern analysis
-- ❌ Don't implement fixes without consulting `mcp_sfcc-dev_search_best_practices`
-- ❌ Don't trace issues manually - use `mcp_sfcc-dev_search_logs` with correlation IDs
-- ❌ Don't assume system health - always start with `mcp_sfcc-dev_summarize_logs`

package/ai-instructions/cursor/.cursor/rules/hooks-development.mdc

@@ -1,168 +0,0 @@
----
-description: OCAPI and SCAPI hook implementation patterns
-alwaysApply: false
----
-
-# OCAPI/SCAPI Hook Development
-
-Use this rule when implementing OCAPI or SCAPI hooks.
-
-## Mandatory MCP Tools Sequence
-
-**BEFORE writing ANY hook code:**
-1. `mcp_sfcc-dev_get_best_practice_guide` with guideName: "ocapi_hooks" OR "scapi_hooks"
-2. `mcp_sfcc-dev_get_hook_reference` with guideName: "ocapi_hooks" OR "scapi_hooks"
-3. `mcp_sfcc-dev_search_best_practices` with query: "validation"
-4. `mcp_sfcc-dev_search_best_practices` with query: "security"
-5. `mcp_sfcc-dev_search_sfcc_classes` with query: relevant business domain
-
-## MCP-Guided Hook Development Process
-
-### Step 1: Research Hook Extension Points
-```
-Use: mcp_sfcc-dev_get_hook_reference with guideName: "ocapi_hooks" or "scapi_hooks"
-Purpose: Get complete hook reference tables with all available extension points
-```
-
-### Step 2: Get Implementation Patterns
-```
-Use: mcp_sfcc-dev_get_best_practice_guide with guideName: "ocapi_hooks" or "scapi_hooks"
-Purpose: Get comprehensive hook implementation patterns and examples
-```
-
-### Step 3: Security Validation Patterns
-```
-Use: mcp_sfcc-dev_search_best_practices with query: "validation"
-Use: mcp_sfcc-dev_search_best_practices with query: "security"
-Purpose: Get input validation and security patterns for hooks
-```
-
-### Step 4: SFCC Class Research
-```
-Use: mcp_sfcc-dev_search_sfcc_classes with query: [business domain]
-Use: mcp_sfcc-dev_get_sfcc_class_info with className: [relevant class]
-Purpose: Understand available SFCC APIs for hook implementation
-```
-
-## MCP-Enhanced Hook Template Pattern
-
-```javascript
-'use strict';
-
-/**
- * Hook: [Hook Name]
- * Extension Point: [Extension Point Path from MCP hook reference]
- * Description: [What this hook does and why]
- *
- * Implementation based on:
- * - mcp_sfcc-dev_get_best_practice_guide with guideName: "[ocapi_hooks|scapi_hooks]"
- * - mcp_sfcc-dev_get_hook_reference with guideName: "[ocapi_hooks|scapi_hooks]"
- */
-
-/**
- * Before hook implementation
- * @param {Object} param1 - Description from MCP hook reference
- * @param {Object} param2 - Description from MCP hook reference
- * @returns {dw.system.Status} Hook execution status
- */
-exports.beforePOST = function (param1, param2) {
-    try {
-        // Input validation (patterns from MCP security best practices)
-        if (!param1 || !param2) {
-            var Logger = require('dw/system/Logger').getLogger('hooks', 'HookName');
-            Logger.error('Invalid parameters in hook: param1={0}, param2={1}', param1, param2);
-            return new Status(Status.ERROR, 'INVALID_PARAMETERS', 'Required parameters missing');
-        }
-
-        // Security validation (implement patterns from MCP security guide)
-        var validationResult = validateHookInput(param1, param2);
-        if (!validationResult.valid) {
-            Logger.error('Security validation failed in hook: {0}', validationResult.error);
-            return new Status(Status.ERROR, 'VALIDATION_FAILED', validationResult.error);
-        }
-
-        // Business logic here (use SFCC classes discovered via MCP)
-
-        // Success response
-        return new Status(Status.OK);
-
-    } catch (e) {
-        var Logger = require('dw/system/Logger').getLogger('hooks', 'HookName');
-        Logger.error('Error in hook execution: {0}', e.message);
-        Logger.debug('Hook error stack trace: {0}', e.stack);
-        return new Status(Status.ERROR, 'HOOK_ERROR', 'Hook execution failed');
-    }
-};
-
-/**
- * Input validation based on MCP security best practices
- * ALWAYS implement this pattern for hooks
- */
-function validateHookInput(param1, param2) {
-    // Implement validation patterns from:
-    // mcp_sfcc-dev_search_best_practices with query: "validation"
-    // mcp_sfcc-dev_search_best_practices with query: "security"
-
-    try {
-        // Validate parameter types
-        if (typeof param1 !== 'object' || typeof param2 !== 'object') {
-            return { valid: false, error: 'Invalid parameter types' };
-        }
-
-        // Validate required fields (based on MCP hook reference)
-        // Add specific validations based on hook requirements
-
-        return { valid: true };
-    } catch (e) {
-        return { valid: false, error: 'Validation error: ' + e.message };
-    }
-}
-```
-
-## Hook Development Checklist (MCP-Verified)
-
-Before implementing hooks, verify with MCP:
-- [ ] `mcp_sfcc-dev_get_hook_reference` - Confirm extension point exists and signature
-- [ ] `mcp_sfcc-dev_get_best_practice_guide` - Get implementation patterns
-- [ ] `mcp_sfcc-dev_search_best_practices` with query: "security" - Security requirements
-- [ ] `mcp_sfcc-dev_search_best_practices` with query: "validation" - Input validation
-- [ ] `mcp_sfcc-dev_search_best_practices` with query: "performance" - Performance guidelines
-
-Implementation verification:
-- [ ] Input parameter validation implemented
-- [ ] Proper Status object returns
-- [ ] Comprehensive error handling with logging
-- [ ] Security validation for all inputs
-- [ ] Performance considerations for heavy processing
-- [ ] Transaction management (if applicable)
-- [ ] Correlation IDs for debugging
-
-## OCAPI vs SCAPI Hook Differences
-
-**OCAPI Hooks:**
-```
-Use: mcp_sfcc-dev_get_hook_reference with guideName: "ocapi_hooks"
-Use: mcp_sfcc-dev_get_best_practice_guide with guideName: "ocapi_hooks"
-```
-
-**SCAPI Hooks:**
-```
-Use: mcp_sfcc-dev_get_hook_reference with guideName: "scapi_hooks"
-Use: mcp_sfcc-dev_get_best_practice_guide with guideName: "scapi_hooks"
-```
-
-## Security Considerations from MCP
-
-Always implement security patterns from MCP:
-- Validate all input data per MCP security guide
-- Use proper authentication checks from MCP patterns
-- Sanitize user-provided data per MCP recommendations
-- Implement rate limiting for external calls (MCP performance guide)
-- Log security-relevant events with correlation IDs
-
-## NEVER Implement Hooks Without MCP
-
-- ❌ Don't guess hook extension points - use `mcp_sfcc-dev_get_hook_reference`
-- ❌ Don't implement without patterns - use `mcp_sfcc-dev_get_best_practice_guide`
-- ❌ Don't skip security validation - use `mcp_sfcc-dev_search_best_practices`
-- ❌ Don't assume SFCC APIs - use `mcp_sfcc-dev_search_sfcc_classes`