awf-save-brain

Synchronizes codebase changes with brain.json and session.json files.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/buiminhduc23011/awf-for-codex --skill awf-save-brain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: awf-save-brain
Source: https://github.com/buiminhduc23011/awf-for-codex/tree/main/skills/awf-save-brain
Command: npx skills add https://github.com/buiminhduc23011/awf-for-codex --skill awf-save-brain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of AI forgetting project context during long sessions or across multiple sessions, ensuring that technical documentation, architecture, and progress remain synchronized with the codebase.

Core Features & Use Cases

  • Proactive Handover: Automatically generates a summary document when the context window is near capacity.
  • Structured Knowledge Sync: Updates static knowledge (brain.json) and dynamic session state (session.json) to keep the AI's memory accurate.
  • Documentation Automation: Generates and updates API documentation, changelogs, and system architecture files based on recent code changes.

Quick Start

Invoke the save brain skill to capture the current project state and update all documentation files.

Frequently Asked Questions about awf-save-brain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AI from forgetting project context during long sessions?

Project context drift is prevented by synchronizing codebase changes with structured documentation and session state files. This maintains persistent memory by updating architecture, API specifications, and business logic records automatically.

How do I maintain AI memory across multiple coding sessions?

AI memory is maintained across multiple coding sessions by managing local brain.json and session.json files. These files store static knowledge and dynamic session state to ensure seamless continuity for long-term development tasks.

Can I automatically generate a context handover document when the context window is full?

Yes, a context handover summary document is automatically generated when the context window is near capacity. This proactive handover ensures seamless continuity for long-term development tasks.

How do I keep API documentation and changelogs synchronized with recent code changes?

API documentation and changelogs are synchronized with recent code changes by scanning project files to update architecture and specification records. This documentation automation ensures technical records remain aligned with the codebase.

Do I need external dependencies to sync session state files with my codebase?

No external dependencies are required to sync session state files with your codebase. The process operates locally by managing brain.json and session.json files to maintain structured knowledge and dynamic session state.