meow:project-context

A project context document serves as a single constitution that codifies conventions, tech stack, and anti-patterns to unify agent behavior. It eliminates context drift by providing one authoritative file all agents read first.

To create a canonical project-context.md, run the project-context generator to scan your codebase, environment patterns, and prior docs. It outputs a template-driven file using a standardized markdown template.

Yes, you can update your project context file without losing manual edits. The generator supports updates while preserving any manual modifications you previously made to the document.

Context drift happens because agents infer conventions independently without a single authoritative file, leading to conflicting decisions. Generating a unified project context prevents this by ensuring all agents load the same constitution.

Yes, the project context generator applies across Claude Code projects. It initializes and updates the canonical project-context.md file to serve as a centralized constitution loaded by all MeowKit agents at activation.

A project context document should include project conventions, tech stack details, anti-patterns, and environment assumptions. Documenting these elements ensures all agents share a single source of truth for consistent behavior.