maintaining-project-context

Update CLAUDE.md context files to reflect contract-level code changes.

Updated Aug 23, 2026

Search Tags:#workflow #architecture #documentation #claude-context #git-diff #domain-context #contract-changes

Ready to run

npx skills add https://github.com/cyarie/cyarie-claude-plugin --skill maintaining-project-context-cyarie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maintaining-project-context
Source: https://github.com/cyarie/cyarie-claude-plugin/tree/main/skills/maintaining-project-context
Command: npx skills add https://github.com/cyarie/cyarie-claude-plugin --skill maintaining-project-context-cyarie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When code changes alter contracts or architectural intent, project context files (CLAUDE.md) must be updated to reflect the new reality to avoid drift and miscommunication.

Core Features & Use Cases

Detect contract-level changes and map them to the correct CLAUDE.md context files.
Read, draft, and update domain and root context documentation with clear invariants and decisions.
Ensure documentation standards are followed so future agents understand contracts and architectural intent.

Quick Start

Run the established workflow to identify contract-level changes and update the corresponding CLAUDE.md context files.

Frequently Asked Questions about maintaining-project-context

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

FAQPage Schema

How do I keep CLAUDE.md project context files in sync with code changes?▼

To keep CLAUDE.md context files in sync, identify contract-level changes from recent refactors or API updates and map them to the correct domain or root context files. Draft updates that clearly state invariants, contracts, and architectural decisions to reflect code evolution accurately.

When do I need to update project context documentation after a refactor?▼

Update project context documentation after significant refactors or API changes that alter contracts or architectural intent. Run the workflow to detect these contract-level shifts and draft corresponding updates to CLAUDE.md files, preventing documentation drift and future agent miscommunication.

What is the best way to document architectural decisions and invariants in CLAUDE.md?▼

The best way to document architectural decisions in CLAUDE.md is to apply a structured workflow after code evolution that maps contract changes to the correct context files. Draft updates following documentation standards so contracts, invariants, and architectural intent are clearly stated for future agents.

How do I detect contract-level changes from a git diff and update domain context?▼

To detect contract-level changes from a git diff, analyze significant refactors or API modifications and map them to the appropriate domain context files. Draft updates that properly document new or updated domains, ensuring invariants and architectural decisions are clearly recorded.

Can I use this workflow to document new API endpoints in root context files?▼

Yes, you can use this workflow to document new API endpoints by identifying the contract-level changes and mapping them to the correct root or domain CLAUDE.md context files. It drafts updates following documentation standards so new domains are properly documented.