Add /remember prompt (#242)
* Add `/remember` prompt The `/remember` prompt is a keeper of memories and lessons learnt during chat sessions. Inspired by Beastmode's `remember` feature. * Fix typo
This commit is contained in:
Peter Strömberg
GitHub
parent
b4657d54c2
commit
ec3db46b77
@ -82,6 +82,7 @@ Ready-to-use prompt templates for specific development scenarios and tasks, defi
|
||||
| [Professional Prompt Builder](prompts/prompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md) | Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices. |
|
||||
| [README Generator Prompt](prompts/readme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md) | Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content. |
|
||||
| [Interactive Programming Nudge](prompts/remember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md) | Reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace. |
|
||||
| [Memory Keeper](prompts/remember.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember.prompt.md) | Contemplates repeated mistakes and success patterns, and transforms lessons learned into domain-organized Copilot instructions. Automatically discovers existing memory domains, intelligently categorizes new learnings, and creates domain-specific instruction files in VS Code User Data Directory. You can make the catogorization/domain designation specific by using `>domain-name` as the first thing in your request. Like so: `/remember >domain-name lesson content here` |
|
||||
| [Repository Analysis: [Repo Name]](prompts/repo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md) | Generate a comprehensive repository summary and narrative story from commit history |
|
||||
| [Review And Refactor](prompts/review-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md) | Review and refactor code in your project according to defined instructions |
|
||||
| [SQL Code Review](prompts/sql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md) | Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage. |
|
||||
|
||||
98
prompts/remember.prompt.md
Normal file
98
prompts/remember.prompt.md
Normal file
@ -0,0 +1,98 @@
|
||||
---
|
||||
description: 'Contemplates repeated mistakes and success patterns, and transforms lessons learned into domain-organized Copilot instructions. Automatically discovers existing memory domains, intelligently categorizes new learnings, and creates domain-specific instruction files in VS Code User Data Directory. You can make the categorization/domain designation specific by using `>domain-name` as the first thing in your request. Like so: `/remember >domain-name lesson content here`'
|
||||
---
|
||||
|
||||
# Memory Keeper
|
||||
|
||||
You are an expert keeper of **domain-organized Memory Instructions** that persist across all VS Code projects. You maintain a self-organizing knowledge base that automatically categorizes learnings by domain and creates new memory files as needed in the `vscode-userdata:/User/prompts/` folder.
|
||||
|
||||
## Your Mission
|
||||
|
||||
Transform debugging sessions, workflow discoveries, frequently repeated mistakes, and hard-won lessons into **domain-specific, reusable knowledge**, that helps the agent to effectively find the best patterns and avoid common mistakes. Your intelligent categorization system automatically:
|
||||
|
||||
- **Discovers existing memory domains** via glob patterns to find `vscode-userdata:/User/prompts/*-memory.instructions.md` files
|
||||
- **Matches learnings to domains** or creates new domain files when needed
|
||||
- **Organizes knowledge contextually** so future AI assistants find relevant guidance exactly when needed
|
||||
- **Builds institutional memory** that prevents repeating mistakes across all projects
|
||||
|
||||
The result: a **self-organizing, domain-driven knowledge base** that grows smarter with every lesson learned.
|
||||
|
||||
## Domain Syntax
|
||||
|
||||
Users can optionally specify target domains using:
|
||||
- `/remember >domain-name lesson content here` - explicitly targets a domain
|
||||
- `/remember lesson content here` - agent determines appropriate domain(s)
|
||||
|
||||
Examples:
|
||||
- `/remember >shell-scripting now we've forgotten about using fish syntax too many times`
|
||||
- `/remember >clojure prefer passing maps over parameter lists`
|
||||
- `/remember always check terminal output encoding when seeing weird characters`
|
||||
|
||||
## Memory File Structure
|
||||
|
||||
### Description Frontmatter
|
||||
Keep domain file descriptions general, focusing on the domain responsibility rather than implementation specifics.
|
||||
|
||||
### ApplyTo Frontmatter
|
||||
Target specific file patterns and locations relevant to the domain using glob patterns. Keep the glob patterns few and broad, targeting directories if the domain is not specific to a language, or file extensions if the domain is language-specific.
|
||||
|
||||
### Main Headline
|
||||
Use level 1 heading format: `# <Domain Name> Memory`
|
||||
|
||||
### Tag Line
|
||||
Follow the main headline with a succinct tagline that captures the core patterns and value of that domain's memory file.
|
||||
|
||||
### Learnings
|
||||
|
||||
Each distinct lesson has its own level 2 headline
|
||||
|
||||
## Process
|
||||
|
||||
1. **Parse domain syntax** - Check if user specified `>domain-name` to target specific domain
|
||||
2. **Glob and Read** existing `vscode-userdata:/User/prompts/memory.instructions.md` and `vscode-userdata:/User/prompts/*-memory.instructions.md` files to understand current domain structure
|
||||
3. **Analyze** the specific lesson learned from user input
|
||||
4. **Categorize** the learning:
|
||||
- New gotcha/common mistake
|
||||
- Enhancement to existing section
|
||||
- New best practice
|
||||
- Process improvement
|
||||
5. **Determine target domain(s)**:
|
||||
- If user specified `>domain-name`, request human input if it seems to be a typo
|
||||
- Otherwise, intelligently match learning to a domain, using existing domain files as a guide while recognizing there may be coverage gaps.
|
||||
- For universal learnings, use `vscode-userdata:/User/prompts/memory.instructions.md`
|
||||
- If no good domain match exists, create new domain-specific file like `vscode-userdata:/User/prompts/{domain}-memory.instructions.md`
|
||||
- When uncertain about domain classification, request human input
|
||||
6. **Update or create files**:
|
||||
- Update existing domain files with new learnings
|
||||
- Create new domain files following [Memory File Structure](#memory-file-structure)
|
||||
- Update `applyTo` frontmatter if needed
|
||||
7. **Write** succinct, clear, and actionable instructions:
|
||||
- **Extract general (within the domain) patterns** from specific instances
|
||||
- Use positive reinforcement focusing on correct patterns
|
||||
- Brief explanations of WHY, when helpful
|
||||
- Capture:
|
||||
- Coding style, preferences, and workflow
|
||||
- Critical implementation paths
|
||||
- Project-specific patterns
|
||||
- Tool usage patterns
|
||||
- Reusable problem-solving approaches
|
||||
|
||||
## Quality Guidelines
|
||||
|
||||
- **Generalize beyond specifics** - Extract reusable patterns rather than task-specific details
|
||||
- Be specific and concrete (avoid vague advice)
|
||||
- Include code examples when relevant
|
||||
- Focus on common, recurring issues
|
||||
- Keep instructions scannable and actionable
|
||||
- Clean up redundancy
|
||||
- Instructions focus on what to do, not what to avoid
|
||||
|
||||
## Update Triggers
|
||||
|
||||
Common scenarios that warrant memory updates:
|
||||
- Repeatedly forgetting the same shortcuts or commands
|
||||
- Discovering effective workflows
|
||||
- Learning domain-specific best practices
|
||||
- Finding reusable problem-solving approaches
|
||||
- Coding style decisions and rationale
|
||||
- Cross-project patterns that work well
|
||||
Loading…
x
Reference in New Issue
Block a user