igmarin/rails-agent-skills

Curated library of 39 AI agent skills for Ruby on Rails development. Organized by category: planning, testing, code-quality, ddd, engines, infrastructure, api, patterns, context, orchestration, and workflows. Includes 5 callable workflow skills (rails-tdd-loop, rails-review-flow, rails-setup-flow, rails-quality-flow, rails-engines-flow) for complete development cycles. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and TDD automation.

1.20x

Quality

98%

Does it follow best practices?

Impact

95%

1.20x

Average score across 35 eval scenarios

Securityby

Passed

No known issues

Workflow: Discovery & Context (00)

Name: igmarin/rails-agent-skills
Rating: 95.37 (1 reviews)
Author: igmarin

When to use: New to a project, need to understand the codebase, or setting up development environment.

Main Flow: New Developer on Project

graph TB
    subgraph Context [🔍 Phase 1: Understand]
        direction TB
        A[New to project] --> B[rails-context-engineering]
        B --> C{Understood?}
        C -- No --> B
    end

    subgraph Setup [⚙️ Phase 2: Setup]
        direction TB
        C -- Yes --> D[rails-project-onboarding]
        D --> E{Ready?}
        E -- No --> D
    end

    E -- Yes --> F((Start Development))

    %% Styling
    style Context fill:#f5f5f5,stroke:#333,stroke-dasharray: 5 5
    style Setup fill:#e1f5fe,stroke:#01579b
    style C fill:#ffd54f
    style E fill:#ffd54f
    style F fill:#e8f5e9,stroke:#1b5e20,stroke-width:3px

Step 1: rails-context-engineering

Goal: Load the minimum context needed before writing code, tests, or PRDs.

What it does:

Inspects db/schema.rb — data structure
Reads config/routes.rb — HTTP surface
Finds neighboring models, controllers, services
Reads existing factories and specs
Detects ambiguities between requirements and code

Output: Context Summary posted before any code proposal.

When to invoke:

"Before I code on this, what's the existing pattern?"
"Where is this defined in the codebase?"
"Match existing style"

Step 2: rails-project-onboarding (NEW)

Goal: Complete development environment setup.

Onboarding Checklist

Repository cloned and structure understood
Docker / docker-compose configured (if applicable)
Environment variables set up (.env, credentials)
Database created, migrated, seeded
Test suite running locally
Linters installed and configured
IDE/Editor configured (Ruby LSP, plugins)
Git hooks installed (pre-commit, etc.)
Documentation read (README, ARCHITECTURE.md)

Standard Rails App Structure

app/
├── controllers/      # HTTP layer, thin
├── models/          # Domain logic + persistence
├── services/        # Business operations
├── jobs/            # Background processing
├── views/           # ERB/HAML + Hotwire
└── helpers/         # View utilities

config/
├── routes.rb        # Routing table
└── initializers/    # Gem configs

spec/ or test/
├── models/          # Unit tests
├── requests/        # Integration tests
├── services/        # Service tests
└── system/          # E2E tests

docs/
├── architecture.md  # System design
├── api/             # API documentation
└── workflows/       # This directory

Database Setup Commands

# Standard setup
bin/rails db:create
bin/rails db:migrate
bin/rails db:seed

# Test environment
RAILS_ENV=test bin/rails db:create db:migrate

# With Docker
docker-compose up -d db
docker-compose run web bin/rails db:create db:migrate db:seed

Environment Variables Checklist

Variable	Purpose	Where to define
`DATABASE_URL`	DB connection	`.env` / env vars
`REDIS_URL`	Cache/Sidekiq	`.env`
`RAILS_MASTER_KEY`	Encrypted credentials	env var only (never in repo)
`AWS_` / `S3_`	Storage	credentials.yml.enc
`SENDGRID_*`	Email	credentials.yml.enc
`STRIPE_*`	Payments	credentials.yml.enc

Integration with Next Steps

If you need...	Next skill
To plan a feature	`create-prd` → planning
To start coding	`rails-tdd-slices` → development
To fix a bug	`rails-bug-triage` → development#bug-fix
To configure CI/CD	(roadmap — `rails-ci-cd-setup`, see setup)

Hard Gate: No Code Without Context

DO NOT write implementation code before running rails-context-engineering.
ALWAYS post the Context Summary and resolve any ambiguities first.

Skills in this Workflow

Skill	Description	Trigger words
rails-context-engineering	Load context before coding	"load context", "before I code", "match existing style"
rails-project-onboarding	Dev environment setup	"onboarding", "new dev", "setup project", "Docker"

evals

mcp_server

skills

README.md

tile.json