adding-backend-entity

Automate adding .NET 10 Clean Architecture backend entities across all layers.

2|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/MGurtD/lilith --skill adding-backend-entity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adding-backend-entity
Source: https://github.com/MGurtD/lilith/tree/main/.github/skills/adding-backend-entity
Command: npx skills add https://github.com/MGurtD/lilith --skill adding-backend-entity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates and standardizes the end-to-end process of introducing new backend entities in a .NET 10 Clean Architecture, covering Domain, Application Contracts, Application, Infrastructure, and Api layers, ensuring consistent repository patterns, configuration, migrations, and DI wiring.

Core Features & Use Cases

  • Supports both Generic Repository (Pattern A) and Specific Repository (Pattern B) workflows, including entity definition, unit of work updates, service and controller generation, and migration creation.
  • Provides an integrated validation script to verify all required steps are implemented and properly wired.
  • Includes scenario references and best-practice patterns to guide complex header-detail or lifecycle-enabled entities.

Quick Start

Run the validate_entity.py script to confirm an entity passes all steps and consult the SCENARIOS.md guidance for typical implementations.

Frequently Asked Questions about adding-backend-entity

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

FAQPage Schema
How do I add a new backend entity in a .NET Clean Architecture?

Adding a backend entity in .NET 10 Clean Architecture requires updating domain, persistence, application, infrastructure, and API layers. This Skill automates the end-to-end process across 11 steps, ensuring correct configuration, service wiring, and migration creation.

What is the difference between generic repository and specific repository patterns in .NET?

Generic repository (Pattern A) provides broad data access, while specific repository (Pattern B) offers tailored operations. This Skill supports both workflows, automatically applying the correct configuration, unit of work updates, and dependency injection registration for your chosen .NET pattern.

How do I validate that a new .NET entity has all required Clean Architecture dependencies wired?

Validating .NET entity wiring involves checking domain, application, and infrastructure dependencies. This Skill provides a built-in validation script that confirms an entity passes all 11 required steps and is properly registered across the Clean Architecture layers.

Can I use this Skill to generate EF Core migrations for complex header-detail entities?

Yes, this .NET 10 entity automation handles EF Core migration creation for complex header-detail or lifecycle-enabled entities. It includes scenario references and best-practice patterns to guide developers through implementing these advanced structures correctly.

What steps are required to wire dependency injection for a new .NET backend entity?

Wiring dependency injection for a .NET entity requires updating service registrations across application and infrastructure layers. This Skill automates DI registration and service wiring as part of its 11-step end-to-end entity creation process.