iron-laws

Enforce 22 Iron Laws across Ruby, Rails, and Grape codebases.

7|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill iron-laws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iron-laws
Source: https://github.com/slbug/claude-ruby-grape-rails/tree/main/plugins/ruby-grape-rails/skills/iron-laws
Command: npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill iron-laws

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ruby, Rails, and Grape projects often suffer from subtle architectural and security issues that the Iron Laws aim to prevent by codifying non-negotiable rules.

Core Features & Use Cases

  • Comprehensive enforcement of 22 laws across ActiveRecord, Sidekiq, Ruby, and security domains to guide development and audits.
  • Practical violation patterns, remediation guidance, and a canonical registry to standardize checks across teams.
  • Use during code reviews, static analysis, and CI checks to raise actionable findings before merging.

Quick Start

Run an automated check against your codebase to detect and remediate any iron-law violations.

Frequently Asked Questions about iron-laws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce static analysis rules to prevent common Ruby on Rails security pitfalls?

To enforce static analysis rules for Ruby on Rails security pitfalls, this Skill identifies and enforces 22 Iron Laws across ActiveRecord, Sidekiq, security, and Ruby runtime boundaries. It provides actionable remediation guidance and explicit violation reporting during code reviews and automated CI checks.

What are the Iron Laws for Ruby and how do they improve code quality?

The Iron Laws for Ruby are 22 non-negotiable rules that codify architectural and security standards to prevent subtle project mistakes. They improve code quality by standardizing checks across ActiveRecord, Sidekiq, and security domains, raising actionable findings before code merges.

Can I use this to detect ActiveRecord and Sidekiq violations during a code review?

Yes, you can use this to detect ActiveRecord and Sidekiq violations during a code review. It enforces a canonical registry of 22 Iron Laws tailored for Ruby, Rails, and Grape projects, outputting explicit violation patterns and remediation guidance for identified issues.

What's the best way to automate Ruby code quality checks for security and runtime boundaries?

The best way to automate Ruby code quality checks for security and runtime boundaries is running this Skill as an automated check against your codebase. It detects iron-law violations across ActiveRecord, Sidekiq, and Ruby domains, providing actionable remediation guidance to standardize team checks.

Does this static analysis tool work with Grape API projects?

Yes, this static analysis tool works with Grape API projects. The 22 Iron Laws are specifically designed to prevent common Ruby, Rails, and Grape mistakes, codifying non-negotiable rules for architectural and security issues across these frameworks.