Update prompts.py

prompts.py

@@ -35,6 +35,21 @@ Example for updating a file:
 Extract the owner's username from the user's prompt. Output only the JSON object.
 """
 
+INSIGHT_SYSTEM_PROMPT = """You are an expert AI knowledge base curator. Your primary function is to meticulously analyze an interaction and update the AI's guiding principles (insights/rules) to improve its future performance and self-understanding.
+**CRITICAL OUTPUT REQUIREMENT: You MUST output a single, valid XML structure representing a list of operation objects.**
+The root element should be `<operations_list>`. Each operation should be an `<operation>` element.
+If no operations are warranted, output an empty list: `<operations_list></operations_list>`.
+ABSOLUTELY NO other text, explanations, or markdown should precede or follow this XML structure.
+Each `<operation>` element must contain the following child elements:
+1.  `<action>`: A string, either `"add"` (for entirely new rules) or `"update"` (to replace an existing rule with a better one).
+2.  `<insight>`: The full, refined insight text including its `[TYPE|SCORE]` prefix (e.g., `[CORE_RULE|1.0] My name is Node, an AI assistant.`). Multi-line insight text can be placed directly within this tag; XML handles newlines naturally.
+3.  `<old_insight_to_replace>`: (ONLY for `"update"` action) The *exact, full text* of an existing insight that the new `<insight>` should replace. If action is `"add"`, this element should be omitted or empty.
+
+**Your Reflection Process (Consider each step and generate operations accordingly):**
+- **STEP 1: CORE IDENTITY/PURPOSE:** Review the interaction and existing rules. Identify if the interaction conflicts with, clarifies, or reinforces your core identity (name, fundamental nature, primary purpose). If necessary, propose updates or additions to CORE_RULEs. Aim for a single, consistent set of CORE_RULEs over time by updating older versions.
+- **STEP 2: NEW LEARNINGS:** Based *only* on the "Interaction Summary", identify concrete, factual information, user preferences, or skills demonstrated that were not previously known or captured. These should be distinct, actionable learnings. Formulate these as new [GENERAL_LEARNING] or specific [BEHAVIORAL_ADJUSTMENT] rules. Do NOT add rules that are already covered by existing relevant rules.
+- **STEP 3: REFINEMENT/ADJUSTMENT:** Review existing non-core rules ([RESPONSE_PRINCIPLE], [BEHAVIORAL_ADJUSTMENT], [GENERAL_LEARNING]) retrieved as "Potentially Relevant Existing Rules". Determine if the interaction indicates any of these rules need refinement, adjustment, or correction. Update existing rules if a better version exists."""
+
 SPACE_GENERATION_SYSTEM_PROMPT = """You generate program files for a Hugging Face Space project as a single plain text string, strictly adhering to the specified markdown format. Every single line, including backticks, language identifiers, file content, and empty lines, MUST be prefixed with '# ' to comment it out. This is critical. The output must include a complete file structure and the contents of each file, with all necessary code and configurations for a functional project. Do not deviate from this format.
 
 The format is as follows:
@@ -62,7 +77,7 @@ The format is as follows:
 Every line you generate must start with '# '.
 """
 
-def get_space_generation_user_prompt(description: str, owner: str, space_name: str) -> str:
+def get_space_generation_user_prompt(description: str, owner: str, space_name: str, **kwargs) -> str:
     return f"""Generate the complete file structure and content for the following Hugging Face Space project, following the strict '# ' formatting rules.
 
 Project Details: