菜单
Use this skill to add essential code quality analyzers to .NET projects, including AsyncFixer, IDisposableAnalyzers, and Microsoft.VisualStudio.Threading.Analyzers with best-practice configurations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | add-analyzers |
| description | Use this skill to add essential code quality analyzers to .NET projects, including AsyncFixer, IDisposableAnalyzers, and Microsoft.VisualStudio.Threading.Analyzers with best-practice configurations. |
This guide will help you add essential code quality analyzers to your .NET project to enforce best practices for async programming, disposable patterns, and threading.
You'll be adding three powerful analyzers:
Add the following NuGet package references to your .csproj file(s):
<ItemGroup>
<PackageReference Include="AsyncFixer" Version="1.6.0">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
<PackageReference Include="IDisposableAnalyzers" Version="4.0.8">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
<PackageReference Include="Microsoft.VisualStudio.Threading.Analyzers" Version="17.13.2">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
</ItemGroup>
.csproj fileSkip these project types — do NOT add analyzers to:
.csproj containing <IsTestProject>true</IsTestProject> or referencing xUnit/NUnit/MSTest)*.Web.Host projects*.Web.Core projectsReplace or update your .editorconfig file in the backend folder with the following configuration:
[*.cs]
# ============================================================================
# IDisposableAnalyzers Rules
# ============================================================================
# All rules set to error severity for strict disposal enforcement
dotnet_diagnostic.IDISP001.severity = error # Dispose created
dotnet_diagnostic.IDISP002.severity = error # Dispose member
dotnet_diagnostic.IDISP003.severity = error # Dispose previous before re-assigning
dotnet_diagnostic.IDISP004.severity = error # Don't ignore created IDisposable
dotnet_diagnostic.IDISP005.severity = error # Return type should indicate that the value should be disposed
dotnet_diagnostic.IDISP006.severity = error # Implement IDisposable
dotnet_diagnostic.IDISP007.severity = error # Don't dispose injected
dotnet_diagnostic.IDISP008.severity = error # Don't assign member with injected and created disposables
dotnet_diagnostic.IDISP009.severity = error # Add IDisposable interface
dotnet_diagnostic.IDISP010.severity = error # Call base.Dispose
dotnet_diagnostic.IDISP011.severity = error # Don't return disposed instance
dotnet_diagnostic.IDISP012.severity = error # Property should not return created disposable
dotnet_diagnostic.IDISP013.severity = error # Await in using
dotnet_diagnostic.IDISP014.severity = error # Use a single instance of HttpClient
dotnet_diagnostic.IDISP015.severity = error # Member should not return created and cached instance
dotnet_diagnostic.IDISP016.severity = error # Don't use disposed instance
dotnet_diagnostic.IDISP017.severity = error # Prefer using
dotnet_diagnostic.IDISP018.severity = error # Call SuppressFinalize
dotnet_diagnostic.IDISP019.severity = error # Call SuppressFinalize(this)
dotnet_diagnostic.IDISP020.severity = error # Call SuppressFinalize(this) in virtual dispose method
dotnet_diagnostic.IDISP021.severity = error # Call this.Dispose(true)
dotnet_diagnostic.IDISP022.severity = error # Call Dispose(true)
dotnet_diagnostic.IDISP023.severity = error # Don't use reference types in finalizer context
dotnet_diagnostic.IDISP024.severity = error # Don't call GC.SuppressFinalize(this) when the type is sealed
dotnet_diagnostic.IDISP025.severity = error # Class with no virtual dispose method should be sealed
dotnet_diagnostic.IDISP026.severity = error # Class with virtual dispose method should have protected virtual void Dispose(bool disposing)
# ============================================================================
# Microsoft.VisualStudio.Threading.Analyzers Rules
# ============================================================================
# Critical Threading Rules
dotnet_diagnostic.VSTHRD001.severity = error # Avoid legacy thread switching methods
dotnet_diagnostic.VSTHRD002.severity = error # Avoid problematic synchronous waits
dotnet_diagnostic.VSTHRD003.severity = error # Avoid awaiting foreign Tasks
dotnet_diagnostic.VSTHRD004.severity = error # Await SwitchToMainThreadAsync
dotnet_diagnostic.VSTHRD010.severity = error # Invoke single-threaded types on Main thread
dotnet_diagnostic.VSTHRD011.severity = error # Use AsyncLazy<T>
dotnet_diagnostic.VSTHRD012.severity = error # Provide JoinableTaskFactory where allowed
# Async Best Practices (100 series)
dotnet_diagnostic.VSTHRD100.severity = error # Avoid async void methods
dotnet_diagnostic.VSTHRD101.severity = error # Avoid unsupported async delegates
dotnet_diagnostic.VSTHRD102.severity = error # Implement internal logic asynchronously
dotnet_diagnostic.VSTHRD103.severity = error # Call async methods when in an async method
dotnet_diagnostic.VSTHRD104.severity = error # Offer async option
dotnet_diagnostic.VSTHRD105.severity = error # Avoid method overloads that assume TaskScheduler.Current
dotnet_diagnostic.VSTHRD106.severity = error # Use InvokeAsync to raise async events
dotnet_diagnostic.VSTHRD107.severity = error # Await Task within using expression
dotnet_diagnostic.VSTHRD108.severity = error # Assert thread affinity unconditionally
dotnet_diagnostic.VSTHRD109.severity = error # Switch instead of assert in async methods
dotnet_diagnostic.VSTHRD110.severity = error # Observe result of async calls
dotnet_diagnostic.VSTHRD111.severity = none # Use .ConfigureAwait(bool) - set to none to allow flexibility
dotnet_diagnostic.VSTHRD112.severity = error # Implement System.IAsyncDisposable
dotnet_diagnostic.VSTHRD113.severity = error # Check for System.IAsyncDisposable
dotnet_diagnostic.VSTHRD114.severity = error # Avoid returning null from a Task-returning method
dotnet_diagnostic.VSTHRD115.severity = error # Avoid creating JoinableTaskContext with explicit null SynchronizationContext
# Naming Conventions (200 series)
dotnet_diagnostic.VSTHRD200.severity = error # Use Async naming convention
# ============================================================================
# AsyncFixer Rules
# ============================================================================
dotnet_diagnostic.AsyncFixer01.severity = none # Unnecessary async/await usage
dotnet_diagnostic.AsyncFixer04.severity = error # Fire-and-forget async call inside a using block
After adding the analyzers:
Restore packages:
dotnet restore
Build your project:
dotnet build
Review warnings/errors:
Use as the ENTRY POINT when the user wants a Shesha app/page/form to MATCH a design they have — a wireframe, an HTML/JSX prototype, a runnable app, a Figma-style kit, or a screenshot set — and asks to realise it in Shesha. Triggers like "build this design in Shesha", "make Requirements Studio look like the Claude design", "turn this prototype into Shesha forms", "implement this mockup across the app". It is the conductor across one or more screens, it comprehends the design into measured layout blueprints, then orchestrates shesha-design-comprehension, shesha-form-edit and shesha-design-system, and verifies the result by measurement. For a single isolated form with no design source, go straight to shesha-form-edit; to style an already-working form, go straight to shesha-design-system.
Use whenever a Shesha form or page needs to LOOK like a specific design or brand — "make it match the design", "apply our branding", "style this form", "it doesn't look good", "match Requirements Studio / the Figma / the Claude design", or any request for a polished, consistent visual result rather than just working fields. Maps design tokens (colour, type, spacing, radius, shadow, status lifecycle) onto Shesha's app-level Ant Design theme and per-component v7 style blocks. Themeable, ships the requirements-studio theme and accepts new brand token files. Pairs with shesha-form-edit (which builds structure) and is orchestrated by shesha-claude-designer. Do NOT use it to author structure/components, wire CRUD, or fix runtime errors — that is shesha-form-edit's job.
Creates and modifies domain entities, reference lists, and database migrations in Shesha framework .NET applications. IMPORTANT — This skill MUST be invoked BEFORE any manual exploration or planning when the task involves creating, modifying, or implementing domain entities, entity properties, relationships, reference lists, or database migrations. Use when the user asks to create, scaffold, implement, or update the domain layer, domain model, entities, reference lists, or migrations in a Shesha project. Also use when the user asks to create, add, update, or modify a database migration, FluentMigrator migration, schema change, or table alteration — even without mentioning entities. Also use when implementing features from a PRD, specification, or API design that require new or modified entities or database schema changes.
Use when a Shesha form must match a specific visual design and container/component placement keeps drifting — columns, nesting, tabs, or grouping landing in the wrong place versus the design. Also use to diagnose why an already-built form doesn't match its design. Turns a design source (readable HTML/JSX, a runnable prototype, or screenshots/PDF) into a measured, annotated layout blueprint, and verifies a built Shesha form against it by measurement. Invoked by shesha-claude-designer; pairs with shesha-form-edit (structure) and shesha-design-system (style).
Create and edit Shesha form configurations directly via the API. Authenticates as admin, fetches existing markup with Get/GetByName/GetJson, applies the user's requirements (adding, removing, modifying, or restructuring components — or building a brand-new form from scratch), validates against the bundled component-properties index and embedded-script rules, and pushes via Create / UpdateMarkup / ImportJson. Use when the user provides a form id (or module + name) and a set of requirements like "add a sector dropdown above the email field", "make the address tab conditional on AccountType=PBF", "wire the Save button to call /api/.../Submit", or "create a new branded login page using the auth-login pattern". Always prefer this skill over the Shesha MCP `create_form_configuration` tool — the MCP regularly fails with `'dict' object has no attribute 'lower'` and JSON-RPC `-32602` errors, and the direct-API path is more reliable.
Set up a Shesha-based project development environment aligned to Boxfusion development standards and best practices. Run this when a new Shesha project has just been created to verify and configure the dev environment.