update-context

Update CLAUDE.md with context-rich, versioned project knowledge.

55|5|Updated Feb 1, 2024
One-click install
npx skills add https://github.com/MakePrisms/agicash --skill update-context-makeprisms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-context
Source: https://github.com/MakePrisms/agicash/tree/main/.claude/skills/update-context
Command: npx skills add https://github.com/MakePrisms/agicash --skill update-context-makeprisms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

You are the expert maintainer of CLAUDE.md — the persistent, high-value context file that prevents stale assumptions and context pollution. Use this skill when you need to ensure context stays accurate after codebase changes or strategic decisions, and to automate recommendations for CLAUDE.md updates.

Core Features & Use Cases

  • Maintains CLAUDE.md as a living knowledge base that captures learnings over time.
  • Provides structured guidance for updating context after major refactors, feature additions, or policy changes.
  • Applies to scenarios where you must add, modify, or remove project context or document evolving patterns and conventions.

Quick Start

Initiate the /update-context flow to review CLAUDE.md and propose the necessary context updates.

Frequently Asked Questions about update-context

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

FAQPage Schema
What is the best way to maintain project documentation and prevent stale assumptions in a knowledge base?

Maintaining documentation as a living knowledge base prevents stale assumptions by capturing learnings and applying context-rich, versioned rules with meta-rules after major codebase changes.

How do I update project context and guidelines after a major codebase refactor?

To update project context after a refactor, initiate a review flow to propose necessary guideline modifications, add new patterns, and document changes using structured, versioned notes.

When do I need to apply structured updates to my project's documentation standards?

You need to apply structured documentation updates when adding, modifying, or removing project context, or when documenting evolving patterns and conventions after strategic decisions.

Does this approach support versioning context rules and tracking where specific guidelines were learned from?

Yes, this approach supports versioning context rules by requiring context-rich entries organized under a clear structure, complete with meta-rules and specific "Learned from" tracking notes.

Can I use this method to automate recommendations for knowledge-base updates?

Yes, you can automate recommendations for knowledge-base updates to ensure context stays accurate after codebase changes, automatically proposing necessary modifications to prevent context pollution.

What are the limitations of keeping a static knowledge base without evolving documentation standards?

Without evolving documentation standards, a static knowledge base suffers from context pollution and stale assumptions, failing to capture learnings or reflect strategic decisions made during codebase evolution.