Claude-skill-registry frago-view-content-generate-tips-json
JSON file content generation guide. Use this skill when you need to create JSON files that can be previewed via `frago view`. Covers formatted display and best practices.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/frago-view-content-generate-tips-json" ~/.claude/skills/majiayu000-claude-skill-registry-frago-view-content-generate-tips-json && rm -rf "$T"
manifest:
skills/data/frago-view-content-generate-tips-json/SKILL.mdsource content
JSON File Content Generation Guide
Preview JSON files via
frago view with automatic formatting and syntax highlighting.
Preview Commands
frago view data.json # Default theme frago view config.json --theme monokai # Specify theme
Rendering Features
Automatic Formatting
- JSON content automatically beautified (Pretty Print)
- Indentation aligned
- Key-value pairs clearly displayed
Syntax Highlighting
| Element | Color Example (github-dark) |
|---|---|
| Key names | Purple |
| String values | Blue |
| Numbers | Cyan |
| Booleans | Red |
| null | Red |
| Brackets/commas | White |
JSON Format Specification
Correct Format
{ "name": "Project Name", "version": "1.0.0", "enabled": true, "count": 42, "tags": ["tag1", "tag2"], "config": { "nested": "value" }, "nullable": null }
Common Errors
| Error | Example | Fix |
|---|---|---|
| Trailing comma | | |
| Single quotes | | |
| Unquoted keys | | |
| Comments | | Comments not supported |
| undefined | | Use |
Best Practices
1. Indentation
- Use 2 or 4 spaces for indentation
- Maintain consistency
2. Key Naming
- Use snake_case or camelCase
- Maintain consistency throughout the file
{ "user_name": "snake_case style", "userName": "camelCase style" }
3. Data Organization
- Group related fields
- Place important fields first
{ "id": "001", "name": "Important fields first", "metadata": { "created_at": "2024-01-01", "updated_at": "2024-01-02" } }
4. File Size
- Single file < 1MB optimal
- Consider pagination or splitting files for large data
Use Cases
- API response data preview
- Configuration file viewing
- Data structure review
- Debug data inspection
Display Themes
Same as code files, supports the following themes:
| Theme | Command |
|---|---|
| github-dark (default) | |
| monokai | |
| atom-one-dark | |
Notes
| Issue | Cause | Solution |
|---|---|---|
| Parse failure | JSON format error | Use JSON validator |
| Truncated display | Value too long | Use nested structure |
| Slow rendering | File too large | Split or simplify |
JSON Validation
Ensure JSON is valid before preview:
# Python validation python -m json.tool data.json # jq validation jq . data.json
Related Tools
- jq: Command-line JSON processor
- jsonlint: JSON validator
- VSCode: JSON editing and formatting