Files
detections/.cursor/rules/openapi.mdc
T
Oleksandr Bezdieniezhnykh d28b9584f2 Generalize tracker references, restructure refactor skill, and strengthen coding rules
- Replace all Jira-specific references with generic tracker/work-item
  terminology (TRACKER-ID, work item epics); delete project-management.mdc
  and mcp.json.example
- Restructure refactor skill: extract 8 phases (00–07) and templates into
  separate files; add guided mode for pre-built change lists
- Add Step 3 "Code Testability Revision" to existing-code workflow
  (renumber steps 3–12 → 3–13)
- Simplify autopilot state file to minimal current-step pointer
- Strengthen coding rules: AAA test comments per language, test failures as
  blocking gates, dependency install policy
- Add Docker Suitability Assessment to test-spec and test-run skills
  (local vs Docker execution)
- Narrow human-attention sound rule to human-input-needed only
- Add AskQuestion fallback to plain text across skills
- Rename FINAL_implementation_report to implementation_report_*
- Simplify cursor-meta (remove _docs numbering table, quality thresholds)
- Make techstackrule alwaysApply, add alwaysApply:false to openapi
2026-03-28 02:42:36 +02:00

16 lines
616 B
Plaintext

---
description: "OpenAPI/Swagger API documentation standards — applied when editing API spec files"
globs: ["**/openapi*", "**/swagger*"]
alwaysApply: false
---
# OpenAPI
- Use OpenAPI 3.0+ specification
- Define reusable schemas in `components/schemas`; reference with `$ref`
- Include `description` for every endpoint, parameter, and schema property
- Define `responses` for at least 200, 400, 401, 404, 500
- Use `tags` to group endpoints by domain
- Include `examples` for request/response bodies
- Version the API in the path (`/api/v1/`) or via header
- Use `operationId` for code generation compatibility