hierarchical-agent-memory
FeaturedScoped CLAUDE.md memory system that reduces context token spend. Creates directory-level context files, tracks savings via dashboard, and routes agents to the right sub-context.
Install
Quality Score: 99/100
Skill Content
Details
- Author
- sickn33
- Repository
- sickn33/antigravity-awesome-skills
- Created
- 4 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
self-improving-agent
Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2) graduating a pattern from notes to enforced rules, (3) turning a debugging solution into a skill, (4) checking memory health and capacity.
memory_road
Persistent 11-layer memory architecture for Claude Code · drop-in for any agent / any project. Substrate (continuity-kernel.service) captures every event to SQLite FOREVER · always-on · LLM-free · indestructible. Comprehension layers (FURROW → SCRIBE → CHRONICLER → CARTOGRAPHER → MINER+SMITH → HUNTSMAN) extract structured meaning over time. Snow plow workers stack parallel from RIGHT-NOW backwards through history · always sharpening recent recall first. Blank-slate workers + batch-5 + strip-CLAUDE.md = 15-25x throughput vs naive single-fire. Forward sweeper keeps the now-edge clean automatically. HUNTSMAN surfaces every unfinished item. CARTOGRAPHER clusters episodes by theme. MINER+SMITH propose lockable doctrines. Forced memory injection on every user prompt via hook · the agent CANNOT forget to use memory. CANONICAL TURN-ON ORDER (every fresh install) · 1. FOUNDATION · substrate (L0) + chunking (L1) → records everything forever 2. FORWARD MEMORY · forward sweeper + WATCHER → now-edge stays summarized 3. BA
claude-md
Create and optimize CLAUDE.md memory files or .claude/rules/ modular rules for Claude Code projects. Covers file hierarchy, content structure, path-scoped rules, best practices, and anti-patterns. Use when working with CLAUDE.md files, .claude/rules directories, setting up new projects, or improving Claude Code's context awareness — even when the user just says "memory file" or mentions Claude instructions without naming the filename.
project-memory
Generate CLAUDE.md project memory files that transfer institutional knowledge, not obvious information. Use when setting up new journalism projects, onboarding collaborators, or documenting project-specific quirks. Includes templates for editorial tools, event websites, publications, research projects, content pipelines, and digital archives.
claude-md-architect
Design, create, extract, or audit CLAUDE.md files and their supporting docs/ folder structure for Claude Code projects. Use this skill whenever the user asks to create a new CLAUDE.md, extract context from a long session into a CLAUDE.md system, audit/refactor an existing CLAUDE.md that has bloated, review whether their CLAUDE.md follows best practices, set up a documentation system for Claude Code, or design progressive disclosure with @ imports and subdirectory CLAUDE.md files. Also use when user says "setup CLAUDE.md", "create context system", "fix my CLAUDE.md", "extract this conversation", "ทำ CLAUDE.md", "สร้างระบบ context", "audit ไฟล์", or mentions phrases about session continuity and project memory in Claude Code. For conceptual explanations or teaching, point the user to the README at https://github.com/trin-zenityx/claude-md-architect — that's where the pedagogical material lives.