backend

Implement Rails backend code for business logic and application workflows.

2|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/mattszein/pro-rails --skill backend-mattszein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend
Source: https://github.com/mattszein/pro-rails/tree/main/.claude/skills/backend
Command: npx skills add https://github.com/mattszein/pro-rails --skill backend-mattszein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement and maintain the server-side behavior of a Rails application without drifting from the project's established patterns. It is designed for teams that need reliable business logic, clean architecture, and consistent handling of data, permissions, and background work.

Core Features & Use Cases

  • Rails business logic: Build models, controllers, interactors, services, and migrations that match the repository's conventions.
  • Production workflows: Implement authorization checks, background jobs, broadcasts, I18n strings, and state transitions in a maintainable way.
  • Real-world use cases: Add an admin action, create a new workflow, enforce validation rules, or wire up a job-driven feature with safe retries and idempotent behavior.

Quick Start

Ask for the Rails backend code needed to add a new feature, including the model, controller, interactor, job, and I18n updates.

Frequently Asked Questions about backend

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

FAQPage Schema
How do I implement Rails business logic for models and controllers without breaking project conventions?

To implement Rails business logic cleanly, build models, controllers, interactors, and services that strictly adhere to repository conventions, ensuring clean architecture and consistent data handling.

What's the best way to set up idempotent background jobs in Rails?

Setting up idempotent Rails jobs requires implementing safe retries and separating side effects from model state transitions, ensuring background workflows execute reliably without duplicate data modifications.

How do you handle authorization guards and validation patterns in a Rails backend?

Handling authorization guards and validation patterns in a Rails backend involves enforcing policies and validation rules within controllers and services to secure application workflows and maintain data integrity.

Can I generate Rails migrations and I18n strings for a new feature workflow?

Yes, you can generate Rails migrations and I18n strings for new features, wiring up complete workflows that include state transitions, broadcasts, and internationalization updates.

When do I need interactors and services in a Rails application architecture?

You need interactors and services in a Rails application to encapsulate complex business workflows, maintaining a clean architecture by separating side effects and execution logic from models and controllers.