ddd-rails-modeling
Use when modeling Domain-Driven Design concepts in a Ruby on Rails codebase. Covers Rails-first mapping of entities, aggregates, value objects, domain services, application services, repositories, and domain events without over-engineering or fighting Rails conventions.
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 strong skill description that clearly defines its scope at the intersection of Domain-Driven Design and Ruby on Rails. It enumerates specific DDD concepts covered, explicitly states when to use it, and adds valuable context about the approach (Rails-first, no over-engineering). The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete concepts: entities, aggregates, value objects, domain services, application services, repositories, and domain events. Also specifies the approach: Rails-first mapping without over-engineering or fighting Rails conventions. | 3 / 3 |
Completeness | Clearly answers both 'what' (Rails-first mapping of DDD concepts like entities, aggregates, value objects, etc.) and 'when' (explicitly starts with 'Use when modeling Domain-Driven Design concepts in a Ruby on Rails codebase'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Domain-Driven Design', 'DDD', 'Ruby on Rails', 'entities', 'aggregates', 'value objects', 'domain services', 'repositories', 'domain events'. These are terms developers naturally use when seeking DDD guidance in Rails. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by combining two specific domains: DDD patterns AND Ruby on Rails. The intersection of these two topics creates a clear niche that is unlikely to conflict with general Rails skills or general DDD skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%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-organized design skill that effectively maps DDD concepts to Rails conventions with clear anti-patterns and decision guidance. Its main weakness is that the examples are descriptive comments rather than concrete, executable Ruby code, and there is some redundancy between the Quick Reference and Rails-First Mapping tables. The workflow and progressive disclosure are strong, with clear sequencing and well-signaled skill chaining.
Suggestions
Replace the comment-only examples with concrete, executable Ruby code showing actual class definitions (e.g., a real Value Object class with `==`, `hash`, and domain methods; a real Application Service with a `call` method)
Consolidate the 'Quick Reference' and 'Rails-First Mapping' tables into a single reference to reduce redundancy and save tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts Claude already knows, but some sections are slightly redundant—the 'Rails-First Mapping' table overlaps significantly with the 'Quick Reference' table, and the 'Common Mistakes' and 'Red Flags' sections cover similar ground. Could be tightened by ~20%. | 2 / 3 |
Actionability | The skill provides structured guidance with clear tables and a modeling order, but the examples are comments/descriptions rather than executable code. The output style template is helpful but the examples lack concrete, copy-paste-ready Ruby implementations showing actual value objects or services with real method signatures. | 2 / 3 |
Workflow Clarity | The 'Modeling Order' section provides a clear 6-step sequence from listing domain concepts through verification with tests. For a decision-making/design skill (not a destructive operation), the workflow is well-sequenced with a clear handoff to testing as validation. The chaining guidance provides explicit next steps. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections, tables for quick scanning, and explicit integration references to other skills (ddd-ubiquitous-language, ddd-boundaries-review, generate-tasks, etc.) that are one level deep and clearly signaled with 'when to chain' context. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- igmarin/rails-agent-skills
- Commit
ae8ea63
- Reviewed
Table of Contents
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.