35 lines
1.8 KiB
Markdown
35 lines
1.8 KiB
Markdown
# 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.
|
|
|
|
## Scope
|
|
|
|
- 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.
|
|
- 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
|
|
|
|
- `skills/ddr-analysis/`: analyze FileMaker DDR safely and evidence-first.
|
|
- `skills/filemaker-scripting/`: prepare or review FileMaker script work.
|
|
- `skills/ticket-analysis/`: turn a request into confirmed scope, questions, risks, and tests.
|