create-module

Generate Shesha Domain and Application module projects with csproj files and references.

3|20|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/shesha-io/shesha-plugins --skill create-module
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-module
Source: https://github.com/shesha-io/shesha-plugins/tree/main/plugins/shesha-developer/skills/create-module
Command: npx skills add https://github.com/shesha-io/shesha-plugins --skill create-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a repeatable, standards-compliant starting point for Shesha modules by generating the Domain and Application projects with the correct structure and references.

Core Features & Use Cases

  • Scenario-aware scaffolding: detects existing Domain/Application projects and creates missing components or full module structures as needed.
  • Convention-driven structure: outputs {Organization}.{ModuleName}.Domain and {Organization}.{ModuleName}.Application folders with pre-configured csproj files, assembly info, module classes, and web references.
  • Guided integration: prepares the solution and project references wiring skeletons for Web.Core, ready for later customization.
  • Use Case: starting a new module like DEP under Org results in Org.DEP.Domain and Org.DEP.Application with ready-to-compile projects.

Quick Start

Provide the organization name and the new module name to generate both Domain and Application projects.

Frequently Asked Questions about create-module

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

FAQPage Schema
How do I scaffold a new Shesha module with Domain and Application projects?▼

To scaffold a Shesha module, provide the organization name and module name to generate paired Domain and Application projects. This creates fully structured folders with pre-configured csproj files, assembly info, module classes, and Web.Core reference wiring.

What naming conventions does Shesha module scaffolding enforce for project structure?▼

Shesha module scaffolding enforces an {Organization}.{ModuleName}.Domain and {Organization}.{ModuleName}.Application naming convention. This structure ensures standards-compliant project pairs ready for compilation and integration within your existing solution.

Can I generate only the missing Domain or Application project for an existing Shesha module?▼

Yes, the scaffolding process is scenario-aware and detects existing Domain or Application projects. It can generate missing components individually or create a full module structure as needed, adapting to your current solution state.

Do I need to manually wire Web.Core references after creating a new dotnet module?▼

No, manual wiring is not needed. The scaffolding prepares the solution and project reference skeletons for Web.Core automatically, creating ready-to-customize integration points alongside the generated csproj files and module classes.

What's the best way to structure a modular dotnet project under an organization namespace?▼

The best way is using convention-driven scaffolding to output paired Domain and Application projects under an {Organization}.{ModuleName} namespace. This generates a repeatable, standards-compliant starting point with correct csproj files and web references.

Why does my generated Shesha module include separate Domain and Application csproj files?▼

Separate Domain and Application csproj files enforce modular design by splitting business logic layers. This convention-driven structure outputs distinct projects with assembly info and module classes, ensuring a clean separation of concerns for your module.