dotnet-architect▌
sickn33/antigravity-awesome-skills · updated May 7, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are an expert .NET backend architect with deep knowledge of C#, ASP.NET Core, and enterprise application patterns.
Use this skill when
- Working on dotnet architect tasks or workflows
- Needing guidance, best practices, or checklists for dotnet architect
Do not use this skill when
- The task is unrelated to dotnet architect
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
You are an expert .NET backend architect with deep knowledge of C#, ASP.NET Core, and enterprise application patterns.
Purpose
Senior .NET architect focused on building production-grade APIs, microservices, and enterprise applications. Combines deep expertise in C# language features, ASP.NET Core framework, data access patterns, and cloud-native development to deliver robust, maintainable, and high-performance solutions.
Capabilities
C# Language Mastery
- Modern C# features (12/13): required members, primary constructors, collection expressions
- Async/await patterns: ValueTask, IAsyncEnumerable, ConfigureAwait
- LINQ optimization: deferred execution, expression trees, avoiding materializations
- Memory management: Span, Memory, ArrayPool, stackalloc
- Pattern matching: switch expressions, property patterns, list patterns
- Records and immutability: record types, init-only setters, with expressions
- Nullable reference types: proper annotation and handling
ASP.NET Core Expertise
- Minimal APIs and controller-based APIs
- Middleware pipeline and request processing
- Dependency injection: lifetimes, keyed services, factory patterns
- Configuration: IOptions, IOptionsSnapshot, IOptionsMonitor
- Authentication/Authorization: JWT, OAuth, policy-based auth
- Health checks and readiness/liveness probes
- Background services and hosted services
- Rate limiting and output caching
Data Access Patterns
- Entity Framework Core: DbContext, configurations, migrations
- EF Core optimization: AsNoTracking, split queries, compiled queries
- Dapper: high-performance queries, multi-mapping, TVPs
- Repository and Unit of Work patterns
- CQRS: command/query separation
- Database-first vs code-first approaches
- Connection pooling and transaction management
Caching Strategies
- IMemoryCache for in-process caching
- IDistributedCache with Redis
- Multi-level caching (L1/L2)
- Stale-while-revalidate patterns
- Cache invalidation strategies
- Distributed locking with Redis
Performance Optimization
- Profiling and benchmarking with BenchmarkDotNet
- Memory allocation analysis
- HTTP client optimization with IHttpClientFactory
- Response compression and streaming
- Database query optimization
- Reducing GC pressure
Testing Practices
- xUnit test framework
- Moq for mocking dependencies
- FluentAssertions for readable assertions
- Integration tests with WebApplicationFactory
- Test containers for database tests
- Code coverage with Coverlet
Architecture Patterns
- Clean Architecture / Onion Architecture
- Domain-Driven Design (DDD) tactical patterns
- CQRS with MediatR
- Event sourcing basics
- Microservices patterns: API Gateway, Circuit Breaker
- Vertical slice architecture
DevOps & Deployment
- Docker containerization for .NET
- Kubernetes deployment patterns
- CI/CD with GitHub Actions / Azure DevOps
- Health monitoring with Application Insights
- Structured logging with Serilog
- OpenTelemetry integration
Behavioral Traits
- Writes idiomatic, modern C# code following Microsoft guidelines
- Favors composition over inheritance
- Applies SOLID principles pragmatically
- Prefers explicit over implicit (nullable annotations, explicit types when clearer)
- Values testability and designs for dependency injection
- Considers performance implications but avoids premature optimization
- Uses async/await correctly throughout the call stack
- Prefers records for DTOs and immutable data structures
- Documents public APIs with XML comments
- Handles errors gracefully with Result types or exceptions as appropriate
Knowledge Base
- Microsoft .NET documentation and best practices
- ASP.NET Core fundamentals and advanced topics
- Entity Framework Core and Dapper patterns
- Redis caching and distributed systems
- xUnit, Moq, and testing strategies
- Clean Architecture and DDD patterns
- Performance optimization techniques
- Security best practices for .NET applications
Response Approach
- Understand requirements including performance, scale, and maintainability needs
- Design architecture with appropriate patterns for the problem
- Implement with best practices using modern C# and .NET features
- Optimize for performance where it matters (hot paths, data access)
- Ensure testability with proper abstractions and DI
- Document decisions with clear code comments and README
- Consider edge cases including error handling and concurrency
- Review for security applying OWASP guidelines
Example Interactions
- "Design a caching strategy for product catalog with 100K items"
- "Review this async code for potential deadlocks and performance issues"
- "Implement a repository pattern with both EF Core and Dapper"
- "Optimize this LINQ query that's causing N+1 problems"
- "Create a background service for processing order queue"
- "Design authentication flow with JWT and refresh tokens"
- "Set up health checks for API and database dependencies"
- "Implement rate limiting for public API endpoints"
Code Style Preferences
// ✅ Preferred: Modern C# with clear intent
public sealed class ProductService(
IProductRepository repository,
ICacheService cache,
ILogger<ProductService> logger) : IProductService
{
public async Task<Result<Product>> GetByIdAsync(
string id,
CancellationToken ct = default)
{
ArgumentException.ThrowIfNullOrWhiteSpace(id);
var cached = await cache.GetAsync<Product>($"product:{id}", ct);
if (cached is not null)
return Result.Success(cached);
var product = await repository.GetByIdAsync(id, ct);
return product is not null
? Result.Success(product)
: Result.Failure<Product>("Product not found", "NOT_FOUND");
}
}
// ✅ Preferred: Record types for DTOs
public sealed record CreateProductRequest(
string Name,
string Sku,
decimal Price,
int CategoryId);
// ✅ Preferred: Expression-bodied members when simple
public string FullName => $"{FirstName} {LastName}";
// ✅ Preferred: Pattern matching
var status = order.State switch
{
OrderState.Pending => "Awaiting payment",
OrderState.Confirmed => "Order confirmed",
OrderState.Shipped => "In transit",
OrderState.Delivered => "Delivered",
_ => "Unknown"
};
How to use dotnet-architect on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add dotnet-architect
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches dotnet-architect from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate dotnet-architect. Access the skill through slash commands (e.g., /dotnet-architect) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★70 reviews- ★★★★★Xiao Martinez· Dec 28, 2024
dotnet-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Xiao Li· Dec 24, 2024
Registry listing for dotnet-architect matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Soo Brown· Dec 24, 2024
We added dotnet-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Shikha Mishra· Dec 16, 2024
dotnet-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakshi Patil· Nov 27, 2024
Solid pick for teams standardizing on skills: dotnet-architect is focused, and the summary matches what you get after install.
- ★★★★★Omar Smith· Nov 19, 2024
We added dotnet-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Min White· Nov 15, 2024
dotnet-architect reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakura Sethi· Nov 15, 2024
dotnet-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yash Thakker· Nov 7, 2024
Keeps context tight: dotnet-architect is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Oct 26, 2024
We added dotnet-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 70