Scaffold
codewithmukesh/dotnet-claude-kit
Architecture-aware feature scaffolding for .NET 10 projects.
Create a new domain bounded context with aggregates, commands, events, and handlers
$ npx skills add RailsEventStore/ecommerce --skill domain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RailsEventStore/ecommerce domain --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/RailsEventStore/ecommerce.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/domain .claude/skills/domain && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "domain" agent skill from https://github.com/RailsEventStore/ecommerce/tree/master/.claude/skills/domain into .claude/skills/domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/RailsEventStore/ecommerce/tree/master/.claude/skills/domainType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add RailsEventStore/ecommerce --skill domain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RailsEventStore/ecommerce domain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RailsEventStore/ecommerce.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/domain .agents/skills/domain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "domain" agent skill from https://github.com/RailsEventStore/ecommerce/tree/master/.claude/skills/domain into .agents/skills/domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RailsEventStore/ecommerce --skill domain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RailsEventStore/ecommerce domain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RailsEventStore/ecommerce.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/domain .cursor/skills/domain && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "domain" agent skill from https://github.com/RailsEventStore/ecommerce/tree/master/.claude/skills/domain into .cursor/skills/domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/RailsEventStore/ecommerce.git --path .claude/skills/domain--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add RailsEventStore/ecommerce --skill domain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RailsEventStore/ecommerce domain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RailsEventStore/ecommerce.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/domain .gemini/skills/domain && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "domain" agent skill from https://github.com/RailsEventStore/ecommerce/tree/master/.claude/skills/domain into .gemini/skills/domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install RailsEventStore/ecommerce domainInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add RailsEventStore/ecommerce --skill domain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RailsEventStore/ecommerce.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/domain .github/skills/domain && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "domain" agent skill from https://github.com/RailsEventStore/ecommerce/tree/master/.claude/skills/domain into .github/skills/domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RailsEventStore/ecommerce --skill domain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RailsEventStore/ecommerce domain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RailsEventStore/ecommerce.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/domain .opencode/skills/domain && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "domain" agent skill from https://github.com/RailsEventStore/ecommerce/tree/master/.claude/skills/domain into .opencode/skills/domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
domainCreate a new domain bounded context with aggregates, commands, events, and handlers
Domain is an agent skill from RailsEventStore/ecommerce. Create a new domain bounded context with aggregates, commands, events, and handlers
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Domain-driven design. The repository describes itself as: Application with CQRS and Event Sourcing built on Rails and Rails Event Store. The licence is MIT.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 42c6c23. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
makebundleFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
rubygems.orgFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Domain loads about 2.6k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 697 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from RailsEventStore/ecommerce at commit 42c6c23, republished under its MIT licence (© RailsEventStore). 697 words, ~2,601 tokens.
.claude/skills/domain/SKILL.md (or your agent's skills folder).Use this skill when asked to create a new domain module (bounded context) in the domains/ directory, or to add new aggregates/commands/events to an existing domain.
Two patterns exist in the codebase:
lib/{domain}/todo.rbUse the structured pattern for any non-trivial domain. The simple pattern is only for demos.
Before writing any code, clarify:
project_management, ticketing)Customer, Deal, Contact)Create the directory structure:
domains/{domain_name}/
├── Gemfile
├── Makefile
├── .mutant.yml
├── lib/
│ ├── {domain_name}.rb # Module entry point + Configuration
│ └── {domain_name}/
│ ├── commands/
│ │ └── {command_name}.rb # One file per command
│ ├── events/
│ │ └── {event_name}.rb # One file per event
│ ├── {aggregate_name}.rb # Aggregate root
│ └── {aggregate_name}_service.rb # Command handlers
└── test/
├── test_helper.rb
└── {test_name}_test.rb # One file per test concernGemfile:
source "https://rubygems.org"
eval_gemfile "../../infra/Gemfile.test"
gem "infra", path: "../../infra"Makefile:
install:
@bundle install
test:
@bundle exec ruby -e "require \"rake/rake_test_loader\"" test/*_test.rb
mutate:
@RAILS_ENV=test bundle exec mutant run
.PHONY: install test mutate.mutant.yml:
requires:
- ./test/test_helper
integration: minitest
usage: opensource
coverage_criteria:
process_abort: true
matcher:
subjects:
- {DomainModule}*
ignore:
- {DomainModule}::Configuration#callCreate test/test_helper.rb:
require "minitest/autorun"
require "mutant/minitest/coverage"
require_relative "../lib/{domain_name}"
module DomainModule
class Test < Infra::InMemoryTest
def before_setup
super
Configuration.new.call(event_store, command_bus)
end
private
def some_helper(id, attribute)
run_command(SomeCommand.new(entity_id: id, attribute: attribute))
end
end
endCreate test files — one per logical concern (e.g. test/registration_test.rb, test/assignment_test.rb):
require_relative "test_helper"
module DomainModule
class SomeTest < Test
cover "DomainModule*"
def test_entity_can_be_created
id = SecureRandom.uuid
create_entity(id, "some value")
expected_event = EntityCreated.new(data: { entity_id: id, attribute: "some value" })
assert_events("DomainModule::Entity$#{id}", expected_event) do
create_entity(id, "some value")
end
end
def test_cannot_create_same_entity_twice
id = SecureRandom.uuid
create_entity(id, "value")
assert_raises(Entity::AlreadyExists) do
create_entity(id, "value")
end
end
private
def create_entity(id, value)
run_command(CreateEntity.new(entity_id: id, attribute: value))
end
end
endTest conventions:
cover "DomainModule*" for mutation testingrun_command(...) to dispatch commands (provided by Infra::InMemoryTest)assert_events(stream, expected_event) { block } to verify eventsassert_raises(ErrorClass) { block } for invariant violationsOne file per command in lib/{domain_name}/commands/:
module DomainModule
class CreateEntity < Infra::Command
attribute :entity_id, Infra::Types::UUID
attribute :name, Infra::Types::String
alias aggregate_id entity_id
end
endCommand conventions:
Infra::CommandInfra::Types::UUID for UUIDs, Infra::Types::String for stringsalias aggregate_id {entity_id_field} so the handler can use command.aggregate_idOne file per event in lib/{domain_name}/events/:
module DomainModule
class EntityCreated < Infra::Event
attribute :entity_id, Infra::Types::UUID
attribute :name, Infra::Types::String
end
endEvent conventions:
Infra::EventCreated, Updated, Assigned, Promoted)module DomainModule
class Entity
include AggregateRoot
AlreadyExists = Class.new(StandardError)
NotFound = Class.new(StandardError)
def initialize(id)
@id = id
end
def create(name)
raise AlreadyExists if @created
apply EntityCreated.new(data: { entity_id: @id, name: name })
end
def update_name(name)
raise NotFound unless @created
apply EntityNameUpdated.new(data: { entity_id: @id, name: name })
end
private
on EntityCreated do |event|
@created = true
end
on EntityNameUpdated do |event|
end
end
endAggregate conventions:
include AggregateRoot@created, @completed, etc.)raise before applyon EventClass do |event| blocks update internal stateon blocksClass.new(StandardError)One handler class per command, grouped in a service file:
module DomainModule
class OnCreateEntity
def initialize(event_store)
@repository = Infra::AggregateRootRepository.new(event_store)
end
def call(command)
@repository.with_aggregate(Entity, command.aggregate_id) do |entity|
entity.create(command.name)
end
end
end
class OnUpdateEntityName
def initialize(event_store)
@repository = Infra::AggregateRootRepository.new(event_store)
end
def call(command)
@repository.with_aggregate(Entity, command.aggregate_id) do |entity|
entity.update_name(command.name)
end
end
end
endHandler conventions:
@repository.with_aggregate(AggregateClass, id) { |agg| ... }OnRegistration, OnSetCustomer, OnPromoteCustomerToVip_service.rb file per aggregate, or separate files for clarityCreate lib/{domain_name}.rb:
require "infra"
require_relative "{domain_name}/commands/create_entity"
require_relative "{domain_name}/commands/update_entity_name"
require_relative "{domain_name}/events/entity_created"
require_relative "{domain_name}/events/entity_name_updated"
require_relative "{domain_name}/entity_service"
require_relative "{domain_name}/entity"
module DomainModule
class Configuration
def call(event_store, command_bus)
command_bus.register(CreateEntity, OnCreateEntity.new(event_store))
command_bus.register(UpdateEntityName, OnUpdateEntityName.new(event_store))
end
end
endConfiguration conventions:
require "infra" first, then all domain filesevent_store in constructorcd domains/{domain_name}
bundle install
make test # All tests pass
make mutate # 100% mutation scoreThen from the project root:
make test # Ensure nothing is broken globallyKeep aggregates as small as possible. An aggregate is often a small state machine with two or three states. Adding new methods to an existing aggregate is a smell — it signals a cohesion problem. Before adding a method, ask: "Is this really the same concept, or is it a new aggregate?"
Associations between entities are often aggregates on their own. For example, "Contact assigned to Company" is not a method on Contact — it's a separate ContactCompanyAssignment aggregate with its own lifecycle. The Contact aggregate handles contact registration and attributes. The assignment is a different concern.
Passing strings or "data" into aggregate methods is a smell. Aggregate methods should ideally receive only IDs (UUIDs). If you're passing names, descriptions, or other data, consider whether the aggregate is doing too much. Small smells are acceptable — the goal is to avoid ActiveRecord-like bloat where aggregates accumulate dozens of setter methods.
Don't validate other aggregates from command handlers. Avoid patterns like @event_store.read.stream("Crm::Entity$#{id}").last or raise NotFound in command handlers. This couples the handler to stream naming conventions and makes it responsible for validating external state. Instead, trust the caller (controllers provide valid IDs from read model dropdowns) or model the relationship as its own aggregate that can enforce its own invariants.
Signs an aggregate is too big:
@name, @email, @company_id)on blocks are growing in numberRegisterCustomer, AddTodo, AssignDealCustomerRegistered, TodoAdded, DealAssignedInfra::Types::UUID and Infra::Types::String for typed attributes© RailsEventStore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/domain of RailsEventStore/ecommerce.
Open the folder on GitHubat commit 42c6c23
Domain next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Domain this skillRailsEventStore/ecommerce | 507 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Scaffoldcodewithmukesh/dotnet-claude-kit | 755 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Moai Workflow Testingmodu-ai/moai-adk | 1.2k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Domain Modelingfossasia/eventyay-interpretation | 1.6k | 31 repos | ~821 | Automated safety check: Pass | Apache-2.0 | |
| Architecture Governancezai-org/ZCode | 7.6k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Evolutionary Modular Architecturetech-leads-club/agent-skills | 7k | — | ~3.7k | Automated safety check: Pass | CC-BY-4.0 |
codewithmukesh/dotnet-claude-kit
Architecture-aware feature scaffolding for .NET 10 projects.
modu-ai/moai-adk
A skill your agent uses when writing tests, measuring coverage, or running characterization, performance, or PR-review QA.
fossasia/eventyay-interpretation
Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.
zai-org/ZCode
Apply the repository's architecture policy to code changes by generating a bounded context package, checking module and layer boundaries, and reporting baseline-aware violations.
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
RailsEventStore/ecommerce
Create atomic git commits following project conventions. An agent skill from RailsEventStore/ecommerce.
RailsEventStore/ecommerce
Create a controller with commands, read model queries, routes, and integration tests
RailsEventStore/ecommerce
Scaffold a new Rails app with event sourcing, following project conventions (todomvc as reference)
RailsEventStore/ecommerce
Plan a new feature end-to-end — impact analysis across all layers, start-from-the-middle slicing into deployable steps, then delegating to /domain, /read-model, /controller skills
RailsEventStore/ecommerce
Build a new read model following project conventions (event handlers, tests, migration, configuration)
RailsEventStore/ecommerce
Upgrade Rails framework to a newer version following the smooth upgrade methodology
Categories
Create a new domain bounded context with aggregates, commands, events, and handlers. Domain is an agent skill from RailsEventStore/ecommerce.
Domain fits situations like: tasks that involve Domain-driven design.
Run `npx skills add RailsEventStore/ecommerce --skill domain -a claude-code`. Or copy the skill folder (.claude/skills/domain in RailsEventStore/ecommerce) into .claude/skills/domain in your project. Claude Code loads it when a task matches its description.
Run `npx skills add RailsEventStore/ecommerce --skill domain -a codex`. Or copy the skill folder (.claude/skills/domain in RailsEventStore/ecommerce) into .agents/skills/domain in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add RailsEventStore/ecommerce --skill domain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/domain, .gemini/skills/domain, .github/skills/domain and .opencode/skills/domain in your project.
Going by SKILL.md and its folder, Domain needs the command-line tools its instructions call (make and bundle).
SKILL.md names 1 domain. In commands or code: rubygems.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Domain is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Domain: Scaffold (codewithmukesh/dotnet-claude-kit, 755 stars), Moai Workflow Testing (modu-ai/moai-adk, 1.2k stars), Domain Modeling (fossasia/eventyay-interpretation, 1.6k stars) and Architecture Governance (zai-org/ZCode, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
RailsEventStore (a GitHub organization) maintains it in RailsEventStore/ecommerce, which has 507 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 21, 2026.
Source: RailsEventStore/ecommerce on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.