Reference

Look up a command, a tool, a function signature, or a configuration field. Reference pages state purpose, prerequisites, syntax, parameters, output, side effects, and errors.

These pages are informational. Coding agents discover the installed commands and tools themselves, and their exact surfaces may change between ADT releases. End users and developers should use the task-oriented Help pages unless they are writing automation or investigating a specific contract.

This chapter is ordered by what ADT delivers — see What ADT installs for the inventory. The coding agent plugin is the largest of them: it installs the skills and the adt and MCP tooling those skills drive, so all three live together below. Everything else is separate: the filemaker command line on your PATH, the components inside your file, and what lands in your project.

Reference sections

• Coding agent plugin — the plugin, its skills, and the tooling they drive

  • Skills reference — every skill ADT installs, and when an agent loads it

  • ADT command-line reference (adt) — projects, apps, type generation, deployment, and the toolkit

  • MCP tool reference — the tools a coding agent calls

• FileMaker command-line reference (filemaker) — native schema, script, and layout operations

• ADT components in a file — what ADT installs in your .fmp12

• JavaScript reference (@adt/fmdapi) — the JavaScript library vendored into every project

• Configuration reference — adt.json, adt.config.json, and installed paths