Persistent temporal memory: file-based decision history, session context, searchable project notes, and recall across sessions. No daemons, workers, databases, or services (B-3).
Plugin rinnegan from marketplace awakened in coltonbearden/awakened. Commands read from the repo's manifest — 1 month ago.
architecture-decision-recordsRecord a significant technical or accessibility decision as a short decision record — context, the choice, the alternatives rejected and why, consequences — and file it in rinnegan's decision store or the project's ADR directory. Use when the user picks between frameworks, storage, API styles, auth
growth-logDistil a hard task, a failure or a surprise into a transferable learning entry — root cause, the pattern, the signal that will flag it next time — checked against earlier entries so the same lesson is never logged twice. Use after debugging that took longer than expected, a rollback or rework, a non
recalling-contextFind what earlier sessions did, decided or learned by searching rinnegan's file-based memory index, then session notes, then decision files — returning titles before bodies. Use when the user asks "what did we decide about X", "how did we handle this last time", "what was I working on", or when a ta
/rinnegan:captureWrite this session's memory to rinnegan's file store — a session note (Request, Completed, Learned) plus typed records appended to a searchable index — so a later session can recall what happened. Run at the end of a session or before a long break; safe to re-run, a second run appends nothing new.
/rinnegan:recallSearch rinnegan's session memory for a query — decisions, learned patterns, past sessions — and return a compact hit table before reading any body. Use when you need what an earlier session did, decided or learned about a topic.
Specialist subagents with restricted tool allowlists: research, exploration, debugging, review, planning, documentation, and synthesis agents, plus the skills that dispatch them. Every subagent in Awakened lives here (B-6).
7 skills · 27 agents
Core engineering workflow: planning, implementation discipline, test-driven development, systematic debugging, verification before completion, and git workflow guidance. The stable baseline - it depends on no agents, memory infrastructure, or project-specific tooling (B-1).
18 skills · 9 commands
Project-scoped structural context: codebase onboarding, code maps, documentation upkeep, conventions, domain modeling, and CLAUDE.md scaffolding. Structural context only; it stores no history (B-4).
7 skills · 2 commands
Marketplace meta tooling: skill creation, writing for agents, context budgeting, skill scouting, component auditing, and linting. Marketplace maintenance, not user workflow execution (B-7).
6 skills · 2 commands
Code review and analysis: review discipline, production audit, architecture inspection, AI-debt detection, and security-oriented review. Analysis and review only - implementation stays outside this plugin (B-2).
7 skills · 1 command
Session management and momentum: save and resume sessions, handoffs, checkpoints, and focused asides. Session momentum only - it duplicates no planning, debugging, or review system (B-5).
1 skill · 4 commands
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
AI memory system — mine projects and conversations into a searchable palace. 47 MCP tools, auto-save hooks, guided setup.
3 skills · 6 commands · 1 MCP server · hooks
Universal memory runtime for Claude Code with cross-session memory, entity-aware recall, lifecycle hooks, skills, commands, and memory-curator agents
7 skills · 7 commands · 2 agents · hooks
Long-term semantic memory for Claude Code, powered by OpenViking
5 skills · 1 command · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.