session-memory

To persist AI findings across multiple sessions, save the outputs from skill executions into structured markdown files. This creates a cumulative knowledge base that remains accessible for future recall, comparison, and correlation.

The best way to compare design system audit results between runs is by analyzing metric deltas and finding statuses. This comparison highlights resolved, persistent, and new issues to identify trends across historical data.

Yes, you can cross-reference findings from different skill types to identify systemic patterns. By correlating outputs across different skills, you can surface interdependencies and gain a holistic view of design system health.

You retrieve historical findings for a specific skill or date range by recalling saved session files from the persistent memory layer. This allows you to summarize past findings and review cumulative data over time.

No specific dependencies are required to build a persistent knowledge base for design system operations. The system relies on structured markdown files to manage the persistence, recall, and correlation of findings across sessions.