CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/rails-agent-skills

Curated library of 41 public AI agent skills for Ruby on Rails development. Organized by category: planning, testing, code-quality, ddd, engines, infrastructure, api, patterns, context, and orchestration. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and TDD automation. Repository workflows remain documented in GitHub but are intentionally excluded from the Tessl tile.

95

1.77x
Quality

93%

Does it follow best practices?

Impact

96%

1.77x

Average score across 41 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

SKILL.mdskills/engines/extract-engine/

name:
extract-engine
license:
MIT
description:
Use when extracting existing Rails app code into a reusable engine. Scaffolds the engine structure, moves POROs/services/controllers incrementally, creates adapter interfaces to decouple host dependencies, and verifies regression coverage throughout each extraction slice. Trigger words: extract to engine, move feature to engine, host coupling, adapters, extraction slices, preserve behavior, incremental extraction, bounded feature.
metadata:
{"version":"1.0.0","user-invocable":"true"}

Extract Engine

Use this skill when the task is to move existing code out of a Rails app and into an engine. Prefer incremental extraction over big-bang rewrites. Preserve behavior first, then improve design.

Quick Reference

PhaseFocus
PrepIdentify bounded feature and host dependencies
LogicMove stable domain logic (POROs, services) first
SeamsAdd adapters/config for host dependencies
WebMove controllers, routes, views last

HARD-GATE

DO NOT extract and change behavior in the same step.
Extraction must preserve existing behavior; refactoring and improvements belong in a separate step after the move is complete and verified.

Core Process

  1. Identify the bounded feature to extract — one coherent responsibility.
  2. List hard dependencies on the host app (models, services, config).
  3. Define the future engine boundary and host contract.
  4. Move stable domain logic first: POROs, services, value objects, policies, query objects. Delay direct host model references, authentication, route ownership, and asset integration.
  5. Add adapters or configuration seams for host-owned dependencies. Replace hardcoded host references with config values, adapter objects, or service interfaces.
  6. Move controllers, routes, views, or jobs only after seams are clear.
  7. Keep regression coverage green throughout each slice.

Each slice must have: one coherent responsibility, minimal new public API, passing regression tests, and a clear next step.

Extended Resources

Pitfalls

PitfallWhat to do
Extracting too much at onceOne bounded slice per step; large extractions hide bugs and are hard to revert
Direct host references in engineUse adapters or config; direct constants couple engine to host internals
Behavior changes mixed with extractionPreserve behavior first; refactor only after the move is verified
Circular dependencies introducedVerify import graph before moving each slice
Dummy app passes but host contract is implicitExplicitly document and test the host app contract

Examples First slice (move PORO, no host model yet):

# Move the file into the engine and adjust the namespace
mkdir -p my_engine/app/services/my_engine
mv app/services/pricing/calculator.rb my_engine/app/services/my_engine/pricing_calculator.rb
# Before (in host app): module Pricing; class Calculator
# After (in engine):
module MyEngine
  class PricingCalculator
    def initialize(line_items)
      @line_items = line_items
    end

    def total
      @line_items.sum { |item| item.price * item.quantity }
    end
  end
end

Verify regression coverage still passes before proceeding to the next slice:

bundle exec rspec spec/services/pricing/ spec/requests/orders/

Adapter for host dependency (compact):

# config seam (compact)
module MyEngine
  def self.current_user_for(request)
    config.current_user_provider.call(request)
  end
end

# usage
OrderCreator.for_request(request) # resolves via MyEngine.current_user_for(request)
  • assets/examples.md
  • references/adapter_examples.md

Output Style

  1. Propose one small, bounded extraction slice at a time.
  2. Outline the files moving, the new boundaries, and the regression tests to run.
  3. Language — Must be in English unless explicitly requested otherwise.

Integration

SkillWhen to chain
create-engineEngine structure, host contract, namespace design after extraction
test-engineDummy app, regression tests, integration verification
refactor-codeBehavior-preserving refactors before or after extraction slices

skills

README.md

server.json

tile.json