Asset Evolver

Activation Conditions (When to Use)

/asset-evolve

/asset-update

1. Target Asset: The specified existing knowledge card that must be updated (usually Level S or Level A, with a five-layer structure Markdown card).
2. New Context: New pitfalls the user just encountered in the project, new inapplicable scenarios, or optimization ideas for old methods.

🛑 The Core Directive

• Prohibit "over-concentration" and "full rewrite": This is the biggest red line! It is strictly forbidden to delete or abbreviate large areas of high-fidelity business scenarios such as

  00 Pain Points and Questions

  (symptoms of pain) and

  03 Why Did This Happen

  (trial and error paths) in the original old assets for the sake of smooth writing.
• Prohibit destroying the original structure: Keep the original Markdown directory structure of the old card unchanged, and never split or break the five-layer structure.

• Minimally Invasive Surgery (Append & Merge): Use incremental Append or non-destructive Merge methods.
  • For example: Under the original list of errors, start a new line with

    - [2026-02-xx Updated New Pitfall] ...

    .
  • If there is conflicting experience, or the old method fails in new scenarios, use a blockquote to mark it, such as

    > [!tip] Iteration Patch (YYYY-MM-DD): In XXX scenario, the above method fails, and should be changed to...

• Protect Proof of Work: Treat each trial and error path and error log of the user as "golden assets", ensuring that both new and old experiences are retained with full granularity.

Core Evolution Workflow

Phase 1: Cross Diagnosis

1. New Boundary: Did you discover a new scenario where the original method cannot be applied? 👉 Should be updated to the "Inapplicable Scenarios" section of

   01 Boundaries and Premises

   .
2. New Pain Points/Pitfalls: Did you encounter a new pitfall that you didn't think of before? 👉 Should be updated to the "Wrong Attempts" section of

   00 Pain Points and Questions

   , or the "Consequences of Ignoring Advice" section of

   03 Why Did This Happen

   .
3. New Solutions/Optimizations: Do you have a more streamlined code/process? 👉 Should be updated to

   04 How to Solve It

   (as an iterative solution or replacement, but if replacing, the old solution must be marked as deprecated and retained, not directly deleted).
4. New Insights: Have you realized a higher-dimensional rule? 👉 Should be updated to

   05 Underlying Logic

   .

Phase 2: Issue Evolution Proposal

🛠️ Asset Evolution Proposal

📍 Diagnosis Result: The core value of this new record is confirmed to be verifying that "the original method is not applicable in XX complex scenarios (supplementary boundary)" and providing "a new one-line command alternative solution (solution optimization)".

📝 Targeted Fine-tuning Plan:

• Append 1 (01 Boundaries and Premises): Add a new item to "Inapplicable Scenarios": "[Summary: Describe which business environment will cause the original method to report errors]".
• Update 2 (04 How to Solve It): Under the original operation steps, use the

  > [!info] Iteration Patch (YYYY-MM-DD)

  block to add this extremely simplified alternative command as the recommended preferred solution.
• Append 3 (00 Pain Points and Questions): Append this new error scenario and the user's desperate attempts as the second classic case of

  Wrong Attempts

  below it (never overwrite old cases).

🎖️ Status Recommendation: This asset has now withstood tests from at least two real projects and is continuously improving. It is recommended to upgrade the status in the YAML header from

🌿 Beta (Trial)

to

🌳 Stable (Mature)

.

Please Confirm:

• y

  or

  update directly

  : Agree to execute targeted minimally invasive surgery.

• modify plan

  : Tell us which part of the merging logic you want to adjust.

Phase 3: Non-destructive Execution and Writing

y

1. Status Mark Upgrade: If the

   status

   of the original asset is

   Beta

   , change it to

   Stable

   according to the proposal agreement (if you believe it has indeed undergone cross-scenario reuse verification).
2. Targeted Embedding: Precisely locate the subheadings identified in the above diagnosis and insert the corresponding incremental content.
3. Metadata Maintenance: Never mess up the original

   aliases

   ,

   tags

   , and

   create_date

   in the YAML header.

AI Pitfall Prevention Checklist (Checklist before sending output)

• Have I resisted the urge to condense and clean up? (Cannot wash away the user's contextual emotions like a Refiner)
• Has this update only made "additions"? Or only marked old content as deprecated instead of cruelly erasing it?
• Have I listed clearly why the new "trial and error path" failed, instead of just writing "new failures encountered"?