Automate Rails controller design with RESTful actions and strong parameters.
npx skills add https://github.com/pelletencate/iron-horse --skill controllers-pelletencate
Please help me install this Agent Skill. Skill: controllers Source: https://github.com/pelletencate/iron-horse/tree/main/skills/controllers Command: npx skills add https://github.com/pelletencate/iron-horse --skill controllers-pelletencate
Build robust and maintainable Rails controllers that adhere to RESTful conventions, strong parameters, and a lean architecture.
Create a new RESTful controller, wire a resource route, and start refactoring logic into services while applying strong parameters.
High-intent search queries and answers about installing and using this skill.
To build skinny Rails controllers, delegate business logic to models or services while keeping HTTP concerns in the controller. This ensures standard RESTful actions like index, show, new, create, edit, update, and destroy remain maintainable and lean.
Implementing strong parameters in Rails controllers requires explicit parameter whitelisting to prevent mass-assignment vulnerabilities. This technique consistently filters user input, ensuring only permitted attributes are passed to your models during CRUD operations.
Handling nested resources and concerns in Rails controllers involves scalable composition of related resources. Using controller concerns allows you to share reusable RESTful patterns across multiple resources, maintaining a clean architecture.
Yes, you can build API-first Rails controllers using established patterns for API endpoints and versioning. This approach maintains RESTful routing and strong parameter enforcement while serving structured API responses.
Delegating business logic to services supports skinny controller architecture by isolating complex operations from both HTTP concerns and database persistence. This separation keeps Rails controllers clean and models focused on data integrity.
You need controller concerns in a Rails application when you want to extract and share reusable RESTful patterns across multiple resources. This approach prevents code duplication and maintains a clean, conventional routing structure.
hschneEnforce idiomatic Rails conventions across models, controllers, migrations, and routing.
joshyorkoBuild fat Rails models that encapsulate domain logic with concerns.
adelabdelgawadMap Leptos domain errors to HTTP responses and client messages.
kubiyabotSend arbitrary HTTP requests to REST and GraphQL APIs.
