Skip to content

docs: add adapter naming conventions reference#838

Draft
tphoney wants to merge 1 commit intomainfrom
cursor/adapter-naming-conventions-9a15
Draft

docs: add adapter naming conventions reference#838
tphoney wants to merge 1 commit intomainfrom
cursor/adapter-naming-conventions-9a15

Conversation

@tphoney
Copy link
Member

@tphoney tphoney commented Mar 17, 2026

What

Adds adapter-naming-conventions.md — a reference file that lists every adapter type string across all four sources (aws, azure, gcp, stdlib) and documents how similar concepts are named differently across providers.

Why

An agent selecting adapter types frequently picks the wrong name because the same concept is expressed differently per source. For example:

  • iam-role (aws) vs gcp-iam-role (gcp) vs azure-authorization-role-assignment (azure)
  • ec2-volume (aws) vs gcp-compute-disk / azure-compute-disk
  • gcp-compute-subnetwork (not gcp-compute-subnet)
  • gcp-cloud-kms-crypto-key (not gcp-kms-key)

The file is structured for agent consumption with:

  1. Format table — shows the naming scheme per source at a glance
  2. Cross-source concept tables — groups IAM, compute, networking, storage, databases, Kubernetes, functions, queues, KMS, secrets, DNS into tables that show all three provider equivalents side by side
  3. Common mistakes section — 15 explicit wrong→right corrections covering the most likely errors
  4. Complete adapter lists — every registered type string for all four sources, including the full GCP dynamic adapter set generated from item-types.go
Open in Web Open in Cursor 

Lists all exact adapter type strings across aws, azure, gcp, and stdlib
sources. Focuses on cross-source naming differences for similar concepts
(IAM roles, compute instances, disks, networking, KMS, etc.) and
includes a common-mistakes section to prevent wrong name selection.

Co-authored-by: TP Honey <thomas.honey@overmind.tech>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants