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
93%
Does it follow best practices?
Impact
96%
1.77xAverage score across 41 eval scenarios
Passed
No known issues
BOUNDARY_GUIDE.mdskills/testing/triage-bug/
Bug Triage Boundary Guide
Maps common bug shapes to the highest-value first failing spec.
| Bug shape | Likely first spec | Path |
|---|---|---|
| Wrong status code, params handling, JSON payload | Request spec | spec/requests/ |
| Invalid state transition, validation, calculation | Model or service spec | spec/models/ or spec/services/ |
| Async side effect missing or duplicated | Job spec | spec/jobs/ |
| Engine routing/install/generator regression | Engine spec | Dummy app path |
| Third-party mapping/parsing issue | Integration or client-layer spec | spec/services/module_name/ |
Diagnosing the Right Layer
- HTTP symptoms (wrong status, wrong JSON shape, redirect loops): start at request level
- Data symptoms (wrong value saved, wrong validation message): start at model or service
- Timing symptoms (missing email, job not enqueued): start at job or service spec
- Engine symptoms (routes not found, generator broke): use dummy app request spec
When the Boundary Is Unclear
- Write the spec at the highest visible symptom boundary first.
- Run it — if it fails for the wrong reason (e.g., factory error), move down a layer.
- The correct boundary is where the failure message directly names the missing behavior.
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
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
mcp_server
skills
api
generate-api-collection
implement-graphql
code-quality
apply-code-conventions
apply-stack-conventions
assets
snippets
code-review
refactor-code
respond-to-review
review-architecture
security-check
context
load-context
setup-environment
ddd
define-domain-language
model-domain
review-domain-boundaries
engines
create-engine
create-engine-installer
document-engine
extract-engine
release-engine
review-engine
test-engine
upgrade-engine
infrastructure
implement-background-job
implement-hotwire
optimize-performance
review-migration
seed-database
version-api
orchestration
skill-router
patterns
create-service-object
implement-calculator-pattern
write-yard-docs
planning
create-prd
generate-tasks
plan-tickets
testing
plan-tests
test-service
triage-bug
write-tests
workflows