added ddr script skills

AGENTS.md

@@ -28,7 +28,7 @@ Use these locations for a workspace that follows the standard project layout. A
 - `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.
 - `NOTES/`: confirmed knowledge and business rules that apply across more than one ticket.
-- `DDR-Parsed/`: tracked generated FileMaker reference material. Do not edit it manually.
+- `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.
 
 ## Select the relevant skill
@@ -37,6 +37,7 @@ 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
 - 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`
@@ -53,7 +54,7 @@ Read only the skill that matches the work; do not load every shared reference by
 ## Core rules
 
 - Do not invent business rules, schema details, permissions, or implementation status. Separate confirmed behavior, verified current behavior, proposals, and open questions.
-- Use parsed DDR as generated reference data. Do not edit it manually; defer to direct FileMaker verification when the two conflict.
+- Use parsed DDR as generated reference data and defer to direct FileMaker verification when the two conflict. The only standard manual-edit exception is an authorized DDRparser-format script change under `DDR-Parsed/<solution>/Scripts/`; paste it into FileMaker and regenerate the DDR before calling it implemented.
 - Keep work practical and minimal. Review affected data, permissions, workflows, layouts, reporting, integrations, and regression risk where relevant.
 - Do not make production changes, send client messages, or modify project files unless explicitly asked.
 - Do not expose credentials or other sensitive values found in source material.
@@ -77,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 and use valid `.fmscript` format.
+- 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`.