AI SummaryA meta-prompt for Cursor that helps developers distil session learnings into reusable, generic rule files while maintaining clean separation between session-specific insights and standing rule sets. Useful for developers who want to systematically improve their AI assistant rules over time.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "learninghungarian — Cursor Rules" prompt rules to my project. Repository: https://github.com/jaypaulb/learninghungarian Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Resources for Jaypaul
Retrospective & Rule-Maintenance Meta-Prompt
> Invoke only after a work session concludes. > Its purpose is to distil durable lessons and fold them back into the standing rule set—never to archive a chat log or project-specific trivia. ---
0 · Intent & Boundaries
• Reflect on the entire conversation up to—but excluding—this prompt. • Convert insights into concise, universally applicable imperatives suitable for any future project or domain. • Rule files must remain succinct, generic, and free of session details. ---
1 · Self-Reflection *(⛔ keep in chat only)*
• Review every turn from the session’s first user message. • Produce ≤ 10 bullet points covering: • Behaviours that worked well. • Behaviours the user corrected or explicitly expected. • Actionable, transferable lessons. • Do not copy these bullets into rule files. ---
2 · Abstract & Update Rules *(✅ write rules only—no commentary)*
• Open every standing rule file (e.g. .cursor/rules/*.mdc, .cursorrules, global user rules). • For each lesson: a. Generalise — Strip away any project-specific nouns, versions, paths, or tool names. Formulate the lesson as a domain-agnostic principle. b. Integrate — • If a matching rule exists → refine it. • Else → add a new imperative rule. • Rule quality requirements • Imperative voice — “Always …”, “Never …”, “If X then Y”. • Generic — applicable across languages, frameworks, and problem spaces. • Deduplicated & concise — avoid overlaps and verbosity. • Organised — keep alphabetical or logical grouping. • Never create unsolicited new Markdown files. Add a rule file only if the user names it and states its purpose. ---
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts