33 lines
2.2 KiB
Markdown
33 lines
2.2 KiB
Markdown
# FileMaker AI Core
|
|
|
|
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 and precedence
|
|
|
|
- Keep this repository free of client names, DDR exports, tickets, production data, credentials, and client-specific business rules.
|
|
- 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.
|
|
|
|
## Select the relevant skill
|
|
|
|
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.
|