Guidelines and patterns for maintaining the .NET SphereIntegrationHub solution.
Install
mkdir -p .claude/skills/dotnet-pinedatec-eu && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17258" && unzip -o skill.zip -d .claude/skills/dotnet-pinedatec-eu && rm skill.zipInstalls to .claude/skills/dotnet-pinedatec-eu
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Work on the .NET solution for SphereIntegrationHub. Use this when editing services, components, JSON data, or tests.Key capabilities
- →Enforce CancellationToken as the last parameter in method signatures
- →Ensure adherence to SOLID principles
- →Promote descriptive variable naming
- →Order methods as public, protected, then private
- →Avoid magic numbers and strings by using constants
How it works
The skill enforces architectural rules for .NET development within the SphereIntegrationHub solution, covering parameter ordering, SOLID principles, variable naming, method ordering, and the use of constants. It also guides unit testing practices.
Inputs & outputs
When to use dotnet
- →Editing services in SphereIntegrationHub
- →Writing unit tests for .NET components
- →Configuring integration hub workflows
- →Refactoring .NET code following SOLID
About this skill
.NET
Main structure
- CLI tool:
src/SphereIntegrationHub(Application). - Tests:
tests/SphereIntegrationHub.cli.tests(xUnit).
Considerations
- If a method has a
CancellationToken, it must be the last parameter in the method signature. - SOLID principles must be followed.
- Variables must be descriptive and clear, without being excessively long.
- The order of methods in classes must be: public, protected, then private.
- Magic numbers, strings, etc. must be avoided. Use
private constwhen elements are exclusive to a class, or, if shared, aXxxxConstsclass withinternal constmembers and reduced visibility. - When possible, components should use a fluent style for construction/configuration.
- Methods must have clearly bounded responsibilities; actions should be focused and the code readable, split into small chunks (ideally no more than 50 lines of code).
Tests
- Reusable, associated fixtures must be used, with methods that create common elements for multiple tests, reducing complexity and improving readability.
- Tests must be unit tests, using mocks or WireMock (for endpoints).
- Interfaces of the elements under test must be used, for example:
IWorkflowExecutor executor = new WorkflowExecutor(), ensuring that the interface is fully implemented and complete.
When not to use it
- →When the method has a CancellationToken that is not the last parameter
- →When SOLID principles are not followed
- →When variables are not descriptive or are excessively long
Limitations
- →CancellationToken must be the last parameter in method signatures.
- →SOLID principles must be followed.
- →Methods must have clearly bounded responsibilities.
How it compares
This skill provides specific architectural and coding standards for .NET development, ensuring consistency and maintainability within the SphereIntegrationHub solution, which goes beyond general .NET development guidelines.
Compared to similar skills
dotnet side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dotnet (this skill) | 0 | 6mo | No flags | Intermediate |
| dotnet-architect | 12 | 3mo | No flags | Advanced |
| dotnet-backend-patterns | 7 | 4mo | No flags | Advanced |
| azure-resource-manager-postgresql-dotnet | 1 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
dotnet-architect
sickn33
Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use PROACTIVELY for .NET API development, code review, or architecture decisions.
dotnet-backend-patterns
wshobson
Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.
azure-resource-manager-postgresql-dotnet
microsoft
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for PostgreSQL", "PostgreSQL database management", "PostgreSQL firewall", "PostgreSQL backup", "Postgres".
azure-resource-manager-sql-dotnet
microsoft
Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: "SQL server", "create SQL database", "manage SQL resources", "ARM SQL", "SqlServerResource", "provision Azure SQL", "elastic pool", "firewall rule".
orleans
managedcode
Build or review distributed .NET applications with Orleans grains, silos, persistence, streaming, reminders, placement, transactions, serialization, event sourcing, testing, and cloud-native hosting.
appsettings
punk-link
Rules for modifying ASP.NET Core configuration files (appsettings*.json) in the Warp project. Use when: adding, removing, or changing any configuration key in appsettings files; creating new Options classes that bind to configuration; the user mentions 'appsettings', 'configuration', 'options', 'con