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.

1.77x

Quality

93%

Does it follow best practices?

Impact

96%

1.77x

Average score across 41 eval scenarios

Securityby

Passed

No known issues

First Slice Template

Name: igmarin/rails-agent-skills
Rating: 95.72 (1 reviews)
Author: igmarin

Use this template when the task is to choose the first failing spec.

## Behavior

[User-visible behavior or invariant to prove]

## Boundary Decision

| Candidate | Keep/Reject | Reason |
| --- | --- | --- |
| Request spec | Keep/Reject | [HTTP/routing/serialization risk?] |
| Service spec | Keep/Reject | [orchestration boundary?] |
| Model spec | Keep/Reject | [domain invariant?] |
| Job spec | Keep/Reject | [async behavior?] |
| System spec | Keep/Reject | [browser-only risk?] |

## Opening Gate

- Spec path: `spec/...`
- First focused command: `bundle exec rspec spec/...`
- Expected RED reason: `[feature missing, not broken setup]`

```ruby
it 'proves one observable behavior' do
  # exactly one opening example
end
```

## Follow-up Coverage

- [ ] [Additional case after the opening gate is green]

## HARD-GATE Design Checkpoint

| Question | Answer |
| --- | --- |
| Does this test cover the right behavior? | Yes/No |
| Is the boundary correct? | Yes/No |
| Are the most important edge cases represented or listed for follow-up? | Yes/No |
| Is the failure reason correct? | Yes/No |