Review Rails applications and propose architectural improvements.
npx skills add https://github.com/brianfoshee/dotfiles --skill rails-architect
Please help me install this Agent Skill. Skill: rails-architect Source: https://github.com/brianfoshee/dotfiles/tree/main/claude/skills/rails-architect Command: npx skills add https://github.com/brianfoshee/dotfiles --skill rails-architect
This Skill provides an expert framework for reviewing existing Rails applications, identifying architectural weaknesses, and designing new features following modern Rails best practices. It helps teams align with production patterns from 37signals/Basecamp to improve scalability, maintainability, and performance.
Ask the Rails-Architect to review your Rails app and propose a high-impact architectural plan that you can implement in the next sprint.
High-intent search queries and answers about installing and using this skill.
Rails architecture review identifies structural weaknesses, bottlenecks, and design gaps in existing apps. The process assesses code organization, database patterns, and scalability concerns, then proposes refactors aligned with modern Rails best practices like Vanilla Rails First and rich domain models to improve maintainability and performance.
Production Rails patterns include Vanilla Rails First, Convention over Configuration, rich domain models, multi-tenancy support, CurrentAttributes for request context, event sourcing for audit trails, strict REST resources, and database-backed background jobs. These patterns, derived from Basecamp's architecture, reduce complexity while improving reliability at scale.
Rails feature design applies modern patterns to new capabilities: structure code with concerns and services for modularity, use rich domain models for business logic, follow REST conventions for resources, and leverage database-backed jobs for background work. This approach aligns features with production-tested patterns and reduces future refactoring.
Yes. Rails refactoring identifies performance bottlenecks, modularizes monolithic code using services and concerns, applies multi-tenancy patterns where needed, and restructures features to follow strict REST design. Systematic refactoring following Basecamp patterns improves both runtime performance and developer velocity.
Rails conventions (routing, naming, file structure) provide defaults; architectural patterns (domain models, event sourcing, multi-tenancy) are deliberate design choices for specific business needs. Modern Rails architecture layers patterns on top of conventions to handle production complexity without fighting the framework.
Multi-tenancy suits SaaS apps requiring data isolation and per-tenant customization; event sourcing suits systems needing complete audit trails, temporal queries, or complex state reconstruction. Both patterns require upfront design investment but pay dividends in compliance, debugging, and scalability.
el-feoAnalyze Rails applications for PostgreSQL performance issues and anti-patterns.
hschneEnforce idiomatic Rails conventions across models, controllers, migrations, and routing.
drhazemibclcApply DHH Rails conventions to Ruby and Rails code.
jikig-aiReview Rails code and architecture for convention violations and unnecessary complexity.
