clean-architecture-validator
Validate .NET API project structure follows Clean Architecture with proper layer separation and dependencies
What this skill does
# Clean Architecture Validator Skill
Use this skill to validate that a .NET API project follows StyleMate's Clean Architecture standards with proper layer separation and dependencies.
## When to Use
- After creating a new .NET API project
- When refactoring an existing API
- During code reviews
- Troubleshooting dependency issues
- Ensuring architectural compliance
## What This Skill Does
### 1. Structure Validation
Checks for required directories:
- `Domain/` (no dependencies)
- `Application/` (depends on Domain only)
- `Infrastructure/` (implements interfaces)
- `Controllers/` (orchestration layer)
### 2. Dependency Analysis
Validates that:
- Domain has NO dependencies on other layers
- Application depends only on Domain
- Infrastructure implements Domain/Application interfaces
- Controllers depend on all layers for orchestration
- No circular dependencies exist
### 3. Entity Validation
Ensures Domain entities:
- Contain business logic
- Have proper value objects
- Define domain interfaces
- Use proper encapsulation
### 4. Service Layer Check
Validates Application services:
- Define clear DTOs
- Implement business workflows
- Use dependency injection properly
- Return appropriate types (not entities)
### 5. Infrastructure Compliance
Checks Infrastructure layer:
- Proper DbContext configuration
- Repository pattern implementation
- External service integrations
- Configuration management
## Expected Inputs
- Path to the .NET API project
- Context name for the service
## Deliverables
- Validation report with pass/fail status
- List of violations with recommendations
- Suggested refactoring steps (if needed)
- Compliance checklist
## Example Usage
```
Please validate the staff-api project structure to ensure it follows Clean Architecture.
The project is located at ./staff/staff-api/
```
## Validation Checklist
### Domain Layer ✓
- [ ] Entities/ directory exists with domain models
- [ ] Interfaces/ directory for domain contracts
- [ ] No dependencies on other layers
- [ ] Business logic in entities
- [ ] Value objects properly defined
### Application Layer ✓
- [ ] DTOs/ directory for data transfer
- [ ] Services/ directory for business workflows
- [ ] Interfaces/ for service contracts
- [ ] Only depends on Domain layer
- [ ] No infrastructure concerns
### Infrastructure Layer ✓
- [ ] Data/ directory with DbContext
- [ ] Repositories/ implementing domain interfaces
- [ ] Services/ for external integrations
- [ ] Implements Application/Domain interfaces
- [ ] EF Core configurations present
### API Layer (Controllers) ✓
- [ ] Controllers orchestrate workflow
- [ ] Proper routing with [Route] attributes
- [ ] JWT authorization on endpoints
- [ ] Input validation with FluentValidation
- [ ] Returns DTOs, not entities
### Configuration ✓
- [ ] Program.cs properly configures DI
- [ ] appsettings.json has required sections
- [ ] Middleware pipeline configured
- [ ] Health checks implemented
- [ ] Swagger with JWT scheme
## Common Violations
### ❌ Domain depending on Infrastructure
```csharp
// WRONG: Domain referencing DbContext
using Infrastructure.Data;
public class Employee
{
public void Save(AppDbContext context) { } // ❌
}
```
### ✓ Correct Domain
```csharp
// CORRECT: Domain with no dependencies
public class Employee
{
public Guid Id { get; private set; }
public string Name { get; private set; }
// Business logic only
public void UpdateName(string newName)
{
if (string.IsNullOrWhiteSpace(newName))
throw new ArgumentException("Name required");
Name = newName;
}
}
```
### ❌ Returning Entities from Controllers
```csharp
// WRONG: Exposing domain entities
[HttpGet]
public async Task<Employee> Get(Guid id) // ❌
{
return await _service.GetEmployee(id);
}
```
### ✓ Correct Controller Pattern
```csharp
// CORRECT: Returning DTOs
[HttpGet]
public async Task<EmployeeDto> Get(Guid id) // ✓
{
return await _service.GetEmployee(id);
}
```
## Remediation Steps
When violations found:
1. Identify the violating layer
2. Move code to appropriate layer
3. Define interfaces where needed
4. Update dependency injection
5. Revalidate structure
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.