Plandex · API Governance Rules
Plandex API Rules
Spectral linting rules defining API design standards and conventions for Plandex.
9 Rules
error 2
warn 3
info 4
Rule Categories
plandex
Rules
warn
plandex-operation-summary-title-case
All operation summaries must use Title Case.
$.paths[*][*].summary
warn
plandex-operation-ids-camel-case
operationId must use camelCase.
$.paths[*][*].operationId
error
plandex-tags-required
Each operation must declare at least one tag drawn from the documented Plandex resource taxonomy.
$.paths[*][*]
error
plandex-bearer-auth-required
The Plandex server API uses bearer-token auth issued by the sign-in flow.
$.components.securitySchemes
warn
plandex-server-localhost-default
At least one server URL must point at the default local-mode host (http://localhost:8099) so docs reflect the self-hosted deployment.
$.servers[*].url
info
plandex-plan-id-path-param
Plan-scoped paths must use a {planId} path parameter named consistently.
$.paths[?(@property =~ /\/plans\//)]
info
plandex-branch-id-path-param
Branch-scoped paths must use a {branch} path parameter named consistently.
$.paths[?(@property =~ /\{branch\}/)]
info
plandex-resource-tag-allow-list
Operation tags should be drawn from the documented Plandex resource taxonomy.
$.paths[*][*].tags[*]
info
plandex-streaming-endpoint-naming
Streaming endpoints (tell, build, connect) should keep their canonical paths to remain compatible with the CLI/REPL.
$.paths