system_overview

Solid

Show how Continuous Claude works - the opinionated setup with hooks, memory, and coordination.

AI & Automation 501 stars 42 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# System Overview Show users how Continuous Claude works - the opinionated setup with hooks, memory, and coordination. ## When to Use - User asks "how does this work?" - User asks "what can you remember?" - User asks "what's different about this setup?" - User runs `/system_overview` ## Response ``` CONTINUOUS CLAUDE SYSTEM OVERVIEW ================================= MEMORY LAYER (PostgreSQL + pgvector) ------------------------------------ - 78,000+ temporal facts from past sessions - Learnings extracted automatically at session end - Semantic search with embeddings RECALL: uv run python opc/scripts/recall_temporal_facts.py --query "your topic" HOOKS (9 event types registered) -------------------------------- SessionStart → Load continuity ledger, rebuild symbol index UserPromptSubmit → Skill activation check, context injection PreToolUse → Smart search routing (Grep → TLDR for code) PostToolUse → File claims, compiler feedback PreCompact → Save state before context compaction Stop → Extract learnings, create handoffs SubagentStart → Register spawned agents SubagentStop → Coordination, handoff creation SessionEnd → Cleanup CONTINUITY SYSTEM ----------------- Ledger: thoughts/ledgers/CONTINUITY_CLAUDE-{session}.md Handoffs: thoughts/shared/handoffs/{session}/*.yaml Commands: /resume_handoff <path> - Continue from handoff /create_handoff - Create snapshot for transfer TL...

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
2 months ago
Last Updated
yesterday
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

system-overview

Show users how Continuous Claude works - the opinionated setup with hooks, memory, and coordination

3,809 Updated 4 months ago
parcadei
AI & Automation Listed

claude-recall

Always-on Claude Code skill that bridges Claude with an Obsidian vault for persistent project memory. Automatically loads relevant context nodes from mindmap.json before every prompt (UserPromptSubmit hook) and saves structured session notes to the vault on exit (Stop hook). Zero manual invocation — hooks fire automatically. Context is AUTO-GENERATED using the claude CLI. Claude analyzes transcripts and project files to populate mindmap.json with stack, architecture decisions, gotchas, and current state. Users never need to manually edit. The /recall command lets users trigger on-demand context updates from the terminal. MCP tools (recall_get, recall_update_node, recall_session_history, recall_mindmap) let Claude fetch deeper context mid-session. Storage: <vault>/claude-recall/projects/<project-slug>/mindmap.json (JSON graph) and sessions/YYYY-MM-DD_HH-MM.md (session notes). Project slug is derived from the directory Claude Code was launched in. Install from GitHub (one command): curl -fsSL https://raw.github

6 Updated 1 weeks ago
senapati484
AI & Automation Listed

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

1 Updated 1 weeks ago
RickyPOnline