Skill Instructions

This skill treats JSON as executable configuration.

Inputs / Outputs / Non-goals

• •Inputs: JSON schemas, affected feature specs, validation commands.
• •Outputs: schema-safe JSON edits, impact notes, suggested validations.
• •Non-goals: schema-breaking changes without explicit approval.

What this skill helps accomplish

• •Maintain consistent data contracts
• •Prevent silent breakage across modules
• •Improve predictability of AI-generated data changes

When to use this skill

• •Editing judoka.json or battle state files
• •Adding new metadata or configuration
• •Modifying tooltips or content files

Common files

• •src/data/judoka.json
• •src/data/tooltips.json
• •src/config/settingsDefaults.js

Rules for JSON changes

1. •Schema stability first
2. •Additive changes preferred
3. •Explicit defaults for new fields
4. •Identify impacted consumers

Validation

• •Prefer npm run validate:data after JSON edits.

Required behaviour

• •Explain why a change is safe
• •Call out any required code updates
• •Suggest validation or tests if needed

Expected output

• •Well-structured JSON
• •Clear explanation of changes
• •Impact analysis