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
99%
Does it follow best practices?
Impact
98%
1.38xAverage score across 26 eval scenarios
Passed
No known issues
The platform team at Meridian Financial needs a reusable audit logging module that multiple internal Rails applications can mount. Every significant user action (record creation, updates, deletions) must be stored in an audit_events table with the actor, resource type, resource ID, action, and a JSON payload of changed attributes. The module needs to work across several host applications that each have their own User model (some call it Employee, some call it User), so the engine must not hard-code any host model class names.
The team intends to open-source this engine eventually, so clean boundaries between the engine and host apps are essential. Host applications should be able to configure the engine once in an initializer and have it ready to use. The audit table needs to live in each host app's database — migrations should not be applied automatically; they should be installable on-demand by the host app team.
Your task is to scaffold the minimal viable structure of a AuditTrail Rails engine. You do not need to implement full business logic — focus on the correct engine architecture and host integration design.
Produce the following files (stubs with correct structure are acceptable, full implementations are welcome):
lib/audit_trail.rb — root require filelib/audit_trail/version.rb — version constantlib/audit_trail/configuration.rb — Configuration classlib/audit_trail/engine.rb — Engine classconfig/routes.rb — engine routes (can be minimal/empty)app/models/audit_trail/audit_event.rb — AuditEvent model stubdb/migrate/TIMESTAMP_create_audit_trail_audit_events.rb — migration file (use any timestamp)spec/dummy/config/routes.rb — dummy app routes mounting the enginespec/requests/audit_trail/audit_events_spec.rb — at least one request spec stubAlso produce:
host_contract.md — a document describing: what the host app must configure, what the engine exposes, and which extension points are supportedapi-rest-collection
create-prd
ddd-boundaries-review
ddd-rails-modeling
ddd-ubiquitous-language
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
generate-tasks
mcp_server
rails-architecture-review
rails-background-jobs
rails-bug-triage
rails-code-conventions
rails-code-review
rails-engine-compatibility
rails-engine-docs
rails-engine-extraction
rails-engine-installers
rails-engine-release
rails-engine-reviewer
rails-engine-testing
rails-graphql-best-practices
rails-migration-safety
rails-review-response
rails-security-review
rails-skills-orchestrator
rails-stack-conventions
rails-tdd-slices
refactor-safely
rspec-best-practices
rspec-service-testing
ruby-service-objects
strategy-factory-null-calculator
ticket-planning
yard-documentation