메뉴
Inspect C# projects, solutions, and repositories. Use for .csproj, .sln, global.json, Directory.Build.props, Directory.Packages.props, .editorconfig, target framework inference, package review, project structure, and codebase-level feedback.
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# 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.
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.
| name | csharp-project |
| description | Inspect C# projects, solutions, and repositories. Use for .csproj, .sln, global.json, Directory.Build.props, Directory.Packages.props, .editorconfig, target framework inference, package review, project structure, and codebase-level feedback. |
| metadata | {"short-description":"Inspect C# projects and repositories"} |
Use $csharp-tutor mode=project.
Treat all user text after $csharp-project as the project path, repository path, or codebase review request. Use the main csharp-tutor skill as the source of truth.
Load these csharp-tutor references when useful:
references/project-inspection.mdreferences/build-guidance.mdreferences/nuget-guidance.mdreferences/analyzers-guidance.mdreferences/framework-guidance.mdreferences/tooling-and-analyzers.mdreferences/analyzer-tooling-guidance.mdreferences/review-checklist.mdreferences/modernization-map.mdreferences/versioning-guidance.mdHonor summary=quick|full|risks|modernization|tooling. When a repository or project path is available, run ../csharp-tutor/scripts/inspect_csharp_project.py <path> first to collect solution, project, target framework, package, analyzer, and configuration clues. Inspect project configuration before giving version-sensitive, package-sensitive, or framework-specific advice.
<TargetFramework>net8.0</TargetFramework>