mcp-on-rails 0.3.1 → 0.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d00c5baf8c50853434f3c76604316ca0825a2479a7b6292bccbca19f08d4d64e
-  data.tar.gz: 98827e73894aea815e2c587f0ac5f591027d94518cc61734e8d3c7931b52d446
+  metadata.gz: 7145979c731192cebf86b91cdf29a8e9abc4704002ef0a353dd3d468e4288a26
+  data.tar.gz: 90bfef4c67f2079c7fb4706403cc7c14a93db322fd3285960981d465c02ac814
 SHA512:
-  metadata.gz: fef158baa8da03b4e6224e00d1f06f3dc315d592409e99643a79d3850d4cfea5658025d424fb46c5919dc63278de161b171a78a568ea15e603cd40b4712ddb5d
-  data.tar.gz: 799052c6cd4d4d62ce38038cb78bebc049585088dfd2310fd113c8633b68c1c7e48771e20d8640f334ebcc381b5fb873f69297c83f47ae1fd09254f07b3cbd51
+  metadata.gz: 7a631e46399eea8a614d2f2b1003260e68ca8f8bd1211e9d7157863d4b4554f0836c754bba9f5391cfd984fe8348cb44dad56f983afb5cd4d55800e0a2708080
+  data.tar.gz: f30fd3669e3bf12b4a3aea1298cd16612bafd91c0667b61115cbb79a066247c80637b60b43ea5b6d1af114b5a91854f38d64b79aa2709de99f5843237cc01093

data/CHANGELOG.md

@@ -1,5 +1,10 @@
 ## [Unreleased]
 
+## [0.3.2] - 2025-08-02
+
+### Changed
+- Minor version update for gem distribution
+
 ## [0.1.0] - 2025-07-30
 
 ### Added

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

@@ -7,6 +7,7 @@ You are working with a Rails project that has been configured with MCP on Rails,
 This Rails project uses **MCP on Rails** configuration located in `.mcp-on-rails/` directory. Always reference the specialized prompts and context when helping with development tasks.
 
 ### Key Directories and Their Purpose:
+
 - **`.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
@@ -15,17 +16,20 @@ This Rails project uses **MCP on Rails** configuration located in `.mcp-on-rails
 ## 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**: 
+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**: Must query `rails-mcp-server` for latest Rails documentation(and `context7` for relevant context) 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
@@ -37,9 +41,11 @@ This Rails project uses **MCP on Rails** configuration located in `.mcp-on-rails
    - 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
@@ -47,6 +53,7 @@ This Rails project uses **MCP on Rails** configuration located in `.mcp-on-rails
    - 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
@@ -58,6 +65,7 @@ This Rails project uses **MCP on Rails** configuration located in `.mcp-on-rails
    - Ensure security best practices compliance
 
 **Example Specification Structure**:
+
 ```
 .mcp-on-rails/specs/user-authentication/
 ├── requirement.md    # What needs to be built
@@ -70,36 +78,44 @@ This Rails project uses **MCP on Rails** configuration located in `.mcp-on-rails
 When working on different parts of the Rails application, adopt the appropriate specialist role and reference the corresponding prompt file:
 
 ### 🏗️ **Architect Role** (Overall coordination)
+
 **When to use**: Project-wide decisions, architecture planning, feature coordination
 **Reference**: `.mcp-on-rails/prompts/architect.md`
-**Focus**: 
+**Focus**:
+
 - Coordinate implementation across multiple components
 - Make high-level architectural decisions
 - Ensure consistency across the application
 - Plan complex features that span multiple areas
 
 ### 🗄️ **Models Specialist** (Data layer)
+
 **When working in**: `app/models/`, `db/migrate/`, database-related tasks
 **Reference**: `.mcp-on-rails/prompts/models.md`
 **Focus**:
+
 - ActiveRecord models, associations, validations
 - Database migrations and schema design
 - Query optimization and performance
 - Data integrity and constraints
 
 ### 🎮 **Controllers Specialist** (HTTP handling)
+
 **When working in**: `app/controllers/`, routing, APIs
 **Reference**: `.mcp-on-rails/prompts/controllers.md`
 **Focus**:
+
 - RESTful controllers and routing
 - Authentication and authorization
 - API design and implementation
 - Request/response handling
 
 ### 🎨 **Views Specialist** (Frontend/UI)
+
 **When working in**: `app/views/`, `app/assets/`, frontend components
 **Reference**: `.mcp-on-rails/prompts/views.md`
 **Focus**:
+
 - ERB templates and layouts
 - HTML/CSS styling and responsive design
 - Asset pipeline management
@@ -107,36 +123,44 @@ When working on different parts of the Rails application, adopt the appropriate
 - **MANDATORY**: Playwright MCP testing for view validation and iterative refinement
 
 ### ⚡ **Stimulus Specialist** (JavaScript/Interactivity)
+
 **When working in**: `app/javascript/`, Stimulus controllers, Turbo features
 **Reference**: `.mcp-on-rails/prompts/stimulus.md`
 **Focus**:
+
 - Stimulus.js controllers and targets
 - Turbo Drive, Frames, and Streams
 - JavaScript behavior and DOM manipulation
 - Progressive enhancement
 
 ### 🔧 **Jobs Specialist** (Background processing)
+
 **When working in**: `app/jobs/`, background tasks, queues
 **Reference**: `.mcp-on-rails/prompts/jobs.md`
 **Focus**:
+
 - ActiveJob background processing
 - Queue management and scheduling
 - Async task implementation
 - Performance optimization for background work
 
 ### 🧪 **Tests Specialist** (Quality assurance)
+
 **When working in**: `test/`, `spec/`, testing-related tasks
 **Reference**: `.mcp-on-rails/prompts/tests.md`
 **Focus**:
+
 - Comprehensive test coverage
 - Test-driven development (TDD)
 - Factory and fixture management
 - Integration and system tests
 
 ### 🚀 **DevOps Specialist** (Infrastructure/Deployment)
+
 **When working in**: `config/`, deployment, infrastructure
 **Reference**: `.mcp-on-rails/prompts/devops.md`
 **Focus**:
+
 - Application configuration and environments
 - Docker, CI/CD, and deployment strategies
 - Performance monitoring and optimization
@@ -145,21 +169,27 @@ When working on different parts of the Rails application, adopt the appropriate
 ## How to Work with This Project
 
 ### 1. **Always Check Context First**
+
 Before starting any task, review:
+
 ```
 - .mcp-on-rails/context.md for project-specific information
 - .mcp-on-rails/prompts/[relevant-area].md for specialized guidance
 ```
 
 ### 2. **Multi-Agent Coordination**
+
 For complex features that span multiple areas:
+
 1. Start with the **Architect** role to plan the implementation
 2. Break down tasks for appropriate specialists
 3. Ensure consistency across all components
 4. Always include comprehensive tests
 
 ### 3. **Rails Best Practices**
+
 Always follow:
+
 - Rails conventions and naming patterns
 - RESTful design principles
 - Security best practices
@@ -167,6 +197,7 @@ Always follow:
 - Comprehensive test coverage
 
 ### 4. **Code Quality Standards**
+
 - Write clean, readable, and maintainable code
 - Follow Ruby and Rails style guides
 - Include proper documentation and comments
@@ -176,6 +207,7 @@ Always follow:
 ## Implementation Workflow
 
 ### For New Features:
+
 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
@@ -196,6 +228,7 @@ Always follow:
 11. **📝 Update**: Mark tasks complete in `tasks.md` with ✅ and timestamp
 
 ### For Bug Fixes:
+
 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
@@ -205,6 +238,7 @@ Always follow:
 7. **📝 Document**: Update specs and relevant documentation
 
 ### For Refactoring:
+
 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
@@ -217,18 +251,21 @@ Always follow:
 ## Special Considerations
 
 ### Security First
+
 - Always validate user input
 - Implement proper authentication/authorization
 - Follow Rails security guidelines
 - Use strong parameters and CSRF protection
 
 ### Performance Matters
+
 - Optimize database queries (avoid N+1)
 - Use appropriate caching strategies
 - Monitor and profile performance
 - Consider background processing for heavy tasks
 
 ### Test Everything
+
 - Write tests before implementing features (TDD)
 - Ensure high test coverage
 - Include integration and system tests
@@ -253,6 +290,7 @@ When asked to help with Rails development:
 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

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

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

metadata

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