abp-core

Implement ABP core conventions in .NET modules for DI, localization, and async patterns.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/afonsoft/VideoChat --skill abp-core-afonsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abp-core
Source: https://github.com/afonsoft/VideoChat/tree/main/.agents/skills/abp-core
Command: npx skills add https://github.com/afonsoft/VideoChat --skill abp-core-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This convention pack helps teams standardize ABP project structure by enforcing module registration, DI patterns, and consistent base classes (ApplicationService, DomainService, AbpController), plus time handling and localization practices.

Core Features & Use Cases

  • Standardized module system and DI registration across ABP projects.
  • Guidelines for using IClock, BusinessException, and localization to ensure testability and correctness.
  • Practical patterns for repository usage, base classes, and exception handling in scalable solutions.

Quick Start

Provide a minimal ABP module scaffold that demonstrates the core conventions.

Frequently Asked Questions about abp-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up ABP module registration and dependency injection in a new .NET project?

To set up ABP module registration, you apply conventional module configuration and automatic service registration patterns. This ensures consistent dependency injection across modular .NET applications by standardizing base-class usage and DI patterns.

What is the recommended way to use base classes for ABP application services and domain services?

The recommended approach for ABP application services and domain services is inheriting from standard base classes like ApplicationService and DomainService. Using these ensures correct async patterns, automatic DI registration, and consistent localization handling.

How do I handle exceptions and time correctly in an ABP modular application?

Handling exceptions and time in ABP modular apps requires using BusinessException for errors and IClock for time. These conventions ensure testability and correctness across domain and application services.

Can I apply ABP core conventions to an existing .NET module without breaking current functionality?

You can apply ABP core conventions to existing .NET modules by incrementally adopting module configuration and base-class patterns. This standardizes DI and localization without breaking functionality if implemented per ABP best practices.

What's the best way to structure repository usage in scalable ABP solutions?

The best way to structure repository usage in scalable ABP solutions is following practical repository patterns alongside standard exception handling. This maintains consistency and testability across domain and application service layers.

Why does my ABP application service not automatically register for dependency injection?

ABP application services may not automatically register for dependency injection if standard module configuration is missing or base classes are incorrectly applied. Enforcing automatic service registration conventions resolves this DI issue.