skills.rest
diegoknsk
diegoknskCOMMUNITY
Explore all skills by this author →
GitHub

architecture-clean-70-dotnet

Create a 70% Clean Architecture structure for .NET projects with API and Lambda entry points.

Updated Feb 1, 2026
Search Tags:#architecture#dotnet#ports#clean-architecture#project-structure#multientrypoint#solution-folders
One-click install
npx skills add https://github.com/diegoknsk/video-processing-engine-video-management-lambda --skill architecture-clean-70-dotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-clean-70-dotnet
Source: https://github.com/diegoknsk/video-processing-engine-video-management-lambda/tree/main/.cursor/skills/architecture-clean-70-dotnet
Command: npx skills add https://github.com/diegoknsk/video-processing-engine-video-management-lambda --skill architecture-clean-70-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estrutura padrão para projetos .NET visando Clean Architecture pragmática (~70%) com múltiplos pontos de entrada (API + Lambda) e pastas físicas que espelham as Solution Folders, acelerando a organização, governança e escalabilidade do projeto.

Core Features & Use Cases

  • Estrutura de pastas física: src/Core, src/Infra, src/InterfacesExternas, tests, com mapeamento claro para Core, Infra e InterfacesExternas.
  • Entradas múltiplas: API e Lambda convivem no mesmo repositório mantendo a separação de responsabilidades via Ports e implementations de Infra.
  • Regras de dependência: Domain é puro, Application depende de Domain, Infra depende de Application, Api/Lambda dependem de Application, Domain e Infra.
  • Casos de uso: ideal para iniciar novos projetos que adotam 70% Clean Architecture, definindo macro-estrutura, organização de pastas e dependências entre Camadas.

Quick Start

Crie um novo repositório e estruture-o como src/Core, src/Infra, src/InterfacesExternas, tests, com um Solution que espelhe essas pastas e dois pontos de entrada (API e Lambda) conectados via Ports.

Frequently Asked Questions about architecture-clean-70-dotnet

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

FAQPage Schema
How do I structure a .NET project for Clean Architecture with multiple entry points?▼

Structure your .NET project using physical folders like src/Core, src/Infra, and src/InterfacesExternas that mirror Solution Folders, allowing API and Lambda entry points to coexist while maintaining separate responsibilities via Ports.

What are the dependency rules for a pragmatic .NET Clean Architecture?▼

In a pragmatic .NET Clean Architecture, Domain remains pure, Application depends on Domain, Infra depends on Application, and both API and Lambda entry points depend on Application, Domain, and Infra layers.

When should I use a 70% Clean Architecture structure for a .NET application?▼

Use a 70% Clean Architecture structure when starting new .NET projects that require organized macro-structure, clear folder conventions, and scalable governance without the overhead of a full Clean Architecture implementation.

How do Ports connect UseCases to Infrastructure in .NET Clean Architecture?▼

Ports connect UseCases to Infra implementations by defining interfaces in the Application layer, allowing the physical Infra layer to provide concrete implementations that the API or Lambda entry points can inject.

Can I host an API and AWS Lambda in the same .NET Clean Architecture repository?▼

Yes, API and Lambda can coexist in the same .NET repository. The pragmatic 70% Clean Architecture maintains separation of responsibilities through a Ports-based architecture and distinct physical folder mappings.

What is the difference between Solution Folders and physical folders in this .NET Clean Architecture layout?▼

The pragmatic .NET Clean Architecture layout mirrors Solution Folders with physical folders like src/Core, src/Infra, and src/InterfacesExternas, accelerating project organization and ensuring the file system matches the logical macro-structure.

Related Skills

Explore More Software Engineering Skills→
shahdanishshahdanish

project-structure

Establish .NET solution layout conventions with centralized build and package configuration.

Community
Intermediate
EmilLindforsEmilLindfors
2

hexagonal-advisor

Analyze Rust code for hexagonal architecture violations and ports-and-adapters separation.

Community
Advanced
AxGordAxGord
5

aws-lambda

Resolve .NET deployment challenges on AWS Lambda with networking and logging guidance.

Community
Advanced
NinaVerdeNinaVerde

Architecture Auditor

Audit Flutter feature modules for Clean Architecture and Riverpod compliance.

Community
Basic