Curated library of 28 public AI agent skills for Ruby on Rails development. Organized by category: testing, code-quality, engines, infrastructure, api, and context. Covers code review, architecture, security, testing (RSpec), engines, Hotwire, and TDD automation. Shared Ruby skills (YARD docs, DDD, service objects) have moved to ruby-core-skills. Repository agents remain documented in GitHub but are intentionally excluded from the Tessl tile.
93
95%
Does it follow best practices?
Impact
93%
1.78xAverage score across 28 eval scenarios
Passed
No known issues
When to use: New to a project, need to understand the codebase, or setting up development environment.
graph TB
subgraph Context [🔍 Phase 1: Understand]
direction TB
A[New to project] --> B[load-context]
B --> C{Understood?}
C -- No --> B
end
subgraph Setup [⚙️ Phase 2: Setup]
direction TB
C -- Yes --> D[setup-environment]
D --> E{Ready?}
E -- No --> D
end
E -- Yes --> F((Start Development))
%% Styling
style Context fill:#f5f5f5,stroke:#333,stroke-dasharray: 5 5
style Setup fill:#e1f5fe,stroke:#01579b
style C fill:#ffd54f
style E fill:#ffd54f
style F fill:#e8f5e9,stroke:#1b5e20,stroke-width:3pxGoal: Load the minimum context needed before writing code, tests, or PRDs.
What it does:
db/schema.rb — data structureconfig/routes.rb — HTTP surfaceOutput: Context Summary posted before any code proposal.
When to invoke:
Goal: Complete development environment setup.
app/
├── controllers/ # HTTP layer, thin
├── models/ # Domain logic + persistence
├── services/ # Business operations
├── jobs/ # Background processing
├── views/ # ERB/HAML + Hotwire
└── helpers/ # View utilities
config/
├── routes.rb # Routing table
└── initializers/ # Gem configs
spec/ or test/
├── models/ # Unit tests
├── requests/ # Integration tests
├── services/ # Service tests
└── system/ # E2E tests
agents/ # Callable agents
├── tdd/ # TDD agent
└── ...
docs/
├── architecture.md # System design
└── api/ # API documentation# Standard setup
bin/rails db:create
bin/rails db:migrate
bin/rails db:seed
# Test environment
RAILS_ENV=test bin/rails db:create db:migrate
# With Docker
docker-compose up -d db
docker-compose run web bin/rails db:create db:migrate db:seed| Variable | Purpose | Where to define |
|---|---|---|
DATABASE_URL | DB connection | .env / env vars |
REDIS_URL | Cache/Sidekiq | .env |
RAILS_MASTER_KEY | Encrypted credentials | env var only (never in repo) |
AWS_* / S3_* | Storage | credentials.yml.enc |
SENDGRID_* | credentials.yml.enc | |
STRIPE_* | Payments | credentials.yml.enc |
| If you need... | Next skill |
|---|---|
| To start coding | plan-tests → development |
| To fix a bug | triage-bug → development#bug-fix |
| To configure CI/CD | (roadmap — setup-ci-cd, see setup) |
DO NOT write implementation code before running load-context.
ALWAYS post the Context Summary and resolve any ambiguities first.| Skill | Description | Trigger words |
|---|---|---|
| load-context | Load context before coding | "load context", "before I code", "match existing style" |
| setup-environment | Dev environment setup | "onboarding", "new dev", "setup project", "Docker" |
agents
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
skills
api
generate-api-collection
implement-graphql
code-quality
apply-code-conventions
apply-stack-conventions
assets
snippets
code-review
refactor-code
review-architecture
security-check
context
load-context
setup-environment
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
testing
plan-tests
test-service
write-tests