solution-generator

Generate a .NET solution scaffold with CQRS handlers and entity configurations.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/I-Synergy/AI --skill solution-generator-i-synergy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-generator
Source: https://github.com/I-Synergy/AI/tree/main/.github/skills/solution-generator
Command: npx skills add https://github.com/I-Synergy/AI --skill solution-generator-i-synergy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a complete .NET solution scaffold from architecture documents and design interrogation outputs, reducing manual setup time and ensuring consistent project structure.

Core Features & Use Cases

  • Maps architecture documents to a full solution layout including projects, entities, and CQRS handlers.
  • Produces entity configurations and service registrations following Clean Architecture patterns.
  • Use Case: After completing design interrogation, generate the scaffold to begin implementation with ready-to-fill stubs.

Quick Start

Say generate the solution after you've completed the design interrogation and arch docs to scaffold the project structure.

Frequently Asked Questions about solution-generator

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

FAQPage Schema
How do I scaffold a .NET solution from architecture docs?

To scaffold a .NET solution from architecture docs, map the architecture documents and design interrogation outputs into a project structure with entities, CQRS handlers, and service registrations. This translates ubiquitous language and use cases into a ready-to-implement Clean Architecture layout.

What is the best way to generate CQRS handlers and entity configurations across bounded contexts?

Generating CQRS handlers and entity configurations across bounded contexts requires translating architecture documents into a full solution layout. Mapping ubiquitous language and use cases produces ready-to-fill stubs and service registrations following Clean Architecture patterns.

Can I generate a .NET project layout without completing design interrogation first?

Generating a .NET project layout requires design interrogation outputs and architecture documents as input. Without completing the design interrogation to define ubiquitous language and use cases, the solution structure and CQRS stubs cannot be accurately mapped.

How do I use architecture docs to create a Clean Architecture project structure with service registrations?

Use architecture docs to create a Clean Architecture project structure by translating the documents into project layout, entity mappings, and service registrations. The generated scaffold delivers CQRS stubs and entity configurations following the template's specific patterns.

Does the generated .NET scaffold include ready-to-fill stubs for bounded contexts?

The generated .NET scaffold includes ready-to-fill CQRS stubs and entity configurations across bounded contexts. It delivers the complete project layout and service registrations needed to begin implementation immediately after architecture documents are finalized.