super-save_skill

Overview

This skill saves important project knowledge into a persistent supermemory so teams can preserve architectural decisions, major bug fixes, design patterns, and implementation details. It captures a short, human-readable record of the user's intent, the suggested solution, the decision taken, and any key files or details. The skill is implemented in JavaScript and is meant to be used during conversations to lock knowledge into team memory.

How this skill works

When asked to save knowledge, the skill analyzes the user's request and formats a concise save entry that records the goal, the suggested approach, the final decision, and relevant files or notes. It produces a structured human-friendly block that reflects the conversation flow and then invokes a script to persist the formatted content to supermemory. The entry is intended for team reference and future retrieval.

When to use it

• After resolving an architectural decision that the team should remember
• When documenting a significant bug fix and its root cause
• To capture a new design pattern or library choice for future consistency
• When saving implementation details that help onboard teammates
• Before closing a feature to preserve rationale and file references

Best practices

• Keep entries focused: one decision or topic per save block
• Include the who, what, why, and any related files or paths
• Use clear, simple language to make saves easy to scan later
• Save immediately after the decision so context is fresh
• Avoid attaching transient debug output; prefer actionable details

Example use cases

• Saving the chosen database migration strategy and related scripts
• Recording the root cause and fix for a production crash and affected files
• Capturing why a specific authentication library was selected for the project
• Storing a team-agreed API versioning approach and example endpoints
• Documenting a performance optimization and the benchmarks used