菜单
Teach and review C# Roslyn analyzers, .editorconfig, nullable warnings, warning levels, TreatWarningsAsErrors, WarningsAsErrors, NoWarn, EnforceCodeStyleInBuild, dotnet format, analyzer packages, StyleCop, SonarAnalyzer, Roslynator, code quality gates, and CI analyzer enforcement.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Show available C# Tutor skills, modes, examples, and usage guidance. Use when the user asks what C# Tutor can do, which C# skill to use, or how to invoke the C# Tutor skill family from the Codex picker.
Teach and review C# for developers learning the language. Use when users ask C# questions, request explanations of C# or .NET concepts, share C# code or codebases for feedback, need examples, cheat sheets, exercises, debugging labs, mini projects, interview prep, tips, bug-prevention guidance, vulnerability checks, code quality improvements, or want help applying object-oriented design, clean code, SOLID, design patterns, API design, async, concurrency, LINQ, generics, collections, architecture, build tooling, logging, NuGet packaging, NativeAOT, trimming, analyzer configuration, version compatibility, tooling, performance, maintainability, scalability, newer C#/.NET features, or official Microsoft C# and .NET documentation.
Teach and review C# and .NET NativeAOT, trimming, single-file publishing, linker warnings, reflection risks, serialization compatibility, source generators, publish settings, runtime identifiers, deployment constraints, and AOT/trimming readiness for apps and libraries.
Teach and review C# public API design. Use for method signatures, naming, nullability, exceptions, result types, cancellation, async APIs, records, DTOs, versioning, binary compatibility, XML docs, NuGet packaging, library boundaries, and maintainable API surfaces.
Teach and review C# application architecture. Use for clean architecture, layered architecture, vertical slice architecture, domain services, application services, DTO boundaries, dependency direction, modularity, scalability, maintainability, testability, and avoiding overengineering.
Teach and review ASP.NET Core C# web applications. Use for controllers, minimal APIs, Razor Pages, middleware, routing, model binding, validation, authentication, authorization, configuration, logging, dependency injection, error handling, API design, and web security or performance questions.
| name | csharp-analyzers |
| description | Teach and review C# Roslyn analyzers, .editorconfig, nullable warnings, warning levels, TreatWarningsAsErrors, WarningsAsErrors, NoWarn, EnforceCodeStyleInBuild, dotnet format, analyzer packages, StyleCop, SonarAnalyzer, Roslynator, code quality gates, and CI analyzer enforcement. |
| metadata | {"short-description":"C# analyzers and .editorconfig help"} |
Use $csharp-tutor mode=analyzers.
Treat all user text after $csharp-analyzers as the analyzer warning, .editorconfig, build warning, nullable warning, formatting, suppression, warning-as-error, analyzer package, or CI quality gate question. Use the main csharp-tutor skill as the source of truth.
Load these csharp-tutor references when useful:
references/analyzers-guidance.mdreferences/analyzer-tooling-guidance.mdreferences/tooling-and-analyzers.mdreferences/nullability-guidance.mdreferences/style-guidance.mdreferences/build-guidance.mdreferences/security-review-map.mdreferences/official-sources.mdClassify each diagnostic before advising: compiler, nullable, correctness, security, performance, maintainability, style, or formatting. Do not recommend making all warnings errors until the project has a clean and sustainable baseline.
dotnet format --verify-no-changes