agentleFS
Sign inStart free
ozgurkarahanozgurkarahan/salesforce-meta-tool-identity-propagation/.github/copilot-instructions.md

salesforce-meta-tool-identity-propagation

Copilot instructions4 starsChanged 9 months agoMITView on GitHub

Read these files for full context: When the user says "end session", "wrap up", or "done for today": A compounding cross-project knowledge base lives at ~/projects/memory (%USERPROFILE%\projects\memory on Windows; resolve ~ to your home dir). Consult it reflexively before answering about clients, domains, patterns, tools, colleagues, or past work — do not answer from memory when the wiki has the answer. - Read the top matching page(s) in full before you answer. - Compact catalog / router: ~/projects/memory/index.md (per-category summaries…

The file

We split this copilot-instructions.md into the rules it gives an agent

11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read these files for full context:

    line 3
  2. Distinctive:

    When the user says "end session", "wrap up", or "done for today":

    line 14
  3. Very specific:

    Update the project's wiki page at the registered project's wiki_ref, resolved through Memory's scripts/wiki_paths.py

    line 18
  4. Very specific:

    Update relevant domain pages at Memory's resolved domains catalog (via category_index_path)

    line 19
  5. Very specific:

    Add new glossary terms to ~/projects/memory/glossary.md

    line 20
  6. Very specific:

    Use @workspace to give Copilot full project context

    line 27
  7. Distinctive:

    Use Copilot Edits (Ctrl+Shift+I) for multi-file changes

    line 29
  8. Distinctive:

    Run tests manually — Copilot cannot execute them

    line 30
  9. Very specific:

    When corrected, record the lesson in the wiki project page (wiki:projects/salesforce-meta-tool-id-prop (resolve through Memory's …

    line 31
  10. Distinctive:

    Read the top matching page(s) in full before you answer.

    line 47
  11. Very specific:

    When you learn something durable about this project or client, ask the user to run ingest in the memory repo so it compounds for future …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Copilot Instructions

Read these files for full context:

  • AGENT.md — Project overview, architecture, key paths, workflow rules, and conventions
  • wiki:projects/salesforce-meta-tool-id-prop (resolve through Memory's scripts/wiki_paths.py) — Past mistakes / lessons (wiki = single source of truth; .ai/lessons-learned.md was REMOVED)
  • .ai/project-reference.md — Technical details
  • ~/projects/memory/agent-config/workflow.md — Global workflow rules
  • ~/projects/memory/agent-config/platform.md — Platform preferences and domain knowledge index

End-Session Workflow

When the user says "end session", "wrap up", or "done for today":

  1. Project docs — Check if the wiki project page (wiki:projects/salesforce-meta-tool-id-prop (resolve through Memory's scripts/wiki_paths.py)) and .ai/project-reference.md need updates from today's work. Propose changes.
  2. Wiki compounding — If significant lessons or patterns were discovered:
    • Update the project's wiki page at the registered project's wiki_ref, resolved through Memory's scripts/wiki_paths.py
    • Update relevant domain pages at Memory's resolved domains catalog (via category_index_path)
    • Add new glossary terms to ~/projects/memory/glossary.md
    • Append to ~/projects/memory/log.md
  3. Git check — Run git status and warn about uncommitted changes.
  4. Summary — Report what was updated.

Copilot-Specific Tips

  • Use @workspace to give Copilot full project context
  • Pin important files in chat for persistent context
  • Use Copilot Edits (Ctrl+Shift+I) for multi-file changes
  • Run tests manually — Copilot cannot execute them
  • When corrected, record the lesson in the wiki project page (wiki:projects/salesforce-meta-tool-id-prop (resolve through Memory's scripts/wiki_paths.py))

Shared knowledge base (memory wiki)

A compounding cross-project knowledge base lives at ~/projects/memory (%USERPROFILE%\projects\memory on Windows; resolve ~ to your home dir). Consult it reflexively before answering about clients, domains, patterns, tools, colleagues, or past work — do not answer from memory when the wiki has the answer.

# from ANY repo — resolves the wiki root from the script's own location
python ~/projects/memory/scripts/wiki-search.py <terms>          # ranked hits
python ~/projects/memory/scripts/wiki-search.py <terms> --full   # + Summary
  • Read the top matching page(s) in full before you answer.
  • Compact catalog / router: ~/projects/memory/index.md (per-category summaries in the category catalog resolved by Memory's category_index_path).
  • When you learn something durable about this project or client, ask the user to run ingest in the memory repo so it compounds for future sessions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free