How should we treat AI context files?

[wpotrzebowski]

Context

A Cursor rules file (.cursor/rules/sasview.mdc) was used during SASBDB work, then removed from the PR #3912 so it wouldn’t ship with that change. It’s useful locally; the question is whether SasView should adopt something like this project-wide.

What is it for?

Not runtime code or user docs — a short rulebook for AI-assisted editing. It orients agents on repo layout, install/run expectations, coding/GUI conventions, scientific caution, and where tests live, so they follow SasView practice instead of generic defaults.

Cursor uses .cursor/rules/*.mdc; other tools use different paths for the same idea (Copilot instructions, AGENTS.md, etc.).

Options

1. Local only — ignore .cursor/ (and similar); each contributor keeps private rules
2. One tool-neutral file — e.g. AGENTS.md or a wiki/dev doc; ignore vendor dirs
3. Vendor-specific checked in — Cursor/Copilot/etc. files for tools we support
4. Hybrid — tracked neutral core; optional ignored/thin adapters per IDE

Maintenance (if we check anything in)

• Own it like DeveloperNotes; update when install/test/architecture reality changes
• Point at wiki / INSTALL.md / existing docs — don’t fork a second policy
• Keep it short; review via PR; no personal prefs or secrets

Questions

1. Check AI guidance into the repo, or keep it local?
2. If yes: tool-neutral, vendor-specific, or hybrid?
3. How to maintain it?

[wpotrzebowski]

Example of Cursor's sasview.mdc