architecture

Guide Ruby on Rails architectural decisions with ADRs and trade-off analysis.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill architecture-renzo-tognella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Renzo-Tognella/UniversalThingsForMyAgents/tree/main/skills/architecture
Command: npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill architecture-renzo-tognella

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of making informed architectural decisions in Ruby on Rails by providing a structured framework for analysis, trade-offs, and documentation.

Core Features & Use Cases

  • Structured Decision-Making Process: Guided steps for understanding context, considering options, and analyzing trade-offs.
  • Framework for Documentation: Templates for Architecture Decision Records (ADR) to capture rationale and decisions.
  • Pattern Catalog: Reference for common patterns and design decisions in Rails.
  • Modularization Guide: Best practices for modularizing Rails applications using Packwerk-style organization.
  • Use Case: When developing a new feature that spans multiple domains or requires significant architectural changes, this Skill helps ensure a consistent and maintainable codebase.

Quick Start

To create an ADR for a new feature, follow the structured process outlined in the 'Process of Decision' section of the 'Architecture — Framework de Decisões' guide.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I make architecture decisions in Ruby on Rails using domain-driven design?

This Skill provides a structured decision-making process for Ruby on Rails architecture, guiding you through domain-driven design context, trade-off analysis, and ADR generation to ensure maintainable code.

What is the best way to document Rails architectural trade-offs?

Document Rails architectural trade-offs by creating Architecture Decision Records (ADRs) using provided templates. ADRs capture context, options, and rationale, providing a clear history of modularization and design choices.

How do I modularize a Ruby on Rails application?

Modularize a Ruby on Rails application by applying Packwerk-style organization and domain-driven design boundaries. This isolates domains, enforces dependencies, and maintains a consistent codebase during architectural changes.

When do I need an Architecture Decision Record for my Rails app?

You need an Architecture Decision Record when developing a new feature spanning multiple domains or requiring significant architectural changes. ADRs capture the rationale behind Shopify-style architecture patterns and modularization decisions.

Does this architecture framework support Shopify-style Rails patterns?

Yes, the framework supports Shopify-style Rails patterns. It provides a pattern catalog and modularization guide referencing Packwerk-style organization, ensuring decisions align with domain-driven design principles.