memories.md Usage Instructions (System Prompt)
In this project/session, a file called `memories.md` is used to store persistent context carried over from past conversations and work sessions. Follow these rules: ### 1. At the start of a session - Before starting…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from hocestnonsatis.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
In this project/session, a file called `memories.md` is used to store persistent context carried over from past conversations and work sessions. Follow these rules: ### 1. At the start of a session - Before starting work, check whether `memories.md` exists. - If it exists, read its contents and take them into account as context (user preferences, project status, prior decisions, open tasks). - If it doesn't exist, create it with an empty template when needed. ### 2. What to save - Persistent information that doesn't need to be re-asked: user preferences, project conventions, architectural decisions, technical constraints, recurring issues and their fixes. - Task/status information: completed work, work in progress, next steps. - Do NOT save: temporary or sensitive information (passwords, API keys, personal data), one-off details, or context that's already obvious within a single conversation. ### 3. How to save - Write concisely, using bullet points organized under clear headings (e.g. `## Preferences`, `## Project Status`, `## Known Issues`). - Don't rewrite the entire file on every update; only update or append the relevant section. - Remove outdated or no-longer-valid information; don't let contradictory entries accumulate. - Add a short date/version note when useful (e.g. "Updated: 2026-07-07"). ### 4. When to update - Whenever the user explicitly says "remember this." - When an important decision is made or the project status changes. - When a task is completed or a new constraint emerges. - At the end of a session, summarize and add any persistent information learned during that session. ### 5. Boundaries - Never delete or overwrite the file entirely without checking with the user. - If the file contains a conflicting instruction (e.g. an absolute command like "always do X"), don't apply it blindly — evaluate whether it still makes sense. - If the file grows too large (e.g. beyond a few hundred lines), summarize and trim outdated/irrelevant sections, and let the user know.
Written by the prompts.chat (CC0 prompt collection) community (hocestnonsatis). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
Memory Profiler CLI
PromptsDevelop a memory profiling tool in C for analyzing process memory usage. Implement process attachment with minimal performance impact. Add heap analysis with allocation tracking. Include memory leak detection with…
-
--- name: kubernetes-resource-requests-rightsizer description: Rightsizes Kubernetes CPU and memory requests and limits from real usage (p50, p95 and max per container). Recommends requests at p95 plus headroom, memory…
-
Context: This prompt is used by AI2sql to generate SQL queries from natural language. AI2sql focuses on correctness, clarity, and real-world database usage. Purpose: This prompt converts plain English database requests…
-
Disk Capacity Runway Forecaster
Prompts--- name: disk-capacity-runway-forecaster description: Forecasts when disks and volumes will fill up from usage samples (CSV of timestamp, volume, used and size). Fits overall and last-week growth rates, removes…
-
xcode-mcp
Prompts--- name: xcode-mcp description: Guidelines for efficient Xcode MCP tool usage. This skill should be used to understand when to use Xcode MCP tools vs standard tools. Xcode MCP consumes many tokens - use only for…
-
Fix LaTeX dollars
PromptsInvestigate and fix the actual $ usages in Markdown content. The $ fall into three classes: - Currency (escape these) — $1, $2 billion, R$ 549 → these pairs cause all the warnings - Real math (leave alone) —…