/knowz save
The /knowz save command captures knowledge from your current conversation and stores it in the appropriate vault. It auto-routes based on configurable rules -- security findings go to the security vault, architecture decisions go to the architecture vault. You can also specify a vault explicitly.
Getting started
Type /knowz save followed by the insight: '/knowz save JWT refresh tokens should be rotated on each use to prevent replay attacks'. The skill analyzes the content, determines the appropriate vault based on your routing rules, tags it automatically, and saves it. If no routing rule matches, it asks which vault to use. You can also save with explicit targeting: '/knowz save --vault security-patterns "..."'.
Terminal showing /knowz save with automatic vault routing
Screenshot coming soon
Why it matters
The hardest part of knowledge management is capture. Insights emerge during development -- a tricky bug fix, a design decision rationale, a useful pattern. /knowz save lets you capture these in the moment with zero friction. The auto-routing ensures knowledge ends up in the right place without manual organization. Over time, this builds a rich knowledge base that grows organically from real development work.
Vault contents growing from regular /knowz save usage
Screenshot coming soon