session-knowledge-creator

To enforce cross-session memory, you need an enforcement file like .instructions.md that is auto-injected into the AI context. This Skill generates that file along with a SKILL.md reference and a CLAUDE.md patch to wire memory guidelines into your workflow.

AI agents forget previous decisions because they lack persistent session memory. Applying a session-knowledge integration during project onboarding creates an enforcement file that ensures the AI reads and follows memory guidelines across sessions.

The best way to set up AI memory during project onboarding is to generate a session-knowledge integration. This creates a mandatory enforcement file auto-injected into every context and patches CLAUDE.md to point to your project-specific SKILL.md reference.

No, you do not need to manually patch CLAUDE.md. The session-knowledge integration automatically patches CLAUDE.md to point to the generated enforcement file and SKILL.md reference, enabling smooth onboarding and cross-session memory.

Yes, you can use session-knowledge enforcement for long-running tasks requiring memory across sessions. It generates an enforcement file that ensures AI agents read and follow memory guidelines throughout the ongoing development process.

The .instructions.md file works as a mandatory enforcement file that is auto-injected into every AI context. This ensures the AI agent reads and follows the project-specific session memory guidelines during every interaction.