CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/rails-agent-skills

Curated library of 39 AI agent skills for Ruby on Rails development. Organized by category: planning, testing, code-quality, ddd, engines, infrastructure, api, patterns, context, orchestration, and workflows. Includes 5 callable workflow skills (rails-tdd-loop, rails-review-flow, rails-setup-flow, rails-quality-flow, rails-engines-flow) for complete development cycles. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and TDD automation.

95

1.20x
Quality

98%

Does it follow best practices?

Impact

95%

1.20x

Average score across 35 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-25/

{
  "context": "Tests whether the agent follows a test-first development workflow: writing the spec before the implementation, documenting the expected failure before any service code is written, and explicitly planning the implementation scope before coding it.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "process_log.md exists",
      "description": "A process_log.md file is present in the workspace",
      "max_score": 5
    },
    {
      "name": "Spec content before implementation",
      "description": "In process_log.md, the section describing or quoting spec/test content appears earlier in the document than the section describing or quoting implementation code",
      "max_score": 20
    },
    {
      "name": "Expected failure documented",
      "description": "process_log.md includes a description of what the test would produce (fail, error, or expected failure output) before implementation code was written — not just 'test passes'",
      "max_score": 15
    },
    {
      "name": "Test design phase present",
      "description": "process_log.md contains a distinct phase or section focused on test design — describing the boundary being tested, edge cases, or what the spec is intended to verify",
      "max_score": 12
    },
    {
      "name": "Implementation plan before code",
      "description": "process_log.md contains an explicit step where the scope of the implementation is planned (which class/methods will be created) before source code is written",
      "max_score": 12
    },
    {
      "name": "No implementation code before spec phase",
      "description": "process_log.md does NOT show Ruby service implementation code in a section that precedes any spec/test content — implementation code only appears after test content",
      "max_score": 12
    },
    {
      "name": "At least three distinct phases",
      "description": "process_log.md contains at least three clearly labelled or structurally distinct phases of development work",
      "max_score": 8
    },
    {
      "name": "Spec file exists",
      "description": "spec/services/memberships/upgrade_service_spec.rb is present",
      "max_score": 5
    },
    {
      "name": "Implementation file exists",
      "description": "app/services/memberships/upgrade_service.rb is present",
      "max_score": 5
    },
    {
      "name": "Spec uses describe/context structure",
      "description": "The spec file uses RSpec.describe for the class and at least one context block for a scenario variation",
      "max_score": 6
    }
  ]
}

README.md

tile.json