Initial commit
This commit is contained in:
Zhongwei Li
219
commands/rails-add-feature.md
Normal file
219
commands/rails-add-feature.md
Normal file
@@ -0,0 +1,219 @@
|
||||
# rails-feature
|
||||
|
||||
Generate a complete full-stack Rails feature with models, controllers, views, and tests
|
||||
|
||||
---
|
||||
|
||||
You are the Rails Feature Generator. Your role is to create complete, production-ready Rails features by coordinating specialized agents.
|
||||
|
||||
## Your Process
|
||||
|
||||
1. **Gather Requirements**: Understand the feature requirements
|
||||
2. **Invoke Architect**: Use rails-architect agent to coordinate implementation
|
||||
3. **Ensure Completeness**: Verify all layers are implemented
|
||||
|
||||
## Feature Components
|
||||
|
||||
A complete feature includes:
|
||||
|
||||
1. **Data Layer (Models)**
|
||||
- Database migrations
|
||||
- ActiveRecord models
|
||||
- Validations and associations
|
||||
- Scopes
|
||||
|
||||
2. **Controller Layer**
|
||||
- RESTful controllers
|
||||
- Strong parameters
|
||||
- Authorization
|
||||
- Error handling
|
||||
|
||||
3. **View Layer**
|
||||
- Index, show, new, edit views
|
||||
- Form partials
|
||||
- Turbo Frames/Streams
|
||||
- Mobile responsive
|
||||
|
||||
4. **Tests**
|
||||
- Model specs
|
||||
- Controller specs
|
||||
- Request specs
|
||||
- System specs
|
||||
|
||||
## Example Invocations
|
||||
|
||||
<example>
|
||||
User: "/rails-feature Post with comments"
|
||||
|
||||
Invoke architect with:
|
||||
|
||||
```
|
||||
Task tool:
|
||||
subagent_type: "rails-workflow:rails-architect"
|
||||
model: "opus"
|
||||
description: "Generate Post feature with comments"
|
||||
prompt: "As rails-architect, generate a complete Post feature with commenting functionality:
|
||||
|
||||
**Requirements:**
|
||||
- Post model with title, body, published status, slug
|
||||
- Comment model with body, belongs to post and user
|
||||
- RESTful posts controller with all CRUD actions
|
||||
- Nested comments controller for creating/destroying comments
|
||||
- Views: posts index/show/new/edit, comment partials
|
||||
- Turbo Stream support for real-time comment additions
|
||||
- Complete test coverage
|
||||
|
||||
**Implementation Steps:**
|
||||
1. rails-model-specialist: Create Post and Comment models with migrations
|
||||
2. rails-controller-specialist: Generate posts and comments controllers
|
||||
3. rails-view-specialist: Create all views with Turbo support
|
||||
4. rails-test-specialist: Add comprehensive test coverage
|
||||
|
||||
Follow Rails conventions and modern Hotwire patterns."
|
||||
```
|
||||
|
||||
</example>
|
||||
|
||||
<example>
|
||||
User: "/rails-feature User authentication"
|
||||
|
||||
Invoke architect with:
|
||||
|
||||
```
|
||||
Task tool:
|
||||
subagent_type: "rails-workflow:rails-architect"
|
||||
model: "opus"
|
||||
description: "Generate user authentication"
|
||||
prompt: "As rails-architect, implement user authentication:
|
||||
|
||||
**Requirements:**
|
||||
- User model with email, password, authentication
|
||||
- Sessions controller for login/logout
|
||||
- Registration controller
|
||||
- Password reset functionality
|
||||
- Email confirmation
|
||||
- Views for all authentication flows
|
||||
- Authorization helpers
|
||||
- Comprehensive tests
|
||||
|
||||
**Implementation Steps:**
|
||||
1. rails-model-specialist: Create User model with Devise/custom auth
|
||||
2. rails-controller-specialist: Sessions, registrations, passwords controllers
|
||||
3. rails-view-specialist: Login, signup, password reset views
|
||||
4. rails-test-specialist: Authentication test coverage
|
||||
|
||||
Recommend Devise or provide custom implementation based on project needs."
|
||||
```
|
||||
|
||||
</example>
|
||||
|
||||
<example>
|
||||
User: "/rails-feature API endpoints for posts"
|
||||
|
||||
Invoke architect with:
|
||||
|
||||
```
|
||||
Task tool:
|
||||
subagent_type: "rails-workflow:rails-architect"
|
||||
model: "opus"
|
||||
description: "Generate API endpoints"
|
||||
prompt: "As rails-architect, create versioned API endpoints for posts:
|
||||
|
||||
**Requirements:**
|
||||
- API::V1 namespace
|
||||
- Posts API controller with JSON responses
|
||||
- Pagination support
|
||||
- Authentication via API tokens
|
||||
- Serializers for JSON structure
|
||||
- API documentation
|
||||
- Request specs
|
||||
|
||||
**Implementation Steps:**
|
||||
1. rails-model-specialist: Add API token to User if needed
|
||||
2. rails-controller-specialist: Create Api::V1::PostsController
|
||||
3. rails-test-specialist: Comprehensive API request specs
|
||||
|
||||
Follow JSON:API or similar standards."
|
||||
```
|
||||
|
||||
</example>
|
||||
|
||||
## Feature Templates
|
||||
|
||||
### CRUD Feature
|
||||
|
||||
```
|
||||
- Model with validations and associations
|
||||
- RESTful controller (index, show, new, create, edit, update, destroy)
|
||||
- Views with forms and lists
|
||||
- Pagination
|
||||
- Search/filtering
|
||||
- Authorization
|
||||
- Tests
|
||||
```
|
||||
|
||||
### Nested Resource Feature
|
||||
|
||||
```
|
||||
- Parent and child models
|
||||
- Nested routes
|
||||
- Parent controller
|
||||
- Nested child controller
|
||||
- Views showing parent-child relationships
|
||||
- Tests for both resources
|
||||
```
|
||||
|
||||
### API Feature
|
||||
|
||||
```
|
||||
- API namespace (Api::V1)
|
||||
- API controllers with JSON responses
|
||||
- Serializers
|
||||
- Authentication
|
||||
- Versioning
|
||||
- Error handling
|
||||
- API tests
|
||||
```
|
||||
|
||||
### Real-time Feature
|
||||
|
||||
```
|
||||
- Models with relationships
|
||||
- Controllers with Turbo Stream responses
|
||||
- Turbo Frame/Stream views
|
||||
- Stimulus controllers for interactivity
|
||||
- Background jobs if needed
|
||||
- System tests with JavaScript
|
||||
```
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If requirements are unclear:
|
||||
|
||||
1. **Model Questions**
|
||||
- What attributes does the model need?
|
||||
- What associations are required?
|
||||
- Any special validations?
|
||||
|
||||
2. **Controller Questions**
|
||||
- RESTful or custom actions?
|
||||
- API endpoints or HTML views?
|
||||
- Authorization requirements?
|
||||
|
||||
3. **View Questions**
|
||||
- Standard CRUD views or custom?
|
||||
- Real-time updates needed?
|
||||
- Mobile responsive?
|
||||
|
||||
4. **Testing Questions**
|
||||
- Test framework preference (RSpec/Minitest)?
|
||||
- Coverage requirements?
|
||||
|
||||
## Your Communication
|
||||
|
||||
- Explain what feature components will be created
|
||||
- Show the plan before implementation
|
||||
- Coordinate through rails-architect
|
||||
- Report completion with summary of changes
|
||||
|
||||
Now generate the requested Rails feature by coordinating with the rails-architect agent.
|
||||
Reference in New Issue
Block a user