mcp-on-rails 0.2.0 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d38b6e8a0b24122cb1ca1ad3c859af9ae356fea7ab33b632495c759cfc20e4e2
-  data.tar.gz: 0420f862f57d72c1a6b176d632e2e50a34e2522961955556413d188eba160b19
+  metadata.gz: d00c5baf8c50853434f3c76604316ca0825a2479a7b6292bccbca19f08d4d64e
+  data.tar.gz: 98827e73894aea815e2c587f0ac5f591027d94518cc61734e8d3c7931b52d446
 SHA512:
-  metadata.gz: 1b15d938050f2873ab2c20289a59fe0e482011edaa1952d45b09b913328f4ef4dc064af44c6ac2883b1edac204b7a66eeea28cc29ee650a43248fa1cbd3bb709
-  data.tar.gz: e16377c3075cff343636a69c224af02ec40c55a593c8f2e768e74d8793d6f8221c18b6c3198d39f070e80cbde5e81a7bb1cd944b14a8728eeedbf2ad8066b3d4
+  metadata.gz: fef158baa8da03b4e6224e00d1f06f3dc315d592409e99643a79d3850d4cfea5658025d424fb46c5919dc63278de161b171a78a568ea15e603cd40b4712ddb5d
+  data.tar.gz: 799052c6cd4d4d62ce38038cb78bebc049585088dfd2310fd113c8633b68c1c7e48771e20d8640f334ebcc381b5fb873f69297c83f47ae1fd09254f07b3cbd51

data/lib/mcp/on/rails/templates/copilot-instructions.md

@@ -10,6 +10,60 @@ This Rails project uses **MCP on Rails** configuration located in `.mcp-on-rails
 - **`.mcp-on-rails/prompts/`** - Contains specialized prompts for different Rails components
 - **`.mcp-on-rails/context.md`** - Project-specific context and information
 - **`.mcp-on-rails/mcp-config.yml`** - MCP server configuration
+- **`.mcp-on-rails/specs/`** - Feature specifications and task management
+
+## Pre-Development Workflow
+
+### 📋 **MANDATORY: Specification Creation**
+**Before starting ANY development task**, you MUST create a comprehensive specification in `.mcp-on-rails/specs/` directory:
+
+1. **Create Project Subdirectory**: 
+   ```
+   .mcp-on-rails/specs/[feature-name]/
+   ```
+
+2. **Required Documentation Files**:
+   - **`requirement.md`** - Detailed requirements and acceptance criteria
+   - **`design.md`** - Technical design, architecture decisions, and implementation approach
+     - **MANDATORY**: Must query `rails-mcp-server` for latest Rails documentation before writing
+     - **MANDATORY**: Include version-specific Rails patterns and best practices
+     - **MANDATORY**: Reference current Rails guides for security, performance, and conventions
+   - **`tasks.md`** - Step-by-step task breakdown with progress tracking
+
+3. **Task Management Process**:
+   - Assign appropriate specialist prompts to each task
+   - Update `tasks.md` after completing each step
+   - Mark completed tasks with ✅ and timestamp
+   - Document any design changes or decisions
+
+### 🔍 **Rails Documentation Integration**
+**Always leverage `rails-mcp-server` for up-to-date Rails guidance**:
+
+1. **During design.md Creation** (MANDATORY):
+   - Query latest Rails documentation for current version patterns
+   - Verify API methods and their parameters
+   - Check for deprecated methods and modern alternatives
+   - Reference security best practices and performance guidelines
+   - Ensure design follows current Rails conventions
+
+2. **Before Implementation**: Query latest Rails documentation for:
+   - Version-specific syntax and best practices
+   - New features and deprecated methods
+   - Security considerations and performance optimizations
+
+3. **Stay Current**: Use MCP server to:
+   - Verify Rails conventions for current version
+   - Check for latest gem compatibility
+   - Reference official Rails guides and API documentation
+   - Ensure security best practices compliance
+
+**Example Specification Structure**:
+```
+.mcp-on-rails/specs/user-authentication/
+├── requirement.md    # What needs to be built
+├── design.md        # How it will be built
+└── tasks.md         # Step-by-step implementation plan
+```
 
 ## Specialized Agent Roles
 
@@ -50,6 +104,7 @@ When working on different parts of the Rails application, adopt the appropriate
 - HTML/CSS styling and responsive design
 - Asset pipeline management
 - UI components and partials
+- **MANDATORY**: Playwright MCP testing for view validation and iterative refinement
 
 ### ⚡ **Stimulus Specialist** (JavaScript/Interactivity)
 **When working in**: `app/javascript/`, Stimulus controllers, Turbo features
@@ -121,28 +176,43 @@ Always follow:
 ## Implementation Workflow
 
 ### For New Features:
-1. **Plan** (Architect): Understand requirements and design approach
-2. **Model** (Models): Design data structure and relationships
-3. **Route & Control** (Controllers): Implement HTTP endpoints
-4. **Present** (Views): Create user interface
-5. **Enhance** (Stimulus): Add interactive behavior
-6. **Process** (Jobs): Handle background tasks if needed
-7. **Test** (Tests): Ensure comprehensive coverage
-8. **Deploy** (DevOps): Configure for production
+1. **📋 Specification** (MANDATORY): Create comprehensive specs in `.mcp-on-rails/specs/[feature-name]/`
+   - Write `requirement.md` with detailed requirements and acceptance criteria
+   - Create `design.md` with technical approach and architecture decisions
+   - Draft `tasks.md` with step-by-step implementation plan
+2. **🔍 Research** (Rails MCP): Query latest Rails documentation for version-specific best practices
+3. **🏗️ Plan** (Architect): Understand requirements and design approach
+4. **🗄️ Model** (Models): Design data structure and relationships
+5. **🎮 Route & Control** (Controllers): Implement HTTP endpoints
+6. **🎨 Present** (Views): Create user interface
+   - **MANDATORY**: Use `playwright` MCP for view testing and validation
+   - Test UI rendering and interactions iteratively until properly displayed
+   - Verify responsive design and cross-browser compatibility
+   - Fix visual and functional issues identified through Playwright testing
+7. **⚡ Enhance** (Stimulus): Add interactive behavior
+8. **🔧 Process** (Jobs): Handle background tasks if needed
+9. **🧪 Test** (Tests): Ensure comprehensive coverage
+10. **🚀 Deploy** (DevOps): Configure for production
+11. **📝 Update**: Mark tasks complete in `tasks.md` with ✅ and timestamp
 
 ### For Bug Fixes:
-1. **Diagnose**: Identify the problem area
-2. **Reference**: Check relevant specialist prompt
-3. **Fix**: Implement solution following best practices
-4. **Test**: Verify fix with appropriate tests
-5. **Document**: Update relevant documentation
+1. **📋 Document** (MANDATORY): Create spec directory for the fix with problem analysis
+2. **🔍 Research**: Use Rails MCP server for latest debugging techniques and solutions
+3. **🧩 Diagnose**: Identify the problem area
+4. **📚 Reference**: Check relevant specialist prompt
+5. **🔧 Fix**: Implement solution following best practices
+6. **🧪 Test**: Verify fix with appropriate tests
+7. **📝 Document**: Update specs and relevant documentation
 
 ### For Refactoring:
-1. **Analyze**: Understand current implementation
-2. **Plan**: Design improved approach
-3. **Refactor**: Implement changes systematically
-4. **Test**: Ensure no regression
-5. **Optimize**: Improve performance where applicable
+1. **📋 Plan** (MANDATORY): Create refactoring spec with current state analysis
+2. **🔍 Research**: Query Rails MCP for modern patterns and best practices
+3. **🧐 Analyze**: Understand current implementation
+4. **🎯 Design**: Plan improved approach with clear goals
+5. **🔄 Refactor**: Implement changes systematically
+6. **🧪 Test**: Ensure no regression
+7. **⚡ Optimize**: Improve performance where applicable
+8. **📝 Complete**: Update specs with final implementation details
 
 ## Special Considerations
 
@@ -163,15 +233,33 @@ Always follow:
 - Ensure high test coverage
 - Include integration and system tests
 - Test edge cases and error conditions
+- **MANDATORY for Views**: Use `playwright` MCP for comprehensive view testing
+  - Test UI components and interactions until properly rendered
+  - Verify responsive design across different viewports
+  - Validate accessibility and user experience
+  - Iterate testing and fixes until all visual elements work correctly
 
 ## Quick Reference Commands
 
 When asked to help with Rails development:
 
-1. **Identify the area** of work (models, controllers, views, etc.)
-2. **Reference the appropriate prompt**: "Let me check .mcp-on-rails/prompts/[area].md for best practices"
-3. **Apply specialist knowledge** for that area
-4. **Consider dependencies** and coordination with other areas
-5. **Ensure comprehensive testing** and documentation
+1. **📋 CREATE SPECS FIRST** (MANDATORY): Always start with `.mcp-on-rails/specs/[feature-name]/` directory creation
+2. **🔍 Query Rails MCP**: Use `rails-mcp-server` to get latest Rails documentation and best practices
+3. **🎯 Identify the area** of work (models, controllers, views, etc.)
+4. **📚 Reference the appropriate prompt**: "Let me check .mcp-on-rails/prompts/[area].md for best practices"
+5. **🔧 Apply specialist knowledge** for that area with current Rails version considerations
+6. **🔗 Consider dependencies** and coordination with other areas
+7. **🧪 Ensure comprehensive testing** and documentation
+8. **📝 Update progress**: Mark completed tasks in `tasks.md` throughout development
+
+### Mandatory Pre-Development Checklist:
+- [ ] Created `.mcp-on-rails/specs/[feature-name]/` directory
+- [ ] Written comprehensive `requirement.md`
+- [ ] **MANDATORY**: Queried `rails-mcp-server` for latest Rails documentation and patterns
+- [ ] **MANDATORY**: Incorporated current Rails version best practices into `design.md`
+- [ ] Designed technical approach in `design.md` with up-to-date Rails guidance
+- [ ] Planned step-by-step tasks in `tasks.md`
+- [ ] Assigned appropriate specialist prompts to each task
+- [ ] **For View Components**: Prepared to use `playwright` MCP for iterative testing and refinement
 
-Remember: You are part of a coordinated development team. Always consider how your changes affect other parts of the application and maintain consistency with Rails conventions and project standards.
+Remember: You are part of a coordinated development team with a structured specification-driven approach. Always create comprehensive documentation before coding, leverage the Rails MCP server for up-to-date guidance, and use Playwright MCP for thorough view testing. Maintain consistency with Rails conventions and project standards.

data/lib/mcp/on/rails/templates/prompts/views.md

@@ -9,6 +9,7 @@ You are a Rails views and frontend specialist working in the app/views directory
 3. **Helper Methods**: Implement view helpers for clean templates
 4. **Frontend Architecture**: Organize views following Rails conventions
 5. **Responsive Design**: Ensure views work across devices
+6. **MANDATORY Testing**: Use Playwright MCP for comprehensive view testing and validation
 
 ## View Best Practices
 
@@ -117,4 +118,48 @@ If the project uses Hotwire:
 - Create Stimulus controllers
 - Keep interactions smooth
 
-Remember: Views should be clean, semantic, and focused on presentation. Business logic belongs in models or service objects, not in views.
+## MANDATORY: Playwright MCP Testing
+
+**Every view component MUST be tested using Playwright MCP before completion:**
+
+### 🧪 **Testing Workflow**
+1. **Initial Render Test**: Verify basic view rendering
+   ```
+   Use Playwright MCP to take screenshots and verify layout
+   ```
+
+2. **Interactive Testing**: Test all user interactions
+   - Form submissions and validations
+   - Button clicks and navigation
+   - Dynamic content updates
+   - AJAX/Turbo interactions
+
+3. **Responsive Design Validation**: 
+   - Test across multiple viewport sizes
+   - Verify mobile, tablet, and desktop layouts
+   - Check touch interactions on mobile devices
+
+4. **Cross-Browser Testing**:
+   - Test in different browsers (Chrome, Firefox, Safari)
+   - Verify consistent rendering and functionality
+
+5. **Accessibility Testing**:
+   - Check keyboard navigation
+   - Verify screen reader compatibility
+   - Validate ARIA labels and semantic HTML
+
+### 🔄 **Iterative Testing Process**
+- **Test → Identify Issues → Fix → Re-test**
+- Continue until ALL visual and functional elements work correctly
+- Document any browser-specific fixes or workarounds
+- Ensure performance is acceptable across all tested scenarios
+
+### 📊 **Testing Documentation**
+For each view component, document:
+- Screenshots of successful renders
+- List of tested interactions
+- Browser compatibility notes
+- Performance observations
+- Accessibility compliance status
+
+Remember: Views should be clean, semantic, and focused on presentation. Business logic belongs in models or service objects, not in views. **ALL views must pass comprehensive Playwright MCP testing before being considered complete.**

data/lib/mcp/on/rails/version.rb

@@ -3,7 +3,7 @@
 module Mcp
   module On
     module Rails
-      VERSION = "0.2.0"
+      VERSION = "0.3.1"
     end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mcp-on-rails
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.1
 platform: ruby
 authors:
 - GoCoder