This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This repository contains ABP Framework-specific development assistance tools for both Claude Code and Cursor.ai. It includes specialized AI assistants and rules designed to enhance productivity when working with ABP Framework projects.
- Claude Code: Specialized assistants in
.claude/agents/directory - Cursor.ai: Traditional .mdc rule files in organized directories
abp-ddd-general.md- General ABP and Domain-Driven Design assistantabp-domain-layer.md- Domain layer development specialistabp-application-layer.md- Application services, DTOs, and mapping specialistabp-authorization.md- Security and permissions specialistabp-mvc-razor.md- MVC Razor Pages and UI specialistabp-blazor-server.md- Blazor Server components, real-time features, and modern UI specialistabp-angular.md- Angular frontend development with TypeScript, reactive patterns, and ABP integration specialist
abp-ddd-rules/- Core Domain-Driven Design rules for ABP projectsabp-fundamentals/- Core ABP framework feature rulesabp-infrastructure/- Infrastructure layer specific rulesabp-userinterface-mvc-razor/- MVC Razor Pages UI layer rulesabp-userinterface-blazor-server/- Blazor Server component and real-time feature rulesabp-userinterface-angular/- Angular frontend development, routing, and state management rules
Claude Code assistants are Markdown files with YAML frontmatter that define:
- Name: Assistant identifier
- Description: Purpose and specialization
- Tools: Available tool permissions (usually "*" for full access)
- Content: Detailed expertise, patterns, examples, and guidance
Each assistant provides:
- Domain Expertise: Deep knowledge of specific ABP areas
- Code Patterns: Examples of correct and incorrect implementations
- Architecture Guidance: Layer separation and dependency management
- Best Practices: ABP-specific conventions and optimizations
- Layered Architecture: Domain, Application, Infrastructure, and UI layers with clear boundaries
- DDD Integration: Rich domain models inheriting from ABP base classes (
AggregateRoot,FullAuditedAggregateRoot) - Entity Framework: Uses ABP's repository patterns and EF Core integration
- Authorization: Leverages ABP's permission system and identity framework
- Multi-tenancy: Built-in support for tenant isolation and management
- Domain Layer: Entity modeling, business logic encapsulation, aggregate boundaries
- Application Layer: DTO design, service patterns, validation, authorization
- Infrastructure: Repository implementation, EF Core configuration, external service integration
- UI Layer: MVC/Razor patterns, Blazor Server components, Angular frontend, client-side integration, theme system
- Frontend Development: Angular components, services, routing, authentication, and state management
- Real-time Features: SignalR integration, live updates, real-time communication
- Testing: Unit tests, integration tests, ABP test framework usage
- Assistant Enhancement: Modify existing assistants in
.claude/agents/directory - New Assistants: Create new specialized assistants for specific ABP areas
- Testing: Validate assistants by using them in actual ABP projects
- Documentation: Update patterns and examples based on real-world usage
- Rule Development: Create or modify .mdc files in appropriate directories
- Installation: Copy rules to
~/.cursor/rules/directory for Cursor IDE - Testing: Validate rules by using them in actual ABP projects
This repository contains guidance and rules rather than executable code, so there are no build, test, or compilation commands needed.
When working with assistants in .claude/agents/:
- Use Markdown format with YAML frontmatter
- Include comprehensive code examples (both valid and invalid)
- Provide detailed rationale for patterns and anti-patterns
- Maintain consistent structure across all assistants
- Focus on practical, actionable guidance
When working with .mdc files:
- Preserve the existing directory structure and naming conventions
- Maintain the .mdc file format with proper YAML frontmatter
- Include both valid and invalid examples in rule documentation
- Follow the established pattern of providing rationale for each rule
- Ensure rules target specific file globs (e.g.,
**/Domain/**/*.csfor domain rules)
- This is an experimental project with rules primarily focused on MVC Razor Pages
- Rules are created using AI and documentation research but haven't been fully tested in major ABP projects
- The repository serves as a community starting point for ABP-specific development assistance
- Contributors are welcome to expand coverage for other UI platforms and enhance existing rules