rails

Enforce idiomatic Rails conventions across models, controllers, migrations, and routing.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill rails-hschne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rails
Source: https://github.com/hschne/pi-stuff/tree/main/skills/rails
Command: npx skills add https://github.com/hschne/pi-stuff --skill rails-hschne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates inconsistent Rails code, misplaced business logic, and deviation from framework defaults that lead to hard-to-maintain, fragile applications.

Core Features & Use Cases

  • Full-stack Rails convention guidance: Covers architecture, models, controllers, database migrations, testing, Hotwire, Inertia, routing, and i18n for end-to-end Rails development.
  • Code review and refactoring support: Provides concrete rules to identify anti-patterns like overly broad models, misplaced business logic in controllers, and unnecessary abstractions during reviews or refactors.
  • Use Case: Use this when building a new Rails app, refactoring legacy Rails code, or reviewing pull requests for Rails projects to ensure all code adheres to Rails defaults and domain-driven best practices.

Quick Start

Use the rails skill to review your Rails app's controller and model structure for adherence to framework conventions and proper layer separation.

Frequently Asked Questions about rails

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce idiomatic Rails conventions when refactoring legacy code?

Review Rails controller and model structure to identify anti-patterns like overly broad models or misplaced business logic, applying concrete conventions for proper layer separation and adherence to framework defaults.

What is the best way to structure Rails models and controllers for maintainability?

The best way to structure Rails models and controllers for maintainability is to follow domain-driven best practices, avoiding overly broad models and misplaced business logic in controllers by adhering strictly to framework defaults and proper layer separation.

Does this Rails convention guidance cover Hotwire and Inertia integration?

Yes, this Rails convention guidance covers Hotwire usage and Inertia integration, providing concrete conventions for both alongside architecture, database migrations, routing, testing, and i18n implementation for end-to-end development.

How do I review pull requests for Rails anti-patterns and unnecessary abstractions?

Review pull requests for Rails anti-patterns by applying concrete rules to identify misplaced business logic in controllers, overly broad models, and unnecessary abstractions, ensuring all code adheres to framework defaults and domain-driven best practices.

Can I use these Rails conventions for designing database schemas and routing?

Yes, you can use these Rails conventions for designing database schemas and routing, as the guidance applies to all Rails development tasks including migrations and routing to enforce idiomatic practices and eliminate inconsistent application code.