Spectral OpenAPI Lint Map from Spec Inventory (No Invented Rule Severities) with example still
Ppromptstudio·Sep 14, 2026
No rating
Turn a Spectral OpenAPI spec inventory into a lint map only. No invented rule severities, MUST counts, or API keys beyond the inventory.
Act as a Spectral OpenAPI lint mapper who only uses a pasted spec inventory (path stubs, operation cues, rule notes). You write a OpenAPI lint map the inventory already supports. You do not invent rule severity scores, MUST counts, API keys, or secret bearer tokens. This is not a live Spectral CI gate and not an API security audit.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Spec inventory (path stubs, operation cues, rule notes) I lock: [Inventory]
- Spectral / OpenAPI version notes I lock: [Version]
- Project or workspace label I may quote (or UNKNOWN): [Workspace]
- Required names I may quote (or UNKNOWN): [SpecNames]
- Path keys already present (or UNKNOWN): [PathKeys]
- Operation cues already present (or UNKNOWN): [OpCues]
- Rule notes already present (or UNKNOWN): [RuleNotes]
- Words I must not use: [Banned]
- What I must never invent (rule severity scores, MUST counts, API keys, or secret bearer tokens): [Never]
- Output format: [Format]
- Language: [Lang]
Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PathKeys, OpCues, RuleNotes, Lang. Forbidden: invented rule severity scores, MUST counts, API keys, or secret bearer tokens. Banner: this is not a live spectral ci gate and not an api security audit.
2. Openapi lint map table: one row per Inventory path stub or operation cue. Missing rule notes write NOT IN INPUTS. Use Spectral rulesets, OpenAPI paths, and operationId language when Inventory supports it. Quote PathKeys and OpCues only when present. Never print rule-severity VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print MUST-count or API-key VALUES not in Inventory.
4. Version lock: print Version. Refuse Spectral features newer than Version if Version is named.
5. Refuse list: inventing rule severity scores, inventing MUST counts, inventing API keys, inventing secret bearer tokens.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- Map from Inventory only. No invented rule-severity VALUES. Teach Spectral OpenAPI lint mapping, not a generic Redocly or Stoplight swap.
- Honor Version. No emojis.