abp-entity-patterns
ABP Framework domain layer patterns including entities, aggregates, repositories, domain services, and data seeding. Use when: (1) creating entities with proper base classes, (2) implementing custom repositories, (3) writing domain services, (4) seeding data.
Best use case
abp-entity-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
ABP Framework domain layer patterns including entities, aggregates, repositories, domain services, and data seeding. Use when: (1) creating entities with proper base classes, (2) implementing custom repositories, (3) writing domain services, (4) seeding data.
Teams using abp-entity-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/abp-entity-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abp-entity-patterns Compares
| Feature / Agent | abp-entity-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
ABP Framework domain layer patterns including entities, aggregates, repositories, domain services, and data seeding. Use when: (1) creating entities with proper base classes, (2) implementing custom repositories, (3) writing domain services, (4) seeding data.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ABP Entity Patterns
Domain layer patterns for ABP Framework following DDD principles.
## Architecture Layers
```
Domain.Shared → Constants, enums, shared types
Domain → Entities, repositories, domain services, domain events
Application.Contracts → DTOs, application service interfaces
Application → Application services, mapper profiles
EntityFrameworkCore → DbContext, repository implementations
HttpApi → Controllers
HttpApi.Host → Startup, configuration
```
**Key principle**: Dependencies flow downward. Application depends on Domain, but Domain never depends on Application.
## Entity Base Classes
### Choosing the Right Base Class
| Base Class | Use When |
|------------|----------|
| `Entity<TKey>` | Simple entity, no auditing |
| `AuditedEntity<TKey>` | Need creation/modification tracking |
| `FullAuditedEntity<TKey>` | Need soft delete + full audit |
| `AggregateRoot<TKey>` | Root entity of an aggregate |
| `FullAuditedAggregateRoot<TKey>` | **Most common** - full features |
### Standard Entity Pattern
```csharp
public class Patient : FullAuditedAggregateRoot<Guid>
{
public string FirstName { get; private set; }
public string LastName { get; private set; }
public string Email { get; private set; }
public DateTime DateOfBirth { get; private set; }
public bool IsActive { get; private set; }
// Required for EF Core
protected Patient() { }
// Constructor with validation
public Patient(
Guid id,
string firstName,
string lastName,
string email,
DateTime dateOfBirth)
: base(id)
{
SetName(firstName, lastName);
SetEmail(email);
DateOfBirth = dateOfBirth;
IsActive = true;
}
// Domain methods with validation
public void SetName(string firstName, string lastName)
{
FirstName = Check.NotNullOrWhiteSpace(firstName, nameof(firstName), maxLength: 100);
LastName = Check.NotNullOrWhiteSpace(lastName, nameof(lastName), maxLength: 100);
}
public void SetEmail(string email)
{
Email = Check.NotNullOrWhiteSpace(email, nameof(email), maxLength: 256);
}
public void Activate() => IsActive = true;
public void Deactivate() => IsActive = false;
}
```
### Soft Delete
```csharp
public class Patient : FullAuditedAggregateRoot<Guid>, ISoftDelete
{
public bool IsDeleted { get; set; }
// ABP automatically filters out soft-deleted entities
}
```
### Multi-Tenancy
```csharp
public class Patient : FullAuditedAggregateRoot<Guid>, IMultiTenant
{
public Guid? TenantId { get; set; }
// ABP automatically filters by current tenant
}
```
### Audit Fields
`FullAuditedAggregateRoot<Guid>` provides:
- `CreationTime`, `CreatorId`
- `LastModificationTime`, `LastModifierId`
- `IsDeleted`, `DeletionTime`, `DeleterId`
## Repository Pattern
### Generic Repository Usage
```csharp
public class PatientAppService : ApplicationService
{
private readonly IRepository<Patient, Guid> _patientRepository;
public PatientAppService(IRepository<Patient, Guid> patientRepository)
{
_patientRepository = patientRepository;
}
public async Task<PatientDto> GetAsync(Guid id)
{
var patient = await _patientRepository.GetAsync(id);
return ObjectMapper.Map<Patient, PatientDto>(patient);
}
public async Task<PagedResultDto<PatientDto>> GetListAsync(PagedAndSortedResultRequestDto input)
{
var totalCount = await _patientRepository.GetCountAsync();
var queryable = await _patientRepository.GetQueryableAsync();
var patients = await AsyncExecuter.ToListAsync(
queryable
.OrderBy(input.Sorting ?? nameof(Patient.FirstName))
.PageBy(input.SkipCount, input.MaxResultCount));
return new PagedResultDto<PatientDto>(
totalCount,
ObjectMapper.Map<List<Patient>, List<PatientDto>>(patients));
}
}
```
### Custom Repository
**Define interface in Domain layer:**
```csharp
public interface IPatientRepository : IRepository<Patient, Guid>
{
Task<List<Patient>> GetActivePatientsByDoctorAsync(Guid doctorId);
Task<Patient?> FindByEmailAsync(string email);
}
```
**Implement in EntityFrameworkCore layer:**
```csharp
public class PatientRepository : EfCoreRepository<ClinicDbContext, Patient, Guid>, IPatientRepository
{
public PatientRepository(IDbContextProvider<ClinicDbContext> dbContextProvider)
: base(dbContextProvider)
{
}
public async Task<List<Patient>> GetActivePatientsByDoctorAsync(Guid doctorId)
{
var dbSet = await GetDbSetAsync();
return await dbSet
.Where(p => p.PrimaryDoctorId == doctorId && p.IsActive)
.Include(p => p.Appointments)
.ToListAsync();
}
public async Task<Patient?> FindByEmailAsync(string email)
{
var dbSet = await GetDbSetAsync();
return await dbSet.FirstOrDefaultAsync(p => p.Email == email);
}
}
```
## Domain Services
Use domain services when business logic involves multiple entities or external domain concepts.
```csharp
public class AppointmentManager : DomainService
{
private readonly IRepository<Appointment, Guid> _appointmentRepository;
private readonly IRepository<DoctorSchedule, Guid> _scheduleRepository;
public AppointmentManager(
IRepository<Appointment, Guid> appointmentRepository,
IRepository<DoctorSchedule, Guid> scheduleRepository)
{
_appointmentRepository = appointmentRepository;
_scheduleRepository = scheduleRepository;
}
public async Task<Appointment> CreateAsync(
Guid patientId,
Guid doctorId,
DateTime appointmentDate,
string description)
{
// Business rule: Check if doctor is available
await CheckDoctorAvailabilityAsync(doctorId, appointmentDate);
// Business rule: Check for conflicts
await CheckAppointmentConflictsAsync(doctorId, appointmentDate);
var appointment = new Appointment(
GuidGenerator.Create(),
patientId,
doctorId,
appointmentDate,
description);
return await _appointmentRepository.InsertAsync(appointment);
}
private async Task CheckDoctorAvailabilityAsync(Guid doctorId, DateTime appointmentDate)
{
var schedule = await _scheduleRepository.FirstOrDefaultAsync(
s => s.DoctorId == doctorId && s.DayOfWeek == appointmentDate.DayOfWeek);
if (schedule == null)
throw new BusinessException("Doctor not available on this day");
var timeOfDay = appointmentDate.TimeOfDay;
if (timeOfDay < schedule.StartTime || timeOfDay > schedule.EndTime)
throw new BusinessException("Doctor not available at this time");
}
private async Task CheckAppointmentConflictsAsync(Guid doctorId, DateTime appointmentDate)
{
var hasConflict = await _appointmentRepository.AnyAsync(a =>
a.DoctorId == doctorId &&
a.AppointmentDate == appointmentDate &&
a.Status != AppointmentStatus.Cancelled);
if (hasConflict)
throw new BusinessException("Doctor already has an appointment at this time");
}
}
```
## Data Seeding
### IDataSeedContributor Pattern
```csharp
public class ClinicDataSeedContributor : IDataSeedContributor, ITransientDependency
{
private readonly IRepository<Doctor, Guid> _doctorRepository;
private readonly IGuidGenerator _guidGenerator;
public ClinicDataSeedContributor(
IRepository<Doctor, Guid> doctorRepository,
IGuidGenerator guidGenerator)
{
_doctorRepository = doctorRepository;
_guidGenerator = guidGenerator;
}
public async Task SeedAsync(DataSeedContext context)
{
// Idempotent check
if (await _doctorRepository.GetCountAsync() > 0)
return;
var doctors = new List<Doctor>
{
new Doctor(_guidGenerator.Create(), "Dr. Smith", "Cardiology", "smith@clinic.com"),
new Doctor(_guidGenerator.Create(), "Dr. Jones", "Pediatrics", "jones@clinic.com"),
};
foreach (var doctor in doctors)
{
await _doctorRepository.InsertAsync(doctor);
}
}
}
```
### Test Data Seeding
```csharp
public class ClinicTestDataSeedContributor : IDataSeedContributor, ITransientDependency
{
public static readonly Guid TestPatientId = Guid.Parse("2e701e62-0953-4dd3-910b-dc6cc93ccb0d");
public static readonly Guid TestDoctorId = Guid.Parse("3a801f73-1064-5ee4-a21c-ed7dd4ddc1e");
public async Task SeedAsync(DataSeedContext context)
{
await _patientRepository.InsertAsync(new Patient(
TestPatientId, "Test", "Patient", "test@example.com", DateTime.Now.AddYears(-30)));
await _doctorRepository.InsertAsync(new Doctor(
TestDoctorId, "Test Doctor", "General", "doctor@example.com"));
}
}
```
## Best Practices
1. **Encapsulate state** - Use private setters and domain methods
2. **Validate in constructor** - Ensure entity is always valid
3. **Use value objects** - For complex properties (Address, Money)
4. **Domain logic in entity** - Simple rules belong in the entity
5. **Domain service** - For cross-entity logic
6. **Custom repository** - Only when you need custom queries
7. **Idempotent seeding** - Always check before inserting
## Related Skills
- `abp-service-patterns` - Application layer patterns
- `abp-infrastructure-patterns` - Cross-cutting concerns
- `efcore-patterns` - Database configurationRelated Skills
advanced-patterns
Advanced T-SQL patterns and techniques for SQL Server. Use this skill when: (1) User needs help with CTEs or recursive queries, (2) User asks about APPLY operator, (3) User wants MERGE or OUTPUT clause help, (4) User works with temporal tables, (5) User needs In-Memory OLTP guidance, (6) User asks about advanced grouping (ROLLUP, CUBE, GROUPING SETS).
advanced-js-mocking-patterns
Advanced mocking patterns for Jest and Vitest including module mocking, spies, and fake timers. PROACTIVELY activate for: (1) Module mocking, (2) Partial mocking with spies, (3) Mock lifecycle management, (4) Fake timers for time-dependent code, (5) Complex mock implementations. Triggers: "jest.mock", "vi.mock", "spyOn", "fakeTimers", "mockImplementation", "mockReturnValue", "mock lifecycle"
Advanced GetX Patterns
Advanced GetX features including Workers, GetxService, SmartManagement, GetConnect, GetSocket, bindings composition, and testing patterns
add-ravendb-identity-store
Implement ASP.NET Identity user and refresh token stores backed by RavenDB
add-entity-field
Add a new field to an existing entity/model with related service and endpoint updates
add-domain-entity
Create domain layer components: models, repository interfaces, marshallers, and implementations. Use when: (1) adding domain model in internal/domain/model/, (2) creating repository interface in internal/domain/repository/, (3) implementing repository with marshaller in internal/infrastructure/{db}/. This is Step 2 of CRUD workflow (after add-database-table, before add-api-endpoint).
patterns/adapter
Adapter (Wrapper) Pattern pattern for C development
ActiveRecord Query Patterns
Complete guide to ActiveRecord query optimization, associations, scopes, and PostgreSQL-specific patterns. Use this skill when writing database queries, designing model associations, creating migrations, optimizing query performance, or debugging N+1 queries and grouping errors.
Action Cable & WebSocket Patterns
Real-time WebSocket features with Action Cable in Rails. Use when: (1) Building real-time chat, (2) Live notifications/presence, (3) Broadcasting model updates, (4) WebSocket authorization. Trigger keywords: Action Cable, WebSocket, real-time, channels, broadcasting, stream, subscriptions, presence, cable
accessibility-patterns
Build inclusive web experiences following WCAG guidelines. Covers semantic HTML, ARIA, keyboard navigation, color contrast, and testing strategies. Triggers on accessibility, a11y, WCAG, screen readers, or inclusive design requests.
access-control-patterns
[STUB - Not implemented] Access control auditing with IDOR detection, RBAC/ABAC patterns, and privilege escalation prevention. PROACTIVELY activate for: [TODO: Define on implementation]. Triggers: [TODO: Define on implementation]
acc-stability-patterns-knowledge
Stability Patterns knowledge base. Provides patterns, antipatterns, and PHP-specific guidelines for Circuit Breaker, Retry, Rate Limiter, Bulkhead, and resilience audits.