Centralize reusable FileMaker workspace guidance

AGENTS.md

@@ -1,34 +1,32 @@
 # FileMaker AI Core
 
-This repository contains reusable, client-neutral guidance for FileMaker AI work. It is designed to be consumed by client workspaces as a pinned Git submodule.
+This repository provides reusable, client-neutral guidance for FileMaker AI work. It is normally consumed as a pinned Git submodule by a client workspace.
 
-## Scope
+## Scope and precedence
 
 - Keep this repository free of client names, DDR exports, tickets, production data, credentials, and client-specific business rules.
-- Put project facts, confirmed decisions, raw DDR locations, and client communication requirements in the consuming project repository.
-- Treat this repository as a baseline, not as permission to overwrite legacy project conventions.
-
-## Project Integration
-
-The consuming project's root `AGENTS.md` must direct agents here explicitly and identify the relevant skill. A project normally gives this repository lower priority than:
-
-1. Confirmed client decisions and current ticket requirements
-2. The project's own `AGENTS.md`, notes, and documented conventions
-3. Verified current DDR or direct FileMaker inspection
-4. This core guidance
-5. General FileMaker practice
-
-## Core Rules
-
-- Separate confirmed behavior from assumptions and open questions.
-- Do not invent business rules, schema details, permissions, or implementation status.
+- Read the consuming project's `PROJECT.md` before applying this guidance. Its confirmed client decisions, documented conventions, and verified current FileMaker evidence take priority over this core.
 - Preserve established legacy patterns unless a confirmed requirement deliberately changes them.
-- Treat parsed DDR as generated reference data; do not edit it manually.
-- Before sharing parsed DDR, run the project's secret-redaction and review process.
-- Keep reusable instructions concise and split them into relevant skills instead of growing this file indefinitely.
 
-## Available Skills
+## Select the relevant skill
 
-- `skills/ddr-analysis/`: analyze FileMaker DDR safely and evidence-first.
-- `skills/filemaker-fmscript/`: create, edit, review, or validate `.fmscript` work using the preserved step catalog and references.
-- `skills/ticket-analysis/`: turn a request into confirmed scope, questions, risks, and tests.
+Read only the skill that matches the work; do not load every shared reference by default.
+
+- 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 `.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`
+
+## 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.
+- 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.
+
+## 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.