yeeehaooo/create-snippet
skills/dotnet/templates/create-snippet-skill/SKILL.md
Create reusable .NET atomic capability code snippets that can be directly copied and pasted. Use when: - Creating single-purpose code snippets - Building reusable code templates - Implementing atomic technical capabilities - Creating copy-pasteable code blocks - Building snippet library for common patterns Triggers: "create snippet", "code snippet", "reusable snippet", "atomic snippet", "copy-paste code"
development
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add yeeehaooo/WorkSpace create-snippetInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 11:05 PM18.1s2 files scanned
SKILL.md
- name:
- create-snippet
- description:
- |
- Triggers:
- create snippet", "code snippet", "reusable snippet", "atomic snippet", "copy-paste code
- type:
- template
- version:
- 1.2.1
Create Snippet
Purpose
Create atomic capability code snippets that can be directly copied and pasted.
Scope
Applies to:
- Code snippets
- Reusable templates
- Single technical capabilities
Rules
- Single responsibility (one snippet solves one thing)
- No project-specific names (use placeholders like
{Entity}) - No multi-step processes
- No architecture decisions
- No dependencies on project-specific modules
- Directly copy-pasteable
Anti-Patterns
- Including multi-step workflows
- Creating entire modules
- Using specific business names
- Including architecture decisions
- Dependencies on specific modules
Template Structure
Snippet Template:
public class {Entity}Repository : I{Entity}Repository
{
private readonly IDbContext _db;
public {Entity}Repository(IDbContext db)
{
_db = db;
}
public async Task<{Entity}?> GetByIdAsync(Guid id, CancellationToken ct = default)
{
return await _db.Set<{Entity}>().FindAsync(new object[] { id }, ct);
}
public async Task AddAsync({Entity} entity, CancellationToken ct = default)
{
await _db.Set<{Entity}>().AddAsync(entity, ct);
}
}
Notes
- Use placeholders for entity names
- Keep snippets focused on one capability
- Make snippets directly usable
- Avoid project-specific dependencies
Related Skills
yeeehaooo/create-docker-compose
development
VerifiedTrustedCommunity
Create Docker Compose configuration for containerized .NET application development and deployment. Use when: - Containerizing .NET applications - Setting up local development environment with dependencies - Creating multi-container setups (API + DB + Redis) - Defining service dependencies and networking - Building docker-compose.yml for development or production Triggers: "docker compose", "containerize", "multi-container", "docker-compose.yml", "docker setup"
SKILL.mdUpdated Apr 22, 2026
yeeehaooo/create-api-adapter
tools
VerifiedTrustedCommunity
Create adapter structure for integrating third-party APIs in Clean Architecture applications. Use when: - Integrating external APIs or services - Creating HTTP client adapters for third-party services - Implementing API integration with error handling - Setting up adapter pattern for external dependencies - Building resilient external service integrations Triggers: "api adapter", "third-party api", "external service", "http client adapter", "api integration"
SKILL.mdUpdated Apr 22, 2026
yeeehaooo/dmis
development
VerifiedTrustedCommunity
Enterprise backend structure built on Clean Architecture, DDD, CQRS, and Vertical Slice API Design with Dapper-first persistence. Use when: - Creating new enterprise backend projects - Implementing Clean Architecture with DDD and CQRS - Building vertical slice API endpoints - Using Dapper as primary persistence mechanism - Organizing modules by UseCase-driven and Model-driven separation Triggers: "dmis structure", "clean architecture", "enterprise backend", "DDD CQRS", "vertical slice", "dapper"
SKILL.mdUpdated Apr 22, 2026
yeeehaooo/clean
development
VerifiedTrustedCommunity
Layered architecture with vertical slice organization following Clean Architecture principles. Use when: - Creating new .NET backend projects requiring strict layer separation - Building applications with Clean Architecture principles - Implementing vertical slice API organization - Projects requiring framework-agnostic domain layer - Applications that need CQRS support Triggers: "clean architecture", "layered architecture", "vertical slice", "clean structure", "layer separation"
SKILL.mdUpdated Apr 22, 2026