From totto2727
This skill should be used when persisting development insights, recalling past decisions, building knowledge graphs, or managing AI agent memory. Relevant when the user asks to remember something, recall context, link ideas, or maintain a knowledge base across sessions. Common triggers: "remember this", "recall previous decisions", "store insight", "what did we decide about", "knowledge graph", "exocortex".
npx claudepluginhub totto2727-org/monorepo --plugin totto2727This skill uses the workspace's default tool permissions.
A "second brain" for AI agents — persist insights, recall past decisions, and build knowledge graphs across sessions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
A "second brain" for AI agents — persist insights, recall past decisions, and build knowledge graphs across sessions.
| Tool | Purpose |
|---|---|
exo_store_memory | Persist insights with tags, context, and optional "painful memory" flag |
exo_recall_memories | Search knowledge base with natural language queries and filters |
exo_link_memories | Connect memories via relations (related, extends, depends_on, supersedes, contradicts, evolved_from, rejected_because, caused_by) |
exo_explore_related | Discover adjacent knowledge through links, tags, and context |
exo_trace_lineage | Trace decision evolution backward/forward through relations |
exo_curiosity_scan | Detect contradictions, orphans, and outdated information |
exo_sleep | Background maintenance: deduplication, orphan rescue, pattern mining |
exo_consolidate | Extract common themes from similar memories |
exo_analyze_knowledge | Diagnose health issues (orphans, stale content) |
exo_get_stats | Knowledge base overview with counts and trending tags |
exo_recall_memories — retrieve relevant contextexo_store_memory — persist discoveries with structured Problem/Solution/Rationale sections and specific tagsexo_sleep — consolidate and maintain the knowledge baseChoose the appropriate relation when linking memories:
| Relation | Use When |
|---|---|
related | Two memories share a topic but neither depends on the other |
extends | Memory B adds detail or depth to memory A |
depends_on | Memory B requires knowledge from memory A |
supersedes | Memory B replaces an outdated memory A |
contradicts | Two memories contain conflicting information |
evolved_from | Memory B is a refined version of memory A |
rejected_because | A decision was abandoned — link to the reason |
caused_by | An outcome was triggered by a prior event or decision |
auth-flow, postgres-migration, api-v2bug:, decision:, pattern:billing-service, frontend-auth2026-03, sprint-42Structure the content field for maximum recall value:
**Problem:** [What happened or what question arose]
**Solution:** [What was done or decided]
**Rationale:** [Why this approach was chosen]
**Tags:** specific-module, decision-type