rails-architecture

Guides modern Rails 8 code architecture decisions and patterns. Use when deciding where to put code, choosing between patterns (service objects vs concerns vs query objects), designing feature architecture, refactoring for better organization, or when user mentions architecture, code organization, design patterns, or layered design.

1.40x

Quality

92%

Does it follow best practices?

Impact

97%

1.40x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured architecture guide that excels at organization and progressive disclosure. The decision tree and layer diagrams are excellent navigational aids. The main weakness is that it functions more as a routing document to other skills than a standalone actionable guide—most concrete implementation details are deferred elsewhere.

Suggestions

Add one complete, executable example showing a feature implemented across multiple layers (e.g., a simple order creation flow showing controller → service → model → presenter) to make the architecture tangible

Include a concrete code example for the Query Object pattern inline, since it's referenced but not demonstrated like the Service and Result patterns are

Dimension	Reasoning	Score
Conciseness	The content is highly efficient, using tables, decision trees, and ASCII diagrams to convey maximum information with minimal prose. No unnecessary explanations of concepts Claude already knows.	3 / 3
Actionability	Provides good concrete examples for controller patterns and Result objects, but many sections defer to other skills rather than providing executable code. The decision tree is helpful but abstract—it tells you where to go, not how to implement.	2 / 3
Workflow Clarity	The decision tree provides an excellent clear sequence for architectural decisions. The 'New Feature Checklist' and 'Refactoring Signals' tables give explicit step-by-step guidance. For an architecture/decision skill (not a destructive operation), this level of clarity is appropriate.	3 / 3
Progressive Disclosure	Excellent structure with clear overview, well-organized sections, and one-level-deep references to related skills and reference documents. Navigation is easy with the Related Skills table and References section clearly signaling where to find detailed information.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms developers would use, has an explicit 'Use when...' clause, and is clearly scoped to Rails 8 architecture to avoid conflicts with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'deciding where to put code', 'choosing between patterns (service objects vs concerns vs query objects)', 'designing feature architecture', 'refactoring for better organization'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Guides modern Rails 8 code architecture decisions and patterns') and when with explicit 'Use when...' clause covering multiple trigger scenarios including user mentions of specific terms.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'architecture', 'code organization', 'design patterns', 'layered design', 'service objects', 'concerns', 'query objects', 'refactoring'. Good coverage of terms developers naturally use when discussing Rails architecture.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to 'Rails 8' and 'architecture decisions' with specific pattern names (service objects, concerns, query objects). Unlikely to conflict with general coding skills or other framework-specific skills due to the Rails 8 specificity and architecture focus.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: fernandezbaptiste/rails_ai_agents
Commit: 15fdeaf

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.