docs: add bad case

Author: gusye1234

docs/site/docs.json

@@ -49,6 +49,7 @@
           {
             "group": "Practices",
             "pages": [
+              "practices/bad",
               "practices/tips",
               "practices/openai"
             ]

docs/site/features/profile/profile_filter.mdx

@@ -1,5 +1,5 @@
 ---
-title: Filter Profile
+title: Filter Profile when Retrieving
 ---
 For each user, Memobase will track and model the profile.
 You can use them in your [AI prompt](/features/context) to offer a global understanding of the user.

docs/site/practices/bad.mdx

@@ -0,0 +1,18 @@
+---
+title: How to Fix Bad Cases
+---
+
+## Too many useless profile memories
+1. Make sure you have the idea of what a profile should have.
+2. [Configure](/features/profile/profile_desc) your `config.yaml` properly with profile slots' description.
+3. If you still have too many useless profile memories, you can enable [strict mode](/features/profile/profile_config#strict-mode) 
+to only collect the profiles you want.
+
+## Some profiles should be extracted, but it's not.
+1. Maybe your profile description is too hard for LLM to understand/infer, try to lower your requirements.
+2. If you still have this issue, you can disable the [profile validation](/features/profile/profile_config#profile-validate-mode) 
+
+## My profile is inaccurate/wrong.
+1. Add more details to your [profile description](/features/profile/profile_desc), making sure the profile description is clear and easy to understand.
+2. Add [update descrption](/features/profile/profile_desc#instruct-memobase-to-update-a-profile-slot) for that profile also, it will help Memobase to merge the profile wisely.
+

docs/site/practices/tips.mdx

@@ -11,15 +11,14 @@ In simple terms, Memobase can provide user profile memory for your users. You ca
   description: "Track the gaming preferences/achievements of the user."
   sub_topics:
       - name: "FPS"
-        description: "Games like CSGO, Valorant, etc."
       - name: "LOL"
         ...
 - topic: "Whatever"
   sub_topics:
     ...
 ```
 Memobase will generate user profile preferences based on your configuration.
-Refer to [Customization](/features/customization/profile) for more details.
+Refer to [Customization](/features/profile) for more details.
 
 ## How to Integrate Memory?
 
@@ -40,7 +39,8 @@ Normally, you should call `flush` API right after a chat session is closed.
 
 ## User System Management
 
-Users in Memobase do not need to correspond one-to-one with your actual users. One of your actual users can correspond to multiple Memobase users if a user in your application has multiple segmented memories:
+Users in Memobase do not need to correspond one-to-one with your actual users. 
+One of your actual users can correspond to multiple Memobase users if a user in your application has multiple segmented memories:
 
 - AI Role-Playing: Each agent should have independent memory for the user, so one user might have dozens of corresponding Memobase users for the various role agents they have interacted with.
 - AI Companionship + AI Education: You might provide a unified agent for the user, in which case your user can correspond one-to-one with Memobase.