json-style

Format JSON documents according to Google's JSON Style Guide.

11|2|Updated Feb 18, 2026

Search Tags:#validation #json #google #naming-conventions #style-guide #data-models #apis

Ready to run

npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill json-style

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: json-style
Source: https://github.com/the-perfect-developer/the-perfect-opencode/tree/main/.opencode/skills/json-style
Command: npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill json-style

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This JSON style guide helps teams maintain consistent JSON across APIs by enforcing Google's JSON Style Guide rules for naming, quoting, and structure.

Core Features & Use Cases

Enforces property naming conventions (camelCase, proper quoting, and string values)
Guides data structure decisions for data objects, maps vs. objects, and pagination
Provides reference materials and examples to support API design and client integration

Quick Start

Paste a JSON document and receive a Google-style JSON output.

Frequently Asked Questions about json-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I format JSON consistently for API responses?▼

To format JSON consistently for API responses, apply Google's JSON Style Guide rules for property naming, quoting, and data structure. This enforces camelCase conventions, proper string values, and structured patterns to prevent formatting mistakes across API payloads.

What naming conventions should I use for JSON data models?▼

JSON data models should use camelCase naming conventions for property names, enforce proper quoting, and maintain string values. Following Google's JSON Style Guide ensures valid types and structured data patterns while avoiding comments and non-semantic constructs.

When do I use a map vs object in JSON API payloads?▼

In JSON API payloads, use maps for dynamic key-value pairs and objects for fixed properties with predictable names. Google's JSON Style Guide provides structural guidance on this distinction to ensure proper data modeling and prevent naming collisions in API responses.

Can I include comments in JSON payloads for API documentation?▼

No, you cannot include comments in JSON payloads. Google's JSON Style Guide explicitly avoids comments and non-semantic constructs to ensure valid types and proper quoting. JSON should contain structured data patterns only, without inline documentation or annotations.

What's the best way to validate JSON structure for APIs?▼

The best way to validate JSON structure for APIs is to apply Google's JSON Style Guide rules, which enforce valid types, proper quoting, and structured data patterns. This prevents naming and formatting mistakes while ensuring consistent property conventions across API payloads.

Why does my JSON formatting break API client integration?▼

JSON formatting breaks API client integration when it violates naming conventions or uses inconsistent quoting and structure. Applying Google's JSON Style Guide ensures camelCase properties, proper string values, and valid types to maintain reliable API data models and responses.