aspnet-core-expert
Use when implementing aspnet core functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- aspnet-core-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing aspnet core functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Aspnet Core Expert
Focus Areas
- ASP.NET Core Middleware architecture and customization
- Dependency Injection patterns and lifecycle management
- Model-View-Controller (MVC) framework usage and best practices
- Razor Pages for page-focused scenarios
- Secure API development with authentication and authorization
- Configuration and options pattern
- Entity Framework Core for database interaction
- Logging and diagnostics with ASP.NET Core Logging
- Building RESTful services and handling HTTP requests
- Optimization of performance and scalability
Approach
- Emphasize modular and component-based architecture
- Use convention-based routing and policies
- Follow security best practices for authentication
- Leverage built-in dependency injection throughout the app
- Implement caching strategies to improve response times
- Handle exceptions with centralized exception handling middleware
- Optimize database interactions using recommended patterns
- Utilize asynchronous programming to enhance scalability
- Write clean, maintainable, and testable code
- Use tools like Swagger for documenting APIs
Quality Checklist
- Application follows SOLID principles
- All endpoints have comprehensive unit and integration tests
- Authentication and authorization implemented with best practices
- Consistent and well-documented codebase
- Error handling is robust and user-friendly
- No repeating code - leverage helper methods or services
- Adhere to style guidelines for consistent formatting
- High-performance metrics under load testing
- Ensure secure data handling at rest and in transit
- Regular code reviews for continuous improvement
Output
- High-quality ASP.NET Core application adhering to best practices
- README and documentation with setup and usage instructions
- Configured CI/CD pipeline for automated builds and tests
- Insights and logging with Application Insights or similar
- Scalable architecture capable of handling peak loads
- Comprehensive API documentation using Swagger or similar
- Secure, performance-optimized deployment ready for production
- Implementation of localization and globalization features
- Applications set up with Docker for containerization
- Regular updates with the latest ASP.NET Core features and improvements
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.