knowledge-persistence

To save actionable knowledge into structured markdown notes, this Skill captures decisions, patterns, and architectural insights into Obsidian documents with enforced frontmatter. It organizes entries into specific category directories within a .knowledge/ folder for reliable retrieval.

Yes, for knowledge base persistence, this Skill enforces specific frontmatter requirements including title, date, and tags. This metadata ensures that captured notes remain searchable and reusable across different projects over time.

The best way to categorize troubleshooting notes for reuse is by storing them in structured directories like learnings/, patterns/, or references/. This Skill enforces a consistent naming scheme and path conventions to enable targeted retrieval.

Yes, you can update existing knowledge entries. This Skill supports lifecycle and reusability by allowing you to modify current documents and build a growing knowledge base without creating unnecessary duplicates.

When saving architectural notes and gotchas, you should use enforced category directories such as architecture/, decisions/, learnings/, patterns/, or references/ to maintain a highly structured and searchable knowledge base.