grimoire

Update or create CLAUDE.md files across multiple projects with session changes.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jtucker9/mystuff --skill grimoire-jtucker9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grimoire
Source: https://github.com/jtucker9/mystuff/tree/main/skills/grimoire
Command: npx skills add https://github.com/jtucker9/mystuff --skill grimoire-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically synchronize CLAUDE.md documents across all projects by recording session changes and decisions, preventing drift and orphaned entries.

Core Features & Use Cases

  • Consolidates updates from a session into the target CLAUDE.md files across multiple projects.
  • Creates CLAUDE.md when missing and populates standard sections such as Project Overview, Tech Stack, Directory Structure, Key Files, API Endpoints, Database Schema, Environment Variables, and Dev Commands.
  • Use case: after significant product or code changes, Grimoire updates the knowledge library to reflect new decisions and architectural directions.

Quick Start

Update the CLAUDE.md for the current project with the latest session changes.

Frequently Asked Questions about grimoire

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

FAQPage Schema
How do I keep CLAUDE.md files updated across multiple projects after a session?

To keep CLAUDE.md files updated across multiple projects, you can use an automation Skill that reads existing files, determines new additions based on session work, avoids duplicate entries, and applies a consistent format while preserving current content.

What is the best way to automate CLAUDE.md documentation for project knowledge bases?

Automating CLAUDE.md documentation involves consolidating session updates into target files, creating missing documents, and populating standard sections like Project Overview, Tech Stack, Directory Structure, Key Files, API Endpoints, Database Schema, Environment Variables, and Dev Commands.

Does updating CLAUDE.md preserve existing project entries when adding new session changes?

Updating CLAUDE.md preserves existing project entries by reading the current file when present, determining what to add based on session work, avoiding duplicating entries, and applying a consistent format to update or create the document.

Can I create a CLAUDE.md file automatically when starting a new project?

You can create a CLAUDE.md file automatically when missing, populating standard sections such as Project Overview, Tech Stack, Directory Structure, Key Files, API Endpoints, Database Schema, Environment Variables, and Dev Commands to reflect architectural directions.

Why does CLAUDE.md documentation drift across multiple projects over time?

CLAUDE.md documentation drifts across multiple projects when session changes and decisions are not recorded, causing orphaned entries; synchronizing updates automatically prevents this drift by reflecting new decisions and architectural directions consistently.