CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/rails-agent-skills

Curated library of AI agent skills for Ruby on Rails development. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and workflow automation.

98

1.38x
Quality

99%

Does it follow best practices?

Impact

98%

1.38x

Average score across 26 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

reference.mdrails-engine-author/

Rails Engine Skeleton

Use this as a baseline when the user asks to create a new engine from scratch.

File Layout

my_engine/
  app/
    controllers/my_engine/application_controller.rb
    models/my_engine/
    services/my_engine/
  config/
    routes.rb
  lib/
    my_engine.rb
    my_engine/version.rb
    my_engine/configuration.rb
    my_engine/engine.rb
  spec/
    dummy/
    lib/
    requests/
    services/
  my_engine.gemspec

Baseline Files

lib/my_engine.rb

require "my_engine/version"
require "my_engine/configuration"
require "my_engine/engine"

module MyEngine
  class << self
    attr_writer :configuration

    def configuration
      @configuration ||= Configuration.new
    end

    def configure
      yield(configuration)
    end
  end
end

lib/my_engine/configuration.rb

module MyEngine
  class Configuration
    attr_accessor :user_class, :audit_events

    def initialize
      @user_class = "User"
      @audit_events = false
    end
  end
end

lib/my_engine/engine.rb

module MyEngine
  class Engine < ::Rails::Engine
    isolate_namespace MyEngine

    initializer "my_engine.configuration" do
      config.my_engine = MyEngine.configuration
    end

    config.to_prepare do
      # Reload-safe host integration only.
    end
  end
end

config/routes.rb

MyEngine::Engine.routes.draw do
  root to: "home#index"
end

app/controllers/my_engine/application_controller.rb

module MyEngine
  class ApplicationController < ActionController::Base
  end
end

Generator Guidance

If the engine needs host installation steps, prefer generators for:

  • copying migrations
  • adding initializer config
  • seeding permissions or setup data
  • creating mount routes when appropriate

Generators should be safe to run more than once.

Testing Baseline

Start with:

  • one configuration spec
  • one request or routing spec through the engine
  • one dummy-app integration check
  • one service spec for a public engine object

Escalation Rules

Do not introduce these unless the user asks or the problem clearly needs them:

  • host app model assumptions hardcoded as constants
  • monkey patches
  • engine-wide global state beyond a single configuration object
  • database writes inside initializers

rails-engine-author

reference.md

SKILL.md

README.md

tile.json