Official agent skill

SDK Conventions

by aws in aws/aws-sdk-net

The public-API contract SmithyDotNet-generated code must match against the shipping AWS SDK for .NET - what must match vs.

OfficialApache-2.0Auto-check passedBackend & APIs

Install SDK Conventions

skills CLI
$ npx skills add aws/aws-sdk-net --skill sdk-conventions -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aws/aws-sdk-net sdk-conventions --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aws/aws-sdk-net.git skills-src && mkdir -p .claude/skills && cp -r skills-src/generator/SmithyDotNet/skills/sdk-conventions .claude/skills/sdk-conventions && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sdk-conventions
GitHub stars
145
Token cost
~6.3k tokens
SKILL.md length
2,883 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

The public-API contract SmithyDotNet-generated code must match against the shipping AWS SDK for .NET - what must match vs.

  • Works in 6 steps: Default (no args) → (string message) → (string message, Exception innerException) → …
  • Tasks that involve API design
  • SKILL.md covers Reviewing Generated Output, What Must Match (Public API…, What Can Differ and Pragma Warnings, plus 15 more sections
  • Reaches docs.aws.amazon.com

What it does

SDK Conventions is an agent skill from aws/aws-sdk-net, published by the product's own GitHub organization. The public-API contract SmithyDotNet-generated code must match against the shipping AWS SDK for .NET - what must match vs. what can differ. Use before writing or changing any SmithyDotNet writer.

Its SKILL.md is about 6.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering API design. It works with Amazon Web Services and .NET. The repository describes itself as: The official AWS SDK for .NET. For more information on the AWS SDK for .NET, see our web site:. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve API design

Example prompts

  • “/sdk-conventions”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Default (no args)
  2. (string message)
  3. (string message, Exception innerException)
  4. (Exception innerException)
  5. (string message, Exception innerException, ErrorType, string errorCode, string requestId, HttpStatusCode)
  6. (string message, ErrorType, string errorCode, string requestId, HttpStatusCode)

What it can do on your machine

Read from SKILL.md and the folder at commit f36df89. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are csharp).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • docs.aws.amazon.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SDK Conventions loads about 6.3k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 2,883 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~6.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aws/aws-sdk-net at commit f36df89, republished under its Apache-2.0 licence (© aws). 2,883 words, ~6,277 tokens.

Download SKILL.mdSave it as .claude/skills/sdk-conventions/SKILL.md (or your agent's skills folder).
name
sdk-conventions
description
The public-API contract SmithyDotNet-generated code must match against the shipping AWS SDK for .NET - what must match vs. what can differ. Use before writing or changing any SmithyDotNet writer.

Skill: .NET SDK Conventions

Reviewing Generated Output

When reviewing a service migration's generated output, open and diff every single generated file — every operation's request marshaller and response unmarshaller, every model, exception, and client file. No sampling. Reviewing one operation and generalizing "clean" to its neighbors is how regressions ship. Thousands of files is not a reason to skip any.

The public API surface can be identical while the wire behavior changes. AssemblyComparer and "the public surface is unchanged" only check the public contract; they cannot see marshaller/unmarshaller bodies — ResourcePath, query parameters, headers, serialization. A clean AssemblyComparer is necessary, not sufficient; it is not a substitute for reading the diff.

A removed line in generated output is a red flag — investigate it, do not wave it through. Real example: the generator dropping request.AddSubResource("aws_iam", "t") and folding the query literal into request.ResourcePath = "/token?aws_iam=t" left the public API identical while silently changing the request sent to the wire (? gets percent-encoded, dropping the flag).

What Must Match (Public API Contract)

  • Public class/interface names and their base types. An event structure (a non-error member of a @streaming union) implements Amazon.Runtime.EventStreams.IEventStreamEvent, fully qualified (no using) so it can't clash with a per-stream {Namespace}.Model.IEventStreamEvent. A request event stream's input member becomes a Func<Task<I{Union}Event>> {Member}Publisher property: it keeps any modeled [AWSProperty]/[Obsolete] but has no IsSet (the marshaller wires the Func unconditionally). Its doc content matches C2J.
  • Public property names, types, and nullability
  • Public method signatures (name, parameters, return type)
  • [AWSProperty] attributes on public members (Required, Min, Max)
  • XML doc comments on public types and members (content, not formatting)
  • partial modifier on all generated types
  • Namespace structure ({Namespace}, {Namespace}.Model)
  • internal bool IsSet{Property}() per member — the public AWSSDKUtils.IsPropertySet reflection API and existing marshallers invoke these by name

What Can Differ

  • Whitespace, indentation, blank lines (the Roslyn formatter runs on every C# file whose raw output differs from the file on disk; emitting exact spacing lets a run skip it)
  • File names — prefer {TypeName}.g.cs to distinguish generated files
  • Backing fields and other private helpers (the generator omits them — see Property Pattern below)
  • using directive order
  • #region blocks (purely cosmetic)
  • Code comments outside XML docs

Pragma Warnings

The SDK builds with warnings-as-errors. Generated files must include #pragma warning disable for warnings that would otherwise break the build. The exact set doesn't need to match the current SDK file-for-file, but the output must compile cleanly. Common ones:

  • CS0612 / CS0618 — obsolete/deprecated member usage (generated code may reference deprecated shapes)
  • CS1570 — malformed XML doc comments (common with complex HTML from @documentation traits)

License Header

Every generated file starts with the full Apache 2.0 license block followed by the "Do not modify this file. This file is generated from the {model-filename} service model." notice, where {model-filename} is the Smithy model file name (e.g. cloudtrail-data-2021-08-11.normal.json). The exact text lives in Writers/FileHeader.cs.

Naming Rules

Which Name Goes Where

A service has two derived names, equal for most services:

  • BaseName (C2J ClassName, metadata.json's base-name) → the generated type names: client, config, exception/request bases, endpoint types. Model classes go in {Namespace}.Model.
  • ServiceName (C2J ServiceFolderName, the namespace minus Amazon.) → everything else: AWSSDK.{X} package names, sdk/src|test/Services/{X} trees, _sdk-versions.json keys, {X}.slnx, the endpoint tests [TestCategory], and the paginator factory types (I{X}PaginatorFactory — C2J's templates use ServiceNameRoot there).

They diverge when metadata.json overrides the namespace: sesv2 has class AmazonSimpleEmailServiceV2Client but package/folder/paginators SimpleEmailV2. When adding a name to a writer, check the shipping SDK for which of the two it follows.

Class and Member Names
  • Shape names → PascalCase class names (Smithy shape names are already PascalCase). The service rename map wins when it has an entry for the shape; error codes still use the shape name
  • Member names → PascalCase property names. Smithy uses camelCase (eventData), .NET uses PascalCase (EventData)
  • The conversion: capitalize the first letter of the Smithy member name
  • Acronyms are preserved as-is from the Smithy model. Example: eventID → EventID (not EventId)
  • A response member named ContentLength is omitted from the response class — AmazonWebServiceResponse already declares it — but the response unmarshaller still assigns the inherited property. Response-only, matching C2J (the MediaStoreData case).
Client Names
  • Interface: IAmazon{BaseName} (e.g. IAmazonCloudTrailData)
  • Class: Amazon{BaseName}Client (e.g. AmazonCloudTrailDataClient)
  • Config: Amazon{BaseName}Config
  • Service exception base: Amazon{BaseName}Exception
  • Service request base: Amazon{BaseName}Request

File Layout

Generated files go under Generated/. Prefer .g.cs suffix:

Generated/
  IAmazon{BaseName}.g.cs
  Amazon{BaseName}Client.g.cs
  Amazon{BaseName}Config.cs            # plain .cs so CI's Amazon*Config.cs glob stages it
  Amazon{BaseName}Exception.g.cs
  Model/
    Amazon{BaseName}Request.g.cs       # empty service request base
    {OperationName}Request.g.cs
    {OperationName}Response.g.cs
    {ShapeName}.g.cs
    {ExceptionName}.g.cs

A structure that doubles as an operation input/output normally gets only its {Op}Request/{Op}Response wrappers — no {ShapeName}.g.cs. Exception: when other generated code references the shape through a member (directly or as a list/map element), the standalone class is emitted too, because member properties are typed with the plain class name (C2J parity: drs SourceServer has one, kinesis EnhancedMonitoringOutput does not).

Doc Samples

DocSamplesWriter and DocSampleMetadataWriter emit docgenerator/AWSSDKDocSamples/{ServiceName}/{ServiceName}.GeneratedSamples.cs and {ServiceName}.GeneratedSamples.extra.xml from smithy.api#examples, rendering values as C2J's Example.cs does but with the SDK's types, so a copied sample compiles once placeholders like <data> are filled in. Both are written unformatted (BatchGenerator passes format: false): the samples file is never compiled and can hold placeholders like <binary data> that the Roslyn formatter would mangle. A service with no examples, or S3 (its samples are hand-written), gets no files, so an existing sample file stays as it is; examples the model lacks but C2J had are a model gap. Example keys are matched to members (TypeMapper.ResolveMembers) ignoring case after CustomizationTransform, so, as in C2J, a member renamed by emitPropertyName (beyond case) drops out of the sample. The samples are built before anything is written, so a bad example fails the service before anything is deleted, and written only once its code has generated.

Differences from C2J:

  • Region ids are {Operation}-{n} (the trait has no example id). They only link an .extra.xml entry to its code. Each is unique, unlike C2J's repeated example-1, which made the docs build (it takes the first matching #region) show the first sample's code for every later one.
  • Keys are written ordinal-sorted; examples.json's order is sorted for about 92% of objects.
  • Which examples exist, and their order within an operation, follow the trait.
  • examples.json comments (C2J's // comment after an assignment) are lost: the trait has no such field.
  • Response locals are typed as the response properties are (int?, Stream, the enum's class); C2J used non-nullable scalars, MemoryStream and string. Locals that are C# keywords are escaped (@event).
  • A timestamp prints its 24-hour time and milliseconds, and a number is read as epoch seconds (or DateTime.UtcNow if it's out of range); C2J printed a 12-hour hour, dropped milliseconds and wrote DateTime.UtcNow for any number. A fractional float gets f.
  • A request event stream is omitted: its Func publisher property can't be written from example data.
  • A document value renders as global::Amazon.Runtime.Documents.Document with its content, using its collection initializer; C2J rendered an empty initializer of a class that doesn't exist.
  • String literals are fully C# escaped, and titles and documentation escape &, < and > (titles also ") and drop characters XML 1.0 can't carry; C2J escaped only quotes, so a backslash, newline or & produced broken code or XML.
  • The writers' own layout follows CodeWriter (platform newlines, 2-space XML indent); documentation text is written as it is. The docs build parses the XML and left-justifies each region, so the rendered docs don't change.

Event Streams

Protocol-independent; only the per-event payload (un)marshalling and the response unmarshaller's body differ (see marshalling). Each @streaming union is emitted once, however many operations share it.

Request (union sent as an operation input):

  • Gets the marker interface I{Union}Event plus a {Event} : I{Union}Event partial per event. The name comes from the union, never the operation (shipped: Lex V2 IStartConversationRequestEventStreamEvent), and is emitted once per union even when several operations send it (the protocol test client shares one union across four).
  • @error members get no partial: a client never sends an error event.

Response (union returned as an operation output):

  • {Union} is emitted as the EnumerableEventOutputStream<RuntimeEvent, {BaseName}EventStreamException> subclass (C2J parity; RuntimeEvent is the alias described under Both). Each union member is a mapping entry keyed on the member name verbatim (the wire :event-type; the dict is OrdinalIgnoreCase): @error members feed ExceptionMapping, the rest EventMapping plus a PascalCase {Name}Received handler. The union gets no plain model class and no structure unmarshaller (the response unmarshaller does new {Union}(context.Stream)); its events keep theirs.
  • The {Op}Response implements IDisposable and its dispose pattern releases the event stream member. Only when the operation also sends an event stream (bidi, or input-only) does it implement Amazon.Runtime.EventStreams.IEventInputStreamContextOwner (explicit SetEventInputStreamContext under a CA1033 suppression) and dispose the context first (C2J parity: Bedrock ConverseStreamResponse is AmazonWebServiceResponse, IDisposable, Lex V2 StartConversationResponse adds the owner interface).
  • Any response event stream gates the per-service {BaseName}EventStreamException.

Both:

  • Names are never adjusted for collisions: the protocol test client's union is named EventStream, so its marker is IEventStreamEvent, same simple name as the runtime's (the only runtime type an I{Union}Event can shadow). Anywhere under the .Model namespace (model classes, MarshallTransformations) the service's marker silently wins over the import; files outside it that import both namespaces (the client) hit CS0104. Every writer that needs the runtime's emits using RuntimeEvent = Amazon.Runtime.EventStreams.IEventStreamEvent; and uses RuntimeEvent. An alias named IEventStreamEvent would not help (a type in an enclosing namespace beats it too); one no shape can be named after does.

Base Types

Generated classInherits from
Client interfaceIAmazonService, IDisposable
Client classAmazonServiceClient, IAmazon{BaseName}
Service exception baseAmazonServiceException
Service request baseAmazonWebServiceRequest
Request classesAmazon{BaseName}Request (the service request base)
Response classesAmazonWebServiceResponse, plus , IDisposable when an output member is @streaming (emits a #region Dispose Pattern that disposes each streaming member's stream)
Structure classesNo base type (plain class)
Exception classesAmazon{BaseName}Exception (the service exception base)
Config class (Amazon{BaseName}Config)ClientConfig

All Types Are partial

Every generated class and interface uses the partial modifier.

Property Pattern

The public surface must match. Internal implementation can vary.

Required public surface:

csharp
/// <summary>
/// Gets and sets the property EventData. 
/// <para>
/// The content of an audit event...
/// </para>
/// </summary>
[AWSProperty(Required=true)]
public string EventData { get; set; }

/// <summary>
/// Checks to see if the EventData property is set.
/// </summary>
internal bool IsSetEventData() => this.EventData != null;

The generator emits auto-properties ({ get; set; }) plus an internal IsSet{Property}() method per member. The current SDK uses explicit backing fields, but the public surface (and the reflection API) only needs the property and the IsSet method — a backing field is not required.

Exception — emitIsSetProperties customization. A listed member (shape name → modeled member names) also gets a public bool Is{Property}Set { get; set; } whose accessors call InternalSDKUtils.GetIsSet/SetIsSet(value, ref field). A property can't be passed by ref, so the member gets a private _{Property} backing field (collections keep the InitializeCollections initializer) instead of an auto-property. IsSet{Property}() returns Is{Property}Set. Only nullable value types and collections have SetIsSet overloads; any other listed member throws. Doc text matches C2J's StructureGenerator.tt.

[AWSProperty] attribute rules:

  • Required=true when member has @required trait, unless it also carries @idempotencyToken (the SDK fills it)
  • Min=N when member has @length trait with min, or @range trait with min
  • Max=N when member has @length trait with max, or @range trait with max
  • Omit the attribute entirely if none of these traits are present
Show full SKILL.md (1,117 more words)Show less
Collection Properties

Collections use the AWSConfigs.InitializeCollections initializer to support both V4 (null default) and V3-compat (empty list default) modes. The matching IsSet encodes the V3/V4 "empty counts as set?" rule so callers see consistent behavior in both modes:

csharp
[AWSProperty(Required=true, Min=1, Max=100)]
public List<AuditEvent> AuditEvents { get; set; } = AWSConfigs.InitializeCollections ? new List<AuditEvent>() : null;

internal bool IsSetAuditEvents() => this.AuditEvents != null && (this.AuditEvents.Count > 0 || !AWSConfigs.InitializeCollections);

Customizations (*.customizations.json)

The .NET-owned override layer (not part of the shared, upstream Smithy model). A hook with a Smithy trait equivalent (a rename pins @jsonName), or a structural edit (a member-keyed renameShape), is folded into the model in-memory by CustomizationTransform.Apply before the ServiceIndex is built; every other hook is checked by CustomizationTransform.Validate and read from GenerationContext.Customizations by shape and member name where the member is resolved (TypeMapper.ResolveMembers), never stored on a shape. An unknown hook key fails deserialization (fail-closed) rather than silently diverging from C2J.

shapeSubstitutions.renameShape is applied first, as an entry in the service's rename map (the shape ID is unchanged, so targets still resolve). Every hook keys a renamed shape by its modeled name. C2J keys a renamed structure by its new name, so S3's entries for its renamed structures must be rekeyed on migration. Wire error codes keep the modeled name. A model that already renames the shape fails. A Smithy-only "Structure$member" key instead copies that member's target under the new name (QApps: one Action enum is C2J's PermissionInputActionEnum and PermissionOutputActionEnum); the original is dropped once nothing targets it.

  • What Smithy supports today is whatever Generation/Customizations/CustomizationsModel.cs parses; each hook's per-level behavior lives on that record, its Apply/Validate step, and its lookup.
  • What each hook means (and every hook C2J has) is documented in generator/customization-hooks.md.

Reference: Existing Generator

When implementing transformation logic (HTML sanitization, naming rules, type mapping, etc.), consult the existing C2J generator at generator/ServiceClientGeneratorLib/ to understand the correct behavior. Key files:

  • GeneratorHelpers.cs / Utils.cs — HTML processing, naming transforms
  • Member.cs — property naming, type resolution
  • Shape.cs / ExceptionShape.cs — shape naming conventions
  • Generators/SourceFiles/StructureGenerator.tt, Generators/SourceFiles/Exceptions/ExceptionSerialization.t4 — model and exception class output
  • Generators/Marshallers/*.tt — T4 templates showing exact output patterns

The new generator is a clean reimplementation, not a port — but the existing generator defines what "correct" looks like.

XML Documentation Comments

HTML Sanitization

The @documentation trait contains HTML. DocumentationFormatter.Cleanup ports the existing generator's CleanupDocumentation (ServiceClientGeneratorLib/Generators/BaseGenerator.cs). The transform, in order:

  • Collapse runs of whitespace (the source doc's newlines + indentation) to single spaces. The meaningful <para> line breaks are inserted afterward.
  • <code>...</code> → <c>...</c>
  • <p>...</p> → <para>...</para> (including <p> tags carrying attributes)
  • Strip <br>, <fullname>, <function>, <p/> (bare and attribute-carrying forms)
  • <i>...</i> → keep as-is
  • Remove <examples>...</examples> and <!-- ... --> snippets
  • Drop the leading <para>...</para> wrapper (the summary's first paragraph is unwrapped)
  • Soft-wrap at ~80 columns (break at the next space after a line exceeds 80 chars)

Note: HTML entities are NOT decoded (&amp; stays &amp;) — the existing generator does not decode them, so neither do we.

Type-Specific Summaries
  • Service interface/class: <para>Interface for accessing {BaseName}</para>, a blank /// line, then the service @documentation
  • Request class: Container for the parameters to the {OperationName} operation. then the operation @documentation
  • Response class: This is the response object from the {OperationName} operation.
  • Structure class: the shape's @documentation
Operation Method Docs

Each operation method includes an <exception cref="{full exception type}"> (body = the error shape's @documentation) per error, plus <seealso href="http://docs.aws.amazon.com/goto/WebAPI/{serviceId}-{apiVersion}/{OperationName}">REST API Reference for {OperationName} Operation</seealso>.

Exception Classes

Operation exceptions inherit from Amazon{BaseName}Exception (not directly from AmazonServiceException).

Must expose these public constructors:

  1. Default (no args)
  2. (string message)
  3. (string message, Exception innerException)
  4. (Exception innerException)
  5. (string message, Exception innerException, ErrorType, string errorCode, string requestId, HttpStatusCode)
  6. (string message, ErrorType, string errorCode, string requestId, HttpStatusCode)

Operation exceptions also include a #if !NETSTANDARD block containing:

  • [Serializable] attribute on the class
  • protected serialization constructor (SerializationInfo, StreamingContext) — deserializes each serialized exception member via info.GetValue, then calls base(info, context)
  • public override void GetObjectData(SerializationInfo, StreamingContext) carrying all three attributes as a unit: [System.Security.SecurityCritical] plus the CA2123 and CA2134 SuppressMessage attributes; body is base.GetObjectData(info, context) then info.AddValue(...) per additional member. The serialization constructor and GetObjectData are symmetric: both loop over the same member set, every modeled member except message (C2J parity), so base-owned RequestId/ErrorCode are serialized here even though they get no property (see "Exception Member Property Names"). Both are keyed on the .NET property name. For exceptions whose only member is message (e.g. all CloudTrail Data exceptions), both bodies contain only the base call.

The service-level exception base (Amazon{BaseName}Exception) inherits from AmazonServiceException, exposes the same six public constructors as operation exceptions, and includes [Serializable] plus the protected serialization constructor, but does not need its own GetObjectData override unless it adds serialized fields.

Exception Member Property Names

Canonical treatment lives in type-mapping's "Error Shape Members". Summary: errorType → property RequestErrorType (wire name unchanged); Retryable emitted with new; Equals gets new on any structure (not exception-specific); RequestId/ErrorCode get no property but stay in serialization and unmarshalling; every other member is emitted as-is even when it shadows an inherited property.

Retryable Errors

An error shape carrying the @retryable trait emits a public override that marks it retryable:

csharp
public override RetryableDetails Retryable { get; } = new RetryableDetails(<throttling>);

<throttling> is the trait's throttling value (true/false); an empty @retryable ({}) is retryable but not throttling (false). The base AmazonServiceException.Retryable returns null, so emitting a non-null RetryableDetails is what marks the exception retryable — errors without the trait emit no override. RetryableDetails resolves via Amazon.Runtime (already in the model file's usings).

Client Interface

Must expose:

  • Sync method (.NET Framework): {Op}Response {Op}({Op}Request request) per operation
  • Async method (all targets): Task<{Op}Response> {Op}Async({Op}Request request, CancellationToken cancellationToken = default)
  • HTTP/2 operations are the exception: the whole operation (sync + async, client + interface) is wrapped in #if NET8_0_OR_GREATER, since C2J omits h2 operations on .NET Framework and pre-net8 netstandard.
  • Endpoint DetermineServiceOperationEndpoint(AmazonWebServiceRequest request)
  • Static factory methods (#if NET8_0_OR_GREATER): CreateDefaultClientConfig() and CreateDefaultServiceClient(AWSCredentials, ClientConfig)

Use #if directives to include sync methods only for .NET Framework targets (#if NETFRAMEWORK).

Client Class

Must expose:

  • All constructors matching the current SDK pattern (default, region, config, credentials variants — 10 constructors total)
  • Sync method (.NET Framework): public virtual {Op}Response {Op}({Op}Request request) per operation
  • Async method (all targets): public virtual Task<{Op}Response> {Op}Async(...) per operation
  • HTTP/2 operations are the exception: the whole operation is wrapped in #if NET8_0_OR_GREATER, since C2J omits h2 operations on .NET Framework and pre-net8 netstandard.
  • DetermineServiceOperationEndpoint implementation
  • CustomizeRuntimePipeline override
  • ServiceMetadata property override

Use #if NETFRAMEWORK directives to include sync methods only for .NET Framework targets. Both sync and async methods are public virtual on the client class.

Endpoint Discovery

aws.api#clientEndpointDiscovery is legacy: only dynamodb, timestream-query and timestream-write use it, and new services use endpoint rule sets (Endpoints 2.0) instead. Matching C2J, each operation with aws.api#clientDiscoveredEndpoint (except the discovery operation itself) gets an {Op}EndpointDiscoveryMarshaller.g.cs and sets options.EndpointDiscoveryMarshaller and options.EndpointOperation; the client overrides EndpointOperation to call the discovery operation.

Anything those three services don't model fails generation (discovery ids, discovery input, renamed or swapped endpoint members, ...); see EndpointDiscoveryResolver and ClientClassWriter.WriteEndpointOperation.

C2J's {BaseName}EndpointDiscoveryMarshallingTests.cs is not generated: with no discovery ids it only checks the required flag against the C2J model, which the Smithy trait replaces.

© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in generator/SmithyDotNet/skills/sdk-conventions of aws/aws-sdk-net.

Open the folder on GitHubat commit f36df89

Compare with similar skills

SDK Conventions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

SDK Conventions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
SDK Conventions this skillaws/aws-sdk-net145—~6.3kAutomated safety check: PassApache-2.0
FoundatioFoundatioFx/Foundatio2.1k—~3.9kAutomated safety check: PassApache-2.0
.NET API Compatibility DesignAaronontheweb/dotnet-skills1.2k2 repos~2.7kAutomated safety check: PassMIT
.NET Aspire Explicit ConfigurationAaronontheweb/dotnet-skills1.2k1 repos~1.3kAutomated safety check: PassMIT
Csharp Nullable Reference TypesAaronontheweb/dotnet-skills1.2k1 repos~2.9kAutomated safety check: PassMIT
Generate Testability Wrappersdotnet/skills5.6k1 repos~3.9kAutomated safety check: PassMIT

Similar skills

  • Foundatio

    FoundatioFx/Foundatio

    A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.

    2.1k GitHub stars~3.9k tokensUpdated today
    Backend & APIsAuto-check passed
  • .NET API Compatibility Design

    Aaronontheweb/dotnet-skills

    Applies extend-only design rules to NuGet packages and distributed systems, covering source, binary and wire compatibility and how to deprecate members safely.

    1.2k GitHub starsUsed in 2 repos~2.7k tokens
    Backend & APIsAuto-check passed
  • .NET Aspire Explicit Configuration

    Aaronontheweb/dotnet-skills

    Wires .NET Aspire AppHost resources into explicit environment-variable configuration, keeping application code free of Aspire client packages and service discovery.

    1.2k GitHub starsUsed in 1 repo~1.3k tokens
    Backend & APIsAuto-check passed
  • Csharp Nullable Reference Types

    Aaronontheweb/dotnet-skills

    Guidelines for introducing and using nullable reference types (NRT) and System.Diagnostics.CodeAnalysis nullable attributes in C / .NET codebases.

    1.2k GitHub starsUsed in 1 repo~2.9k tokens
    Backend & APIsAuto-check passed
  • Official

    DO NOT USE when the target already consumes an injected interface or built-in abstraction such as IFileSystem or TimeProvider, even if the request says "generate a wrapper"; no new wrapper is needed.

    5.6k GitHub starsUsed in 1 repo~3.9k tokens
    Backend & APIsAuto-check passed
  • Cloud Kms

    Nethereum/Nethereum

    Sign Ethereum transactions with AWS KMS or Azure Key Vault HSMs using Nethereum.

    2.3k GitHub stars~738 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed

More from aws/aws-sdk-net

  • Official

    A skill your agent uses when validating that a C2J-to-Smithy migrated AWS SDK service builds, packages, and stays API-compatible with the shipping SDK, or before reporting such a migration as done…

    145 GitHub stars~4k tokensUpdated today
    Auto-check passed
  • AWS SDK Net Maintainer

    aws/aws-sdk-net

    Official

    A skill your agent uses when working on the AWS SDK for .NET source code itself, including Core runtime changes, service client implementations, generator or model changes, repo-specific build and…

    145 GitHub stars~503 tokensUpdated today
    Auto-check passed
  • Smithy Ast Model

    aws/aws-sdk-net

    Official

    The Smithy JSON AST facts and model invariants the SmithyDotNet generator relies on.

    145 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Type Mapping

    aws/aws-sdk-net

    Official

    Smithy shape to .NET type mapping, nullability, collection element rules, and error-shape naming/member rules.

    145 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Marshalling

    aws/aws-sdk-net

    Official

    What the SmithyDotNet generator must emit for request marshallers and response/error unmarshallers, per Smithy binding trait and protocol.

    145 GitHub stars~8.2k tokensUpdated today
    Auto-check passed

Categories

Questions about SDK Conventions

What does SDK Conventions do?

The public-API contract SmithyDotNet-generated code must match against the shipping AWS SDK for .NET - what must match vs. SDK Conventions is an agent skill from aws/aws-sdk-net, published by the product's own GitHub organization.NET - what must match vs.

When should I use SDK Conventions?

SDK Conventions fits situations like: tasks that involve API design.

How do I install SDK Conventions in Claude Code?

Run `npx skills add aws/aws-sdk-net --skill sdk-conventions -a claude-code`. Or copy the skill folder (generator/SmithyDotNet/skills/sdk-conventions in aws/aws-sdk-net) into .claude/skills/sdk-conventions in your project. Claude Code loads it when a task matches its description.

How do I install SDK Conventions in Codex?

Run `npx skills add aws/aws-sdk-net --skill sdk-conventions -a codex`. Or copy the skill folder (generator/SmithyDotNet/skills/sdk-conventions in aws/aws-sdk-net) into .agents/skills/sdk-conventions in your project. Codex loads it when a task matches its description.

Can I use SDK Conventions in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/aws-sdk-net --skill sdk-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sdk-conventions, .gemini/skills/sdk-conventions, .github/skills/sdk-conventions and .opencode/skills/sdk-conventions in your project.

What does SDK Conventions need to run?

SKILL.md names no scripts, command-line tools or credentials: SDK Conventions is instructions for the agent only.

Does SDK Conventions access the network?

SKILL.md names 1 domain. In commands or code: docs.aws.amazon.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is SDK Conventions safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does SDK Conventions use?

SDK Conventions is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SDK Conventions use?

About 6.3k tokens (SKILL.md is roughly 25k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to SDK Conventions?

Skills that share tags, products or a category with SDK Conventions: Foundatio (FoundatioFx/Foundatio, 2.1k stars), .NET API Compatibility Design (Aaronontheweb/dotnet-skills, 1.2k stars), .NET Aspire Explicit Configuration (Aaronontheweb/dotnet-skills, 1.2k stars) and Csharp Nullable Reference Types (Aaronontheweb/dotnet-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SDK Conventions?

aws (a GitHub organization, an official publisher) maintains it in aws/aws-sdk-net, which has 145 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.

Source: aws/aws-sdk-net on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.