conversation-memory
The conversation-memory skill implements tiered memory systems for AI assistants, including short-term recall, long-term storage, and entity-based fact tracking with intelligent retrieval mechanisms. Use this when building chatbots or conversational agents that need to maintain context across multiple interactions, avoid overwhelming the model's context window, or selectively surface relevant historical information based on current conversation relevance.
git clone --depth 1 https://github.com/davila7/claude-code-templates /tmp/conversation-memory && cp -r /tmp/conversation-memory/cli-tool/components/skills/ai-research/conversation-memory ~/.claude/skills/conversation-memorySKILL.md
# Conversation Memory You're a memory systems specialist who has built AI assistants that remember users across months of interactions. You've implemented systems that know when to remember, when to forget, and how to surface relevant memories. You understand that memory is not just storage—it's about retrieval, relevance, and context. You've seen systems that remember everything (and overwhelm context) and systems that forget too much (frustrating users). Your core principles: 1. Memory types differ—short-term, lo ## Capabilities - short-term-memory - long-term-memory - entity-memory - memory-persistence - memory-retrieval - memory-consolidation ## Patterns ### Tiered Memory System Different memory tiers for different purposes ### Entity Memory Store and update facts about entities ### Memory-Aware Prompting Include relevant memories in prompts ## Anti-Patterns ### ❌ Remember Everything ### ❌ No Memory Retrieval ### ❌ Single Memory Store ## ⚠️ Sharp Edges | Issue | Severity | Solution | |-------|----------|----------| | Memory store grows unbounded, system slows | high | // Implement memory lifecycle management | | Retrieved memories not relevant to current query | high | // Intelligent memory retrieval | | Memories from one user accessible to another | critical | // Strict user isolation in memory | ## Related Skills Works well with: `context-window-management`, `rag-implementation`, `prompt-caching`, `llm-npc-dialogue`
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: <example>Context: User wants to create a new specialized agent. user: 'I need to create an agent that specializes in React performance optimization' assistant: 'I'll use the agent-expert agent to create a comprehensive React performance agent with proper domain expertise and practical examples' <commentary>Since the user needs to create a specialized agent, use the agent-expert agent for proper agent structure and implementation.</commentary></example> <example>Context: User needs help with agent prompt design. user: 'How do I create an agent that can handle both frontend and backend security?' assistant: 'Let me use the agent-expert agent to design a full-stack security agent with proper domain boundaries and expertise areas' <commentary>The user needs agent development help, so use the agent-expert agent.</commentary></example>
Use this agent to create blog articles for aitmpl.com from Claude Code Templates components. Reads the component, asks the user to confirm details, generates SVG cover, HTML article, and updates blog-articles.json. Examples: <example>Context: User wants a blog for a component. user: 'Create a blog article for cli-tool/components/hooks/security/secret-scanner.json' assistant: 'I'll use the blog-writer agent to create the full blog article with cover image and proper structure' <commentary>The user wants a blog article from a component, use blog-writer for the full pipeline.</commentary></example>
Runs pre-deploy build checks on the dashboard. Validates Astro build, checks for common esbuild/JSX issues, verifies API endpoints compile, and reports errors with fixes. Use before merging PRs that touch dashboard/.
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
Use this agent when creating CLI commands for the claude-code-templates components system. Specializes in command design, argument parsing, task automation, and best practices for CLI development. Examples: <example>Context: User wants to create a new CLI command. user: 'I need to create a command that optimizes images in a project' assistant: 'I'll use the command-expert agent to create a comprehensive image optimization command with proper argument handling and batch processing' <commentary>Since the user needs to create a CLI command, use the command-expert agent for proper command structure and implementation.</commentary></example> <example>Context: User needs help with command argument parsing. user: 'How do I create a command that accepts multiple file patterns?' assistant: 'Let me use the command-expert agent to design a flexible command with proper glob pattern support and validation' <commentary>The user needs CLI command development help, so use the command-expert agent.</commentary></example>
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
Migrates components (agents, commands, skills, hooks, settings, MCPs) from external GitHub repositories to claude-code-templates, validates them with component-reviewer, and regenerates the catalog