package-conventions

Estrelas26

Forks1

Atualizado3 de maio de 2026 às 17:28

NuGet package and project file conventions for CSharpEssentials. Use when modifying .csproj, Directory.Packages.props, or Directory.Build.props.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

senrecep

senrecep/CSharpEssentials

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	package-conventions
description	NuGet package and project file conventions for CSharpEssentials. Use when modifying .csproj, Directory.Packages.props, or Directory.Build.props.

Package & Project Conventions

All package versions live in Directory.Packages.props. Never set Version= directly in a .csproj.
Use <PackageReference Include="Foo" /> (no version) in projects; version is resolved centrally.
Target framework changes require updating the README.MD framework support table.
<IsPackable>true</IsPackable> is the default (set in Directory.Build.props); only override to false for test/example projects.
New packages must follow the existing metadata pattern in Directory.Build.props (Authors, Copyright, PackageLicenseExpression, etc.).
GeneratePackageOnBuild is false — packing is done explicitly via dotnet pack or the publish script.
Keep <IncludeSymbols>true</IncludeSymbols> and <SymbolPackageFormat>snupkg</SymbolPackageFormat> on all packable projects.

Mais deste repositório

mesmo repositório

csharpessentials-maybe

senrecep/CSharpEssentials

Use when representing optional values explicitly — Maybe<T> as a null-safe container, Maybe.From()/FromTry() for creation, HasValue/HasNoValue, Map/Bind chaining, TapNone for None-side effects, Match for consumption, and ToMaybeResult() to bridge into the Result pattern.

2026-05-3126

csharpessentials-results

senrecep/CSharpEssentials

Use when handling operation outcomes without exceptions — Result and Result<T> for success/failure, railway-oriented chaining with Then/ThenAsync/Ensure, Match for consumption, and Result.And/Or for combining multiple results.

2026-05-3126

csharpessentials-rules

senrecep/CSharpEssentials

Use when composing business validation logic — define rules as classes, Func fields, or inline lambdas; combine with .And()/.Or()/.Linear()/.Next(); evaluate with RuleEngine.Evaluate(); branch with RuleEngine.If().

2026-05-3126

csharpessentials-these

senrecep/CSharpEssentials

Use when modeling partial success — These<TError, TValue> holds Left (error only), Right (value only), or Both (error + value), enabling scenarios where a result can partially succeed while carrying warnings. Use FromResult to bridge from Result<T>, ToResult/ToResultLenient to bridge back, and Partition to split collections.

2026-05-3126

csharpessentials-time

senrecep/CSharpEssentials

Use when you need testable time — IDateTimeProvider wraps clock access so production code uses DateTimeProvider while tests use the built-in FakeDateTimeProvider to freeze/advance/set the clock; also provides .ToDateOnly() and .ToTimeOnly() DateTime extension methods.

2026-05-3126

csharpessentials-mediator

senrecep/CSharpEssentials

Use when adding cross-cutting pipeline behaviors to CQRS handlers — ValidationBehavior (CSharpEssentials.Validation, throws EnhancedValidationException), LoggingBehavior (ILoggableRequest), ExceptionHandlingBehavior (auto-converts exceptions to Result.Failure for Result-returning handlers), CachingBehavior (ICacheable with IDistributedCache), and TransactionScopeBehavior (ITransactionalRequest).

2026-05-3126

Execute qualquer Skill com um clique