Configure project standards

ADT's globally installed baseline standards apply to every project. They cover FileMaker naming and common structural patterns so a coding agent does not invent conventions during each task.

Check the active standards

Ask the coding agent before a FileMaker authoring or review task:

Tell me which FileMaker standards are active for this project and where each rule file comes from.

The agent resolves the global baseline, any installed standards plugin declared in adt.json, and any project-specific exceptions.

Create shared standards

Create a standards plugin when the same conventions should apply to several projects. The plugin contains your naming rules, structural patterns, optional review guidance, and any checks ADT can enforce before writing.

Ask the coding agent to create the plugin and describe only the rules that differ from the ADT baseline. Install the finished plugin in the coding agents that work on those projects, then declare its permanent identifier in adt.json.

See FileMaker standards plugins for the plugin structure and manifest entry.

Add project-specific exceptions

Keep rules that apply to only one solution under .adt/standards/ in that project. A project file takes precedence over the corresponding file from the selected standards plugin and the global baseline.

Commit these files with the project so every coding agent receives the same exceptions. Installing or changing standards does not rename or reorganize existing FileMaker objects automatically.

Missing standards plugin

If adt.json declares a plugin that is not installed, the agent reports the missing plugin and continues with the global baseline plus any project-specific exceptions. It must not guess what the missing plugin would have required.