igmarin/ddd-ubiquitous-language
skills/ddd/ddd-ubiquitous-language/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add igmarin/rails-agent-skills ddd-ubiquitous-languageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 2:57 AM110.5s4 files scanned
SKILL.md
- name:
- ddd-ubiquitous-language
- license:
- MIT
- description:
- >
- for Rails-first workflows. Trigger words:
- DDD, shared vocabulary, define terms,
- version:
- 1.0.0
- user-invocable:
- true
DDD Ubiquitous 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
| Topic | Rule | |-------|------| | Canonical term | Pick one business term for one concept | | Synonyms | Capture them, then choose one preferred term | | Overloaded words | Flag them early; split meanings explicitly | | Naming | Prefer business meaning over technical shorthand | | Output | Return 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
ddd-boundaries-reviewwhen the glossary reveals multiple contexts, or toddd-rails-modelingwhen the main problem is tactical modeling in Rails.
Process
- 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 - Group synonyms: Identify words that appear to mean the same thing and words that are overloaded across multiple meanings.
- Choose canonical terms: Prefer the clearest business term; keep aliases only as migration notes or search hints.
- Define each term: Write one short definition, expected invariants, and related concepts.
- Flag ambiguity: List terms that need user confirmation or that likely indicate multiple bounded contexts.
- Hand off: Continue with
ddd-boundaries-review,ddd-rails-modeling, orcreate-prd/generate-tasksdepending on the workflow stage.
Output Style
When using this skill, return:
- Canonical term
- Aliases / conflicting words
- Definition
- Key invariant or business rule
- Likely related context
- Open questions
Minimal example (one row):
| Canonical term | Aliases | Definition | Invariant | Context | |----------------|---------|------------|-----------|----------| | Shipment | Parcel, Package | Physical goods sent to a customer address | Must reference a valid Order | Fulfillment |
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
| Skill | When to chain | |-------|---------------| | create-prd | When a PRD needs cleaner business language before approval | | ddd-boundaries-review | When the glossary suggests multiple bounded contexts or language leakage | | ddd-rails-modeling | When the terms are clear enough to decide entities, value objects, and services | | rails-architecture-review | When naming confusion already appears in the code structure |
Assets
- assets/examples.md
Related Skills
igmarin/rails-agent-skills
development
VerifiedTrustedCommunity
Entry point for Rails development workflows covering TDD, RSpec, Service Objects, DDD, GraphQL, Engines, and Code Quality. Use when the user asks about Ruby on Rails development patterns, needs RSpec test suites generated, wants service objects scaffolded, is setting up GraphQL schemas, performing Rails code review, refactoring .rb files, working with domain-driven design, implementing background jobs, conducting Rails security checks, or building Rails engines. Generates RSpec tests, structures service objects, enforces TDD workflows, configures GraphQL schemas, and coordinates domain-driven design patterns. Trigger keywords: Rails, RSpec, TDD, Rails testing, Rails refactor, Rails API, Rails code review, domain driven design, service objects, GraphQL, Rails engine, Ruby, .rb, background jobs, Rails migrations, Rails security check.
21SKILL.mdUpdated May 18, 2026
igmarin/release-engine
development
VerifiedTrustedCommunity
Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build *.gemspec && gem push --dry-run *.gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.
21SKILL.mdUpdated May 9, 2026
igmarin/tdd
development
VerifiedTrustedCommunity
Orchestrates the full Rails TDD cycle with hard gates: test MUST exist, be run, and FAIL for the correct reason (e.g. undefined method, not syntax error) before any implementation code — propose minimal implementation and wait for user approval → verify test PASSES → run full suite with rubocop, brakeman, rspec all green → produce YARD documentation and self-reviewed PR; phases context/test design→implementation→iterate→finish. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
19SKILL.mdUpdated Jun 5, 2026
igmarin/setup
development
VerifiedTrustedCommunity
Complete Rails project setup loop with hard gates: verify Ruby version matches .ruby-version, Bundler installed, database connection successful, all env vars loaded, and ALL external CI actions pinned to immutable commit SHAs (never mutable tags like @v4) → configure CI/CD pipeline with linting, testing, and security scanning → validate end-to-end with bundle install, db:create, db:migrate, rspec, and write SETUP_CHECKLIST.md; phases context/onboarding→CI/CD configuration→environment validation. Use when starting a new Rails project, running `rails new`, configuring a Gemfile or .ruby-version, setting up a development environment, or wiring up CI/CD for a Ruby on Rails app. Trigger: setup project, new Rails app, configure CI/CD, dev environment setup, rails new, Gemfile setup, .ruby-version, Ruby on Rails project bootstrap.
19SKILL.mdUpdated Jun 5, 2026