CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/rails-agent-skills

Curated library of 42 public AI agent skills for Ruby on Rails development, plus 5 callable workflow skills. Organized by category: planning, testing, code-quality, ddd, engines, infrastructure, api, patterns, context, orchestration, and workflows. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and TDD automation.

96

Quality

96%

Does it follow best practices?

Impact

—

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

SKILL.mdskills/ddd/define-domain-language/

name:
define-domain-language
license:
MIT
description:
Use when a Ruby on Rails feature, bug, or architecture discussion has fuzzy business terminology and you need shared vocabulary. Identifies canonical terms, resolves naming conflicts, maps synonyms to one concept, and generates a glossary for Rails-first workflows. Trigger words: DDD, shared vocabulary, define terms, bounded context naming, what should we call this, terminology alignment, DDD glossary, naming inconsistency.
metadata:
{"version":"1.0.0","user-invocable":"true"}

Define Domain Language

Use this skill when the domain language is fuzzy, overloaded, or inconsistent.

Core principle: Agree on business language before choosing models, services, or boundaries.

Quick Reference

TopicRule
Canonical termPick one business term for one concept
SynonymsCapture them, then choose one preferred term
Overloaded wordsFlag them early; split meanings explicitly
NamingPrefer business meaning over technical shorthand
OutputReturn a usable glossary, not abstract theory

HARD-GATE

DO NOT introduce DDD terminology without grounding it in the user's real domain language.
DO NOT rename code concepts until the glossary is explicit enough to justify the change.
ALWAYS flag overloaded or conflicting terms before recommending modeling changes.

When to Use

  • The user uses multiple words for what might be the same business concept.
  • A feature or bug discussion is blocked by unclear naming.
  • You need a glossary before doing boundary review or Rails modeling.
  • Next step: Chain to review-domain-boundaries when the glossary reveals multiple contexts, or to model-domain when the main problem is tactical modeling in Rails.

Process

  1. Collect terms: Pull candidate nouns, roles, states, events, and actions from the request, PRD, tickets, existing docs, and code names. In a Rails codebase, scan class and file names across layers: 
    grep -rh "^class \|^module " app/models app/controllers app/services --include="*.rb" | sort
  2. Group synonyms: Identify words that appear to mean the same thing and words that are overloaded across multiple meanings.
  3. Choose canonical terms: Prefer the clearest business term; keep aliases only as migration notes or search hints.
  4. Define each term: Write one short definition, expected invariants, and related concepts.
  5. Flag ambiguity: List terms that need user confirmation or that likely indicate multiple bounded contexts.
  6. Hand off: Continue with review-domain-boundaries, model-domain, or create-prd / generate-tasks depending on the workflow stage.

Output Style

When using this skill, return:

  1. Canonical term
  2. Aliases / conflicting words
  3. Definition
  4. Key invariant or business rule
  5. Likely related context
  6. Open questions

Minimal example (one row):

Canonical termAliasesDefinitionInvariantContext
ShipmentParcel, PackagePhysical goods sent to a customer addressMust reference a valid OrderFulfillment

Open questions: Does "Parcel" ever mean an internal warehouse bin ID? If yes, split into two glossary entries.

See assets/examples.md for a full worked glossary example and common mistakes.

Integration

SkillWhen to chain
create-prdWhen a PRD needs cleaner business language before approval
review-domain-boundariesWhen the glossary suggests multiple bounded contexts or language leakage
model-domainWhen the terms are clear enough to decide entities, value objects, and services
review-architectureWhen naming confusion already appears in the code structure

Assets

skills

ddd

define-domain-language

EXAMPLES.md

SKILL.md

README.md

tile.json