Keep project guides project-specific

This commit is contained in:
martin committed 2026-08-09 13:36:51 +02:00
1 parent 9a572f1789
commit d830a65f0c
3 files changed
+27 -15

No files matched your search

+23
View File
@@ -8,6 +8,29 @@ This repository provides reusable, client-neutral guidance for FileMaker AI work
- 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.
## Evidence priority
When sources conflict, use this order unless the project's `PROJECT.md` documents a stricter project-specific rule:
1. Confirmed current client decision in the ticket or project record
2. Verified current FileMaker behavior or current parsed DDR evidence
3. Other confirmed project documentation
4. An organization-specific shared standard explicitly selected by the project
5. This FileMaker Core guidance
Report meaningful conflicts instead of silently resolving them.
## Standard repository map
Use these locations for a workspace that follows the standard project layout. A project may document only deviations in `PROJECT.md`.
- `../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.
- `FMSCRIPTS/`: tracked complete `.fmscript` files that are not clearly ticket-specific or apply across several workstreams.
- `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-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
Read only the skill that matches the work; do not load every shared reference by default.
+3 -2
View File
@@ -5,7 +5,8 @@ Every client AI workspace owns its client context. Keep the project root small,
## Instruction layout
- Root `AGENTS.md`: a short, mandatory router. It tells an agent to read the local `PROJECT.md` and this Core `AGENTS.md` before work.
- `PROJECT.md`: client and project facts, local source priority, repository map, raw DDR location, and organization-specific standards.
- `PROJECT.md`: only client and project facts, organization-specific standards, and true project-specific exceptions.
- Core `AGENTS.md`: shared evidence priority, repository map, workflow, and response rules.
- Core skills: task-specific procedures read only when relevant.
Do not use a filesystem symlink for `PROJECT.md`; track it directly in the client repository.
@@ -17,7 +18,7 @@ Do not use a filesystem symlink for `PROJECT.md`; track it directly in the clien
- tickets, project notes, and approved analysis
- sanitized parsed DDR
- FileMaker work scripts and project-specific prompts
- the location and environment names of raw DDR exports
- project-specific raw DDR environments or any deviation from the standard repository map
## Standard workspace map
+1 -13
View File
@@ -5,22 +5,10 @@
- Client: <Client>
- Project: <Project>
## Local source priority
List the evidence order for this project. Confirmed client decisions and verified current FileMaker evidence should remain above shared guidance.
## Repository map
- Raw DDR: `../DDR/` (local only; never commit)
- Parsed DDR: `DDR-Parsed/`
- Tickets: `TICKETS/`
- Cross-ticket notes: `NOTES/`
- Cross-ticket FileMaker scripts: `FMSCRIPTS/`
## Additional shared standards
List any organization-specific shared repository and state exactly when its skills are required.
## Project-specific rules
Add only rules that do not apply to every FileMaker project.
Add only rules or repository-layout deviations that do not apply to every FileMaker project.