القائمة
Use for C# language level, nullable usage, and file/folder layout consistent with Contentstack.Management.Core.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when reviewing or preparing a pull request for contentstack-management-dotnet.
Use for branches, CI, build/test scripts, and NuGet release flow in contentstack-management-dotnet.
Use for the contentstack.management.aspnetcore package, HttpClient/DI registration with ASP.NET Core.
Use when changing or using the CMA client API, authentication, or NuGet package surface for Contentstack.Management.Core.
Use when building or updating DocFX API documentation under docfx_project for this repository.
Use for target frameworks, assembly signing, NuGet packaging, OS-specific builds, and HTTP pipeline overview in Contentstack.Management.Core.
| name | csharp-style |
| description | Use for C# language level, nullable usage, and file/folder layout consistent with Contentstack.Management.Core. |
Contentstack.Management.Core or test projects.LangVersion in contentstack.management.core.csproj).Nullable is enable). Prefer explicit nullability on public APIs (?, ! only when justified and consistent with existing code).Follow existing top-level folders:
Services/ — API-facing service classes by domain (stack, organization, OAuth, etc.).Models/ — DTOs and domain models (including Models/Fields/).Runtime/ — pipeline, HTTP handlers, execution context.Exceptions/ — SDK exception types.Abstractions/, Queryable/, Utils/ — as used today.New features should land in the same folder that similar code uses; avoid new root folders without team agreement.
async/await patterns consistent with neighboring methods when adding asynchronous APIs.[TestClass], [TestMethod], [ClassInitialize] where the suite requires shared setup (see integration tests).AssertLogger in integration tests) where applicable.