Spells Json Authoring

Workflow

1. Locate spell list:

• Open public/data/spells.json.
• Find @graph node with @id: "sa:spellList".
• Operate only inside sa:items unless user asked for metadata/context changes.

2. Determine task type:

• Refactor-only (default): change representation only, preserve meaning.
• Definition change (opt-in): alter effects, range, duration, targeting, or other spell behavior only if user explicitly asks.

3. Apply safe refactors:

• Keep JSON valid and structurally consistent.
• Keep key names exactly as currently used by the app.
• Normalize missing required keys by adding placeholders with correct types.
• Prefer preserving existing wording, punctuation, and capitalization unless fixing obvious typos requested by user.
• Preserve @id unless user explicitly requests an identifier migration.

4. Guard against semantic drift:

• Do not change mechanical meaning (damage, area, duration, range, targeting, conditions, action economy) in refactor-only mode.
• If a requested formatting change could alter meaning, stop and ask for confirmation.

5. Validate before finishing:

• Confirm file parses as JSON.
• Confirm each touched spell still has all required keys and expected primitive types.
• Confirm no unintended key renames (for example, spell:castingtime must not become spell:castingTime).

Decision Rules

• If instruction is ambiguous between cleanup and mechanical change, treat it as cleanup only and ask a clarifying question.
• If data is incomplete, fill schema-required fields with type-safe placeholders, then flag the entry for follow-up.
• If duplicate or inconsistent IDs are found, report them and request migration approval before changing IDs.

Output Expectations

• Provide the exact JSON edits made.
• Call out whether changes were representation-only or included explicit definition changes.
• List any fields still incomplete after refactor.

Completion Checklist

• JSON remains valid.
• Touched spells conform to implicit schema.
• Intent unchanged unless explicitly instructed.
• Changes are limited to requested scope.