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.
95
98%
Does it follow best practices?
Impact
95%
1.20xAverage score across 35 eval scenarios
Passed
No known issues
Step-by-step install and verification for the rails-agent-skills repository on each supported platform.
There are two primary methods for making skills available to your AI assistant:
Claude Code discovers skills from ~/.claude/skills/ and loads ~/.claude/CLAUDE.md automatically in every session. Two methods are available.
# 1. Clone the repo (once per machine)
git clone git@github.com:igmarin/rails-agent-skills.git ~/skills/rails-agent-skills
# 2. Global instructions (loaded in every session, across all projects)
ln -sf ~/skills/rails-agent-skills/CLAUDE.md ~/.claude/CLAUDE.md
# 3. Skills (adds each skill individually — safe, preserves any existing skills)
mkdir -p ~/.claude/skills
for dir in ~/skills/rails-agent-skills/*/; do
ln -sf "$dir" ~/.claude/skills/
doneOpen a new session and run /skills — all skills will appear.
Updating:
cd ~/skills/rails-agent-skills && git pull
# Add any new skills that were added to the repo
for dir in ~/skills/rails-agent-skills/*/; do
ln -sf "$dir" ~/.claude/skills/
doneThe MCP server gives Claude Code on-demand access to every skill, doc, and workflow without loading the full repo into context.
Open ~/.claude/mcp.json (global) or add to .mcp.json at the repo root (project-level, already populated if you cloned the repo). The project-level .mcp.json is auto-loaded by Claude Code when you open the repo as a project.
Global setup (~/.claude/mcp.json):
{
"mcpServers": {
"rails-agent-skills": {
"type": "stdio",
"command": "bundle",
"args": ["exec", "ruby", "mcp_server/server.rb"],
"cwd": "/YOUR/PATH/TO/rails-agent-skills",
"env": {
"BUNDLE_GEMFILE": "/YOUR/PATH/TO/rails-agent-skills/mcp_server/Gemfile"
}
}
}
}Replace /YOUR/PATH/TO/rails-agent-skills with your actual clone path, then install dependencies:
cd /YOUR/PATH/TO/rails-agent-skills/mcp_server && bundle installStart a new Claude Code session. The rails-agent-skills MCP server will appear in your tools list.
Repeat the installation steps for whichever method you prefer.
# Clone the repo (once per machine)
git clone git@github.com:igmarin/rails-agent-skills.git ~/skills/rails-agent-skills
# Cursor
ln -s ~/skills/rails-agent-skills ~/.cursor/skills/rails-agent-skills
# Windsurf
ln -s ~/skills/rails-agent-skills ~/.windsurf/skills/rails-agent-skillsRestart your IDE for changes to take effect.
Updating: git pull in the repo — symlinks reflect changes immediately.
Clone the repo and install dependencies:
git clone git@github.com:igmarin/rails-agent-skills.git ~/skills/rails-agent-skills
cd ~/skills/rails-agent-skills/mcp_server && bundle installAdd the server to the appropriate config file for your IDE:
Windsurf (~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": {
"rails-agent-skills": {
"type": "stdio",
"command": "bundle",
"args": ["exec", "ruby", "mcp_server/server.rb"],
"cwd": "/YOUR/PATH/TO/rails-agent-skills",
"env": {
"BUNDLE_GEMFILE": "/YOUR/PATH/TO/rails-agent-skills/mcp_server/Gemfile"
}
}
}
}Cursor (~/.cursor/mcp.json or Settings → MCP):
{
"mcpServers": {
"rails-agent-skills": {
"type": "stdio",
"command": "bundle",
"args": ["exec", "ruby", "mcp_server/server.rb"],
"cwd": "/YOUR/PATH/TO/rails-agent-skills",
"env": {
"BUNDLE_GEMFILE": "/YOUR/PATH/TO/rails-agent-skills/mcp_server/Gemfile"
}
}
}
}Reload or restart your IDE. The rails-agent-skills server will appear in the MCP panel.
Why
BUNDLE_GEMFILE? The server'sGemfilelives insidemcp_server/, not at the repo root. This env var tells Bundler exactly which Gemfile to use regardless of working directory.
# Clone the repo (once per machine)
git clone git@github.com:igmarin/rails-agent-skills.git ~/skills/rails-agent-skills
# Symlink GEMINI.md to the Gemini CLI global config directory
ln -s ~/skills/rails-agent-skills/GEMINI.md ~/.gemini/GEMINI.mdRequires starting a new session to pick up changes.
# Clone directly into Codex skills
mkdir -p ~/.codex/skills
git clone git@github.com:igmarin/rails-agent-skills.git ~/.codex/skills/rails-agent-skills
# Or symlink if you already have the repo cloned
ln -s ~/skills/rails-agent-skills ~/.codex/skills/rails-agent-skillsWindows (PowerShell):
New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.codex\skills"
git clone git@github.com:igmarin/rails-agent-skills.git "$env:USERPROFILE\.codex\skills\rails-agent-skills"Updating: cd ~/.codex/skills/rails-agent-skills && git pull
The MCP Server is the recommended method for RubyMine. The symlink approach is not reliably supported for custom skill injection.
Cmd+,) → navigate to Tools → AI Assistant → Model Context Protocol.ruby ~/skills/rails-agent-skills/mcp_server/server.rbThe session-start hook automatically injects the rails-skills-orchestrator bootstrap skill at the beginning of each session. Defined in hooks/hooks.json, executed by hooks/session-start.
For Claude Code, ~/.claude/CLAUDE.md (symlinked from this repo) is the primary mechanism. The session-start hook is retained for completeness and future marketplace support, but is not required for local installs.
| Platform | Context injection field |
|---|---|
| Claude Code | hookSpecificOutput.additionalContext |
| Cursor / Others | additional_context |
| Issue | Solution |
|---|---|
/skills shows "No skills found" (Claude Code) | Re-run the for dir loop to create per-skill symlinks in ~/.claude/skills/ |
| Skills not available (Claude Code) | Verify symlink: ls -la ~/.claude/CLAUDE.md |
| Skills not discovered (Cursor/Codex) | Check symlink/path and restart the platform |
| Hook not firing | Verify hooks/session-start is executable: chmod +x hooks/session-start |
| Changes not picked up (Claude Code) | Run git pull in the repo and start a new session |
| Changes not picked up (Cursor) | Run git pull in the repo; symlinks reflect changes immediately |
| Wrong platform behavior | Verify the correct plugin config for your platform (.claude-plugin/ vs .cursor-plugin/) |
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
mcp_server
skills
api
api-rest-collection
rails-graphql-best-practices
code-quality
rails-architecture-review
rails-code-conventions
rails-code-review
rails-review-response
rails-security-review
rails-stack-conventions
assets
snippets
refactor-safely
context
rails-context-engineering
rails-project-onboarding
ddd
ddd-boundaries-review
ddd-rails-modeling
ddd-ubiquitous-language
engines
rails-engine-compatibility
rails-engine-docs
rails-engine-extraction
rails-engine-installers
rails-engine-release
rails-engine-reviewer
rails-engine-testing
infrastructure
rails-api-versioning
rails-background-jobs
rails-database-seeding
rails-frontend-hotwire
rails-migration-safety
rails-performance-optimization
orchestration
rails-skills-orchestrator
patterns
ruby-service-objects
strategy-factory-null-calculator
yard-documentation
planning
create-prd
generate-tasks
ticket-planning
testing
rails-bug-triage
rails-tdd-slices
rspec-best-practices
rspec-service-testing