Search
Glossary3
Open the full glossary- JSON (JavaScript Object Notation)A lightweight data format in plain text that both humans and programs can read — the common language of AI tooling.
- YAMLThe other common config format: nesting expressed by indentation, closer to a human outline than JSON — and far pickier about whitespace.
- Structured outputAsking the model to return data that conforms to a format you specify (usually a JSON schema) instead of free prose, so downstream code can parse it directly without guessing.
Found 6 articles
Config Files, Dotfiles, and Package Managers: What Are Those Files Starting with a Dot?
Why every tool asks you to edit a file starting with a dot, the difference between YAML and JSON, why wrong indentation breaks everything, what problems package managers like brew and apt solve, and how much regex you actually need to know.
Function Calling 101: Getting an LLM to Actually Use Tools
A clear account of the Function Calling mechanism in mainstream LLM APIs: how to write a tool JSON Schema, how the model decides whether to call a tool, how to use tool_choice for forced calls and parallel calls — with a complete runnable example, plus practical techniques for how the way you write tool descriptions decides call quality.
How Machines Read Financials: From PDF to Structured Data
The first bottleneck of automating financial-statement analysis is that machines cannot read the PDF. This article breaks down the three paths — text-layer extraction, OCR, and layout analysis — explains why financial tables are especially hard to read and why human proofreading is mandatory after OCR, and gives the design concepts of structured output (JSON schema).
300-Page Annual Report to Structured JSON: The Three Statements and Segment Data
Building on the PaddleOCR field practice, this pushes 'reading out the text' to 'usable data': locating the financial-statement pages, handling cross-page tables, field mapping and unit normalization for the three statements and segment information, JSON schema design, and a complete pipeline and checklist for automated proofreading via reconciliation relationships.
A Multi-Agent Investment-Research Pipeline: Collect, Analyze, Report in Three Stages
A single Agent cannot finish an investment-research task: the context blows up, attention scatters, and errors cross-contaminate. This article gives the complete design for a three-stage collect / analyze / report division of labor — each stage's responsibilities and negative list, the structured JSON contract between stages, the write-scope partition, failure isolation and contamination detection, where to place the verification gates, and the cost-and-latency trade-off framework, with an architecture diagram and a failure-mode list.
Open Design Hatch Pet Skill Guide
Create Codex compatible animated sprite pets from character design drafts, screenshots, and generated images: 8×9 atlas, transparent unused cells, per-row animation prompts, QA contact sheet, preview video, and pet.json packaging.