meta-documentation

Organize knowledge placement across CLAUDE.md, SKILL.md, memory, agents, and references.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/JoernStoehler/msc-math --skill meta-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-documentation
Source: https://github.com/JoernStoehler/msc-math/tree/main/.claude/skills/meta-documentation
Command: npx skills add https://github.com/JoernStoehler/msc-math --skill meta-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides structured guidance for writing and updating the meta-layer (CLAUDE.md, SKILL.md, agents, memory, and references) to prevent duplication, drift, and unsafe changes; aligns teams on where to place knowledge.

Core Features & Use Cases

  • Outlines the official placement governance for meta-layer knowledge
  • Presents a decision framework to route knowledge to CLAUDE.md, SKILL.md, references, memory, or tools
  • Includes rationale on architecture layering and change-management practices

Quick Start

Review the meta-documentation before editing the meta-layer to ensure correct placement and consistency.

Frequently Asked Questions about meta-documentation

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

FAQPage Schema
How do I organize knowledge in CLAUDE.md and SKILL.md to prevent duplication?

Organize knowledge in CLAUDE.md and SKILL.md by applying a decision framework that routes information to the correct meta-layer component, preventing duplication and drift across agents and references.

When should I update memory versus references in the meta-layer?

Update memory versus references by following placement governance that directs dynamic state to memory and static supporting context to references, ensuring safe changes during execution and review.

What is the best way to manage meta-layer drift across agents and documentation?

Manage meta-layer drift by hardening structure through defined decision records and architecture layers, aligning teams on where to place knowledge before modifying CLAUDE.md or agents.

How do I apply a decision framework for placing knowledge in agent memory and references?

Apply the decision framework during planning, execution, and review phases to route knowledge into agent memory, references, or tools based on architecture layering and change-management rationale.

Why does my meta-layer documentation drift when updating CLAUDE.md and SKILL.md?

Meta-layer documentation drifts when updates bypass placement governance; enforce best practices by reviewing decision records and architecture layers before modifying CLAUDE.md and SKILL.md.

Can I use a decision framework to govern changes to agents and references without causing drift?

Yes, a decision framework governs changes to agents and references by enforcing structured placement rules and change-management practices that prevent unsafe modifications and knowledge drift.