Instabug (Luciq) · API Governance Rules
Instabug (Luciq) API Rules
Spectral linting rules defining API design standards and conventions for Instabug (Luciq).
9 Rules
error 5
warn 4
Rule Categories
luciq
Rules
error
luciq-server-url-required
Every Luciq OpenAPI document must declare at least one server URL under the api.luciq.ai apex.
$.servers
error
luciq-operation-tagged
Every operation must have at least one tag aligned with the Luciq surface taxonomy.
$.paths[*][get,post,put,patch,delete].tags
error
luciq-tags-title-case
Top-level tags must use Title Case (e.g., "Crashes", "App Hangs", "Bugs").
$.tags[*].name
warn
luciq-summary-title-case
Operation summaries must be Title Case (e.g., "List Crashes", "Get Bug Details").
$.paths[*][get,post,put,patch,delete].summary
error
luciq-operation-id-camel
operationId must be camelCase (e.g., listCrashes, getOccurrenceDetails).
$.paths[*][get,post,put,patch,delete].operationId
error
luciq-security-required
Root-level security must declare at least one scheme (OAuth or PAT bearer).
$.security
warn
luciq-mcp-auth-schemes
The Luciq MCP Server OpenAPI must define both oauth2 and personalAccessToken security schemes.
$.components.securitySchemes
warn
luciq-401-defined
Every operation must define a 401 response so clients can handle auth failures uniformly.
$.paths[*][get,post,put,patch,delete].responses
warn
luciq-path-kebab-case
URL path segments must be lowercase, hyphen-separated (e.g., /app-hangs, /occurrence-tokens).
$.paths