Document Require Name
document-require-name
info
experience: data-modelingexperience: governance
spec: document
name should be present
The name property should be present.
Rule definition
The full Spotlight rule — drop it into a ruleset (.spotlight.yaml / .spectral.yaml) and run it with any Spotlight tool.
document-require-name:
title: Document Require Name
reference: https://spotlight-rules.com/spec/rules/plans/document-require-name/
description: The `name` property should be present.
message: name should be present
severity: info
given: $
then:
field: name
function: truthy
tags:
- format:plans
- spec:document
- experience:data-modeling
- experience:governance
prompt: "You are editing a Plans document to satisfy the Spotlight API
governance rule 'document-require-name' (Document Require Name).
Requirement: The `name` property should be present. To fix: Ensure `name` is
present and non-empty at each matching location. Make the smallest change
that satisfies the rule, leave all unrelated content, key order, comments,
and formatting unchanged, and keep the document valid Plans. Return only the
complete corrected document, with no commentary."
AI fix prompt — send this to Claude, Gemini, or ChatGPT with your artifact to auto-fix this rule
You are editing a Plans document to satisfy the Spotlight API governance rule 'document-require-name' (Document Require Name). Requirement: The `name` property should be present. To fix: Ensure `name` is present and non-empty at each matching location. Make the smallest change that satisfies the rule, leave all unrelated content, key order, comments, and formatting unchanged, and keep the document valid Plans. Return only the complete corrected document, with no commentary.
| Artifact | Plans |
|---|---|
| Applies at (given) | $ |
| Severity | info — educational by default; raise to warn/error to enforce |
| Reference | https://spotlight-rules.com/spec/rules/plans/document-require-name/ |