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
Step-by-step guides for each stage of Rails development. Each workflow is a chain of skills executed in order.
flowchart TD
START([What do you need to do?]) --> DECISION{What stage are you at?}
DECISION -->|New project or setup| DISCOVERY[discovery]
DECISION -->|Plan feature| PLANNING[planning]
DECISION -->|Configure CI/CD or environment| SETUP[setup]
DECISION -->|Develop code| DEV[development]
DECISION -->|Review quality| QUALITY[quality]
DECISION -->|Code review| REVIEW[review]
DECISION -->|Build engine| ENGINES[engines]
DISCOVERY --> NEXT{What next?}
PLANNING --> NEXT
SETUP --> DEV
NEXT -->|Implement| DEV
NEXT -->|Done| END([PR / Merge])
DEV -->|Tests pass| YARD[write-yard-docs]
DEV -->|Need review| REVIEW
YARD --> REVIEW
REVIEW -->|Feedback received| RESPOND[respond-to-review]
RESPOND -->|Re-implement| DEV
RESPOND -->|OK| END
QUALITY --> REVIEW
ENGINES --> REVIEW| Stage | Workflow | Description | Primary Skills |
|---|---|---|---|
| Discovery | Discovery & Context | Understand codebase, project onboarding | load-context, setup-environment |
| Planning | Planning & Design | Plan features, PRD, tasks, DDD | create-prd, generate-tasks, ddd skills |
| Setup | Setup & Configuration | Configure CI/CD, environment, deploy | setup-environment (plus roadmap setup-ci-cd) |
| Development | Development | TDD development, implementation | plan-tests, testing skills, implementation |
| Quality | Code Quality | Conventions, refactoring, documentation | apply-code-conventions, refactor-code, write-yard-docs |
| Review | Review & Validation | Code review, security, architecture | code-review, security-check, review-architecture |
| Engines | Engine Development | Create and maintain Rails engines | engine skills |
This directory contains reference guides describing each stage. For executable orchestration, use the callable workflow skills in workflows/:
| Stage Doc | Callable Skill | Status |
|---|---|---|
| development.md | tdd | Active |
| review.md | review | Active |
| setup.md | setup | Active |
| quality.md | quality | Active |
| engines.md | engine | Active |
| discovery.md | (none — linear, no orchestration needed) | Doc only |
| planning.md | (none — linear, no orchestration needed) | Doc only |
When to use which: Read the stage doc to understand the full context and rationale. Invoke the callable skill when you want the agent to execute the workflow automatically.
| Situation | Workflow | Quick Entry |
|---|---|---|
| Bug fix | bug-fix | triage-bug → reproduce test → fix → verify |
| Refactoring | Refactor Safely | refactor-code → characterization tests → extract |
| Performance | Performance Optimization | optimize-performance |
| GraphQL | graphql | domain modeling → schema → TDD → security |
| Authorization | Authorization Setup | implement-authorization |
| External API | API Integration | integrate-api-client |
| Database migration | migration | plan → test → staging → production |
| Background job | background-job | design → TDD → retry config → monitoring |
New to the project?
├─ Yes → load-context → setup-environment
└─ No → What do you need to do?
Plan a feature?
├─ Yes → create-prd → generate-tasks → (plan-tickets optional)
└─ No → Implement?
Bug or refactor?
├─ Bug → triage-bug
├─ Refactor → refactor-code
└─ New feature → plan-tests → write-tests
Code type?
├─ Service → create-service-object
├─ REST API → integrate-api-client
├─ GraphQL → implement-graphql
├─ Migration → review-migration
├─ Background job → implement-background-job
└─ Engine → create-engine
Authorization/roles?
└─ implement-authorization
Performance?
└─ optimize-performanceAll code-producing workflows include this gate:
Write test → Run test → Verify it FAILS → Implement → Verify it PASSESSee details in each specific workflow.
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