governing-operation-identifiers

What problem does it solve?

This Skill addresses the critical issue of inconsistent and poorly named identifiers within OpenAPI specifications, which directly leads to confusing and error-prone generated SDKs.

Core Features & Use Cases

• Enforce Naming Conventions: Ensures operationId, schema keys, and parameter names adhere to established best practices (e.g., camelCase, UpperCamelCase, snake_case).
• Promote Uniqueness: Guarantees that operationIds are unique across the entire specification to prevent compilation errors in generated code.
• Optimize for SDK Generation: Aligns identifier choices with common SDK generator expectations for idiomatic and readable code across various programming languages.
• Use Case: When reviewing a new OpenAPI specification, use this Skill to audit all operationIds for verb-noun consistency and uniqueness, and to verify that schema names like ProjectResponse follow UpperCamelCase.

Quick Start

Use the governing-operation-identifiers skill to audit the operationIds in the attached openapi.yaml file for camelCase verbNoun convention and uniqueness.