lang-json

Format JSON content using Google JSON style and Prettier conventions.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-json
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lang-json
Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/lang-json
Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-json

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write and maintain JSON that stays readable, consistent, and compatible with downstream tooling, reducing formatting drift and style debates.

Core Features & Use Cases

  • Style Standardization: Applies the Google JSON style guide so JSON stays uniform across files and teams.
  • Automatic Formatting: Uses Prettier-friendly formatting to keep structure tidy and syntactically valid.
  • Workflow Guidance: Reminds you to load clean-code alongside this Skill for cleaner, more maintainable JSON conventions.

Quick Start

Ask the assistant to format the provided JSON according to the Google JSON style guide and Prettier while also applying clean-code guidance.

Frequently Asked Questions about lang-json

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

FAQPage Schema
How do I format JSON files to follow the Google style guide?

To format JSON according to the Google style guide, apply Prettier-compatible conventions to standardize indentation, syntax, and structure, ensuring your configuration files remain valid and consistently readable.

What is the best way to standardize JSON configuration files for team collaboration?

Standardizing JSON configuration files requires applying Google JSON style conventions and Prettier formatting to enforce uniform syntax, reducing formatting drift and style debates across teams and downstream tooling.

Does Prettier work with Google JSON style guide conventions?

Yes, Prettier works with Google JSON style conventions by generating Prettier-compatible output that standardizes structure and syntax, keeping JSON valid and maintainable for downstream tooling.

How do I keep JSON payloads clean and valid for downstream tooling?

To keep JSON payloads clean and valid for downstream tooling, apply automated Prettier formatting and clean-code guidance to standardize syntax, preventing formatting drift and ensuring tooling compatibility.

Why does my JSON formatting drift between different code editors?

JSON formatting drifts between editors when a unified style guide is absent. Enforcing Prettier-compatible output and Google JSON conventions across workflows standardizes formatting and prevents structural inconsistencies.