Clement

Import memories from other AI memory systems into Cortex. Supports claude-mem (SQLite), Claude Desktop sessions, ChatGPT web export (JSON), Gemini Takeout (JSON), Cursor conversations, and Claude Code JSONL. Use when the user says 'import from claude-mem', 'migrate memories', 'import ChatGPT history', 'import from Gemini', 'transfer memories', or when Cortex detects another memory system is installed.

View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile' to rescan all session history, or 'list domains' to see all tracked project domains.

Navigate the knowledge graph — trace entity relationships, explore causal chains, drill into memory clusters, and traverse co-access paths. Use when the user asks 'how are these related', 'what connects X to Y', 'show me the knowledge graph', 'trace the relationship', 'what caused X', 'drill down into', 'explore connections', or when you need to understand the web of relationships between concepts, entities, and memories.

Search and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or architecture choices. Also use proactively when working on something that likely has relevant historical context.

Bootstrap Cortex for a new project or import existing session history. Use when the user says 'set up Cortex', 'seed this project', 'import my history', 'backfill memories', 'bootstrap memory', 'initialize Cortex for this project', or when starting to use Cortex on an existing codebase that already has Claude Code conversation history.

Store important decisions, patterns, errors, lessons, and context into Cortex persistent memory. Use when the user says 'remember this', 'save this', 'store this for later', 'note this down', 'don't forget', 'this is important', 'bookmark this', or when a significant decision, bug fix, architecture choice, or lesson learned occurs during a session. Also use after resolving tricky bugs, making technology choices, or discovering important patterns.

Launch the interactive unified neural graph visualization. Use when the user says 'show visualization', 'show me the graph', 'visualize memories', 'show memory map', 'open neural graph', or when a visual overview of the memory system or cognitive profile would be helpful.

View your cognitive methodology profile and reasoning patterns

Store a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global rule', 'shared convention', 'infrastructure note', 'cross-project', or when the content is clearly universal (clean architecture, SOLID, deployment configs, server addresses).

Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to automate memory behavior based on conditions.

Debug and fix memory system issues — validate memories, rate quality, manage protection, forget bad memories, and restore from checkpoints. Use when the user says 'fix memory', 'bad memory', 'wrong memory', 'delete this', 'protect this', 'this memory is wrong', 'memory quality', 'rate this memory', 'restore checkpoint', 'undo', or when memories are returning incorrect or stale results.

Rewrites Cortex wiki pages to match their kind's template + naming convention. Use when audit_wiki reports drift: missing front-matter, wrong status values, non-canonical slugs, or missing required sections. Preserves content semantics — never deletes information; restructures and fills gaps from existing context.

Author first-class wiki pages (ADRs, specs, file docs, notes) that live alongside Cortex memory. Use when the user says 'this is an ADR', 'document this decision', 'write an ADR', 'add a spec', 'spec this out', 'document this file', 'add a note about', 'link these pages', 'bookmark this as a spec', or when finalizing a design decision that should persist as a human-readable document.

Run memory maintenance — decay old memories, compress stale content, consolidate episodic memories into semantic knowledge, and run sleep-like replay. Use when the user says 'clean up memories', 'consolidate', 'run maintenance', 'compress old memories', 'memory cleanup', or periodically to keep the memory system healthy. Also use after importing many memories or at the end of a long session.

Search and retrieve global memories — knowledge that applies across all projects. Use when the user asks 'what are our coding standards', 'what conventions do we follow', 'what's our infrastructure setup', 'do we have a rule about', 'what applies to all projects', 'shared knowledge', 'global rules', or when you need cross-project context like architecture decisions, server configs, or team policies.

Explore the memory system's state, find gaps in knowledge, assess coverage, and get diagnostic information. Use when the user asks 'what does my memory look like', 'show me memory stats', 'what am I missing', 'how good is my knowledge', 'memory health', 'show coverage', 'find gaps', 'what topics are weak', or when you need to understand the state of stored knowledge before a task.

Database specialist adapting to any engine (PostgreSQL, MySQL, SQLite, MongoDB, etc.) — schema design

ML infrastructure specialist — training pipelines, model serving, GPU optimization, distributed training

UX/UI designer focused on usability, accessibility, information architecture, and design systems

Proactively review code changes for Clean Architecture, SOLID, size limits

Academic teaching specialist — explains concepts at the right level, builds mental models, designs exercises

Proactively analyze structural changes, decomposition decisions

Research scientist specializing in reproducible empirical ML/IR research — designs experiments

Software engineer specializing in Clean Architecture, SOLID, and root-cause problem solving

Academic peer reviewer — evaluates paper drafts against NeurIPS/ICML/CVPR/ACL reviewer standards for novelty

Frontend engineer specializing in component-driven UI, state ownership, accessibility

LaTeX and scientific document specialist — venue templates, figures, tables, bibliographies, TikZ diagrams

ML/empirical experiment design specialist — pre-registration, Fisher-style design, reproducibility manifests

Scientific writing specialist for research papers — argument structure, claim-evidence chains, narrative arc

Proactively refactor code to comply with rules/coding-standards.md through behavior-preserving

DevOps engineer specializing in CI/CD, containerization, infrastructure-as-code, observability

Orchestrates parallel agent execution across worktrees — decomposes tasks, routes to specialists

Proactively design tests that verify contracts, audit flaky tests, and enforce CI integrity.

Proactively audit security when auth/crypto/billing/PII paths are touched, when dependencies change

Data scientist specializing in profile-first EDA, distribution-aware modeling, missingness classification