learn

You can store and organize project learnings across sessions in a single append-only markdown file. The skill enforces a strict format and de-duplication by key to keep your knowledge base clean and searchable.

You can search and prune development knowledge using dedicated commands like /learn search and /learn prune. These commands help you interactively manage your knowledge file, ensuring outdated entries are removed while keeping your team aligned.

Yes, the approach supports categorizing learnings into multiple types including Patterns, Pitfalls, Preferences, Architecture, and Tools. This categorization helps structure your markdown file for better organization and retrieval.

Yes, you can export markdown learnings for team review using /learn export and track usage with /learn stats. It also includes telemetry for usage insights to help you understand how your team interacts with the knowledge base.

You can add new entries to the centralized learnings file using the /learn add command. The system strictly enforces de-duplication by key, preventing identical entries from being appended to your markdown history.

Managing project knowledge in a markdown file is append-only and prevents direct code changes. This ensures historical integrity but means you must use specific commands like /learn prune to remove or update outdated information.