solid-ruby

Name: solid-ruby
Author: fusengine

github.com/fusengineDevelopment3438 installsUpdated 2w ago

About solid-ruby

solid-ruby is an agent skill for applying modular, SOLID-oriented architecture in Ruby 4.0+ and Rails 8 projects. It defines module locations, code and documentation rules, reuse checks, and reference guides and templates for implementation.

Key features

01Feature-based module structure
02Shared core services and contracts
03Mandatory YARD docs and frozen strings
04DRY checks before new code
05SOLID references and scaffolding templates

Use cases

01Structure a new Rails feature module
02Check for reusable services before coding
03Create services, contracts, models, and tests
04Review code against modular architecture rules

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fusengine/agents --skill solid-ruby

After installing, type/solid-rubyin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

architecture-patterns.md

dependency-inversion.md

interface-segregation.md

liskov-substitution.md

open-closed.md

single-responsibility.md

solid-principles.md

references/templates/

contract.md

error.md

model.md

module.md

service.md

test.md

Details

From the project README

SOLID Ruby enforces a modular architecture for Ruby 4.0+/Rails 8: every feature lives under `app/modules/[feature]/` (controllers, services, repositories, contracts, models) with shared code in `app/modules/core/`, contracts (duck-typing modules) live only in `contracts/` directories, `# frozen_string_literal: true` is required in every file, and every public method carries YARD documentation.

Before writing any new code it requires a DRY check against app/modules/core/services and app/modules/core/contracts. See solid-principles.md for the overview, the per-principle references for SRP/OCP/LSP/ISP/DIP detail, and the templates for module/service/contract/model/error/test scaffolding.

SOLID Ruby - Modular Architecture

Agent Workflow (MANDATORY)

Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:

fuse-ai-pilot:explore-codebase - Analyze existing architecture
fuse-ai-pilot:research-expert - Verify Ruby/Rails docs via Context7
fuse-ai-pilot:sniper - Post-implementation validation

DRY - Reuse Before Creating (MANDATORY)

Before writing ANY new code:

Grep the codebase for similar modules, services, or logic
Check shared locations: app/modules/core/services/, app/modules/core/contracts/
If similar code exists -> extend/reuse instead of duplicate
If code will be used by 2+ features -> create it in app/modules/core/

Architecture (Modules MANDATORY)

Layer	Location
Controllers	`app/modules/[feature]/controllers/`
Services	`app/modules/[feature]/services/`
Repositories	`app/modules/[feature]/repositories/`
Contracts	`app/modules/[feature]/contracts/`
Models	`app/modules/[feature]/models/`
Shared	`app/modules/core/{services,contracts,concerns}/`

NEVER use flat app/ structure - always app/modules/[feature]/

Critical Rules (MANDATORY)

Rule	Value
File limit	`FUSE_SOLID_MAX_LINES`
Controllers	Thin, delegate to services
Contracts	`contracts/` directory ONLY (duck typing modules)
YARD doc	Every public method documented
Frozen string	`# frozen_string_literal: true` in every file
Concerns	Use for shared behavior (like interfaces)

Reference Guide

Concepts

Topic	Reference	When to consult
SOLID Overview	solid-principles.md	Quick reference
SRP	single-responsibility.md	Fat classes
OCP	open-closed.md	Adding strategies
LSP	liskov-substitution.md	Contracts
ISP	interface-segregation.md	Fat modules
DIP	dependency-inversion.md	Injection
Architecture	architecture-patterns.md	Modular Rails

Templates

Template	When to use
module.md	Feature module structure
service.md	Business logic service
contract.md	Duck typing contracts
model.md	Active Record model
error.md	Custom exceptions
test.md	RSpec tests

Forbidden

Anti-Pattern	Fix
Files over `FUSE_SOLID_MAX_LINES`	Split by responsibility
Business logic in models	Extract to service
Fat controllers	Delegate to services
Flat `app/` structure	Use `app/modules/[feature]/`
God classes	Split by responsibility

Comments

Markdown supported

Details

Author: fusengine
Repository: fusengine/agents
Category: Development
Installs: 38
GitHub stars: 34

Report

More skills

All skills

remotion-render

github.com/inference-sh

1.6M

Render videos from React/Remotion component code via inference.sh. Pass TSX code, get MP4. Supports all Remotion APIs: useCurrentFrame, useVideoConfig, spring, interpolate, AbsoluteFill, Sequence. Configurable resolution, FPS, duration, codec. Use for: programmatic video generation, animated graphics, motion design, data-driven videos, React animations to video. Triggers: remotion, render video from code, tsx to video, react video, programmatic video, remotion render, code to video, animated video, motion graphics code, react animation video

improve-codebase-architecture

github.com/mattpocock

1.2M

Scan a codebase for architecture improvement opportunities, present them as a visual HTML report, then dive deep into whichever one you pick.

design-mobile-apps

github.com/designed-by-ai

1.1M

Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML

vercel-react-best-practices

github.com/vercel-labs

848.6k

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.