From 48a12a78e009a03dee6b98774f46a3fafaf7018c Mon Sep 17 00:00:00 2001 From: Martin Galik Date: Tue, 15 Sep 2026 16:39:44 +0200 Subject: [PATCH] Default to DDRparser script format --- AGENTS.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 2adaacd..85903d2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -26,7 +26,7 @@ Use these locations for a workspace that follows the standard project layout. A - `../DDR/`: local raw FileMaker DDR input. Never copy it into the repository or commit it; move it only as part of an explicitly approved filesystem migration. - `TICKETS/`: one folder per ticket or workstream. Keep its source requests, handoffs, analysis, questions, reports, assets, and ticket-specific scripts together. Use a `scripts/` subfolder when it helps navigation. -- `FMSCRIPTS/`: tracked complete `.fmscript` files that are not clearly ticket-specific or apply across several workstreams; keep one `.fmscript` file per FileMaker script. +- `FMSCRIPTS/`: legacy location for tracked `.fmscript` files. Use it only when the user explicitly requests `.fmscript` or ai2fm. - `NOTES/`: confirmed knowledge and business rules that apply across more than one ticket. - `DDR-Parsed/`: tracked FileMaker reference material generated by DDRparser. Do not manually edit generated definitions outside `Scripts/`. When a project uses the DDRparser copy-and-paste workflow, edit the affected `Scripts/*.txt` file in place for Git review, paste it into FileMaker, regenerate the DDR, and verify the round trip. - `ddr-parse.sh`: run `zsh ddr-parse.sh` from the project root to parse the latest DDR into `DDR-Parsed/` when an up-to-date reference is needed. @@ -37,8 +37,8 @@ Read only the skill that matches the work; do not load every shared reference by - Ticket, request, email, or handoff: `skills/ticket-analysis/SKILL.md` - Current implementation, schema, script, calculation, layout, relationship, security, reporting, or integration analysis: `skills/ddr-analysis/SKILL.md` -- Any DDRparser-format script generation, edit, review, syntax question, or copy-and-paste preparation: `skills/filemaker-ddr-script/SKILL.md` -- Any `.fmscript` generation, edit, review, or syntax question: `skills/filemaker-fmscript/SKILL.md` and the examples it selects +- Any FileMaker script discussion, generation, edit, review, syntax question, or copy-and-paste preparation: use DDRparser text format by default and read `skills/filemaker-ddr-script/SKILL.md`. +- Use `skills/filemaker-fmscript/SKILL.md` and the examples it selects only when the user explicitly asks for `.fmscript`, ai2fm, or that legacy format. - New or changed FileMaker object, field, variable, parameter, or result names: `skills/filemaker-naming/SKILL.md` - Project-manager reply or short billable work report: `skills/ticket-delivery/SKILL.md` @@ -78,4 +78,4 @@ Read only the skill that matches the work; do not load every shared reference by ## Response format - Do not hard-wrap Markdown prose. Use line breaks only where Markdown structure or meaning requires them. -- Present every FileMaker script snippet, including partial sections, in a fenced `text` block. Use DDRparser text format when the request or project uses `filemaker-ddr-script`; use `.fmscript` format only when the request or project selects `filemaker-fmscript`. +- Present every FileMaker script snippet, including partial sections, in a fenced `text` block and use DDRparser text format by default. Use `.fmscript` only when the user explicitly requests `.fmscript`, ai2fm, or that legacy format.