memory-reference
Claude Code memory (CLAUDE.md) configuration reference. Use when setting up project memory, understanding memory hierarchy, or configuring persistent instructions.
What this skill does
# Claude Code Memory Reference
Memory files (CLAUDE.md) provide persistent instructions that Claude loads every session.
## Memory Hierarchy (Priority Order)
| Priority | Location | Purpose | Shared With |
|----------|----------|---------|-------------|
| 1 (highest) | Enterprise policy | Organization rules | All users |
| 2 | `./CLAUDE.md` | Project instructions | Team via git |
| 3 | `./.claude/CLAUDE.md` | Alternative project location | Team via git |
| 4 | `./.claude/rules/*.md` | Modular project rules | Team via git |
| 5 | `~/.claude/CLAUDE.md` | Personal preferences | Just you |
| 6 | `./CLAUDE.local.md` | Personal project prefs | Just you (gitignored) |
## File Locations
```
/Library/Application Support/ClaudeCode/CLAUDE.md # Enterprise (macOS)
./CLAUDE.md # Project root
./.claude/CLAUDE.md # Alternative project
./.claude/rules/*.md # Modular rules
~/.claude/CLAUDE.md # User global
~/.claude/rules/*.md # User modular rules
./CLAUDE.local.md # Project personal
```
## Basic CLAUDE.md
```markdown
# Project Instructions
## Code Style
- Use TypeScript for all new files
- Prefer functional components in React
- Use ESLint and Prettier for formatting
## Commands
- Build: `npm run build`
- Test: `npm test`
- Lint: `npm run lint`
## Architecture
- Components in `src/components/`
- API routes in `src/api/`
- Types in `src/types/`
```
## Importing Files
Use `@path/to/file` to import other files:
```markdown
# Project Memory
See @README.md for project overview.
See @package.json for available commands.
## Team Guidelines
@docs/guidelines.md
## Personal Preferences
@~/.claude/my-prefs.md
```
Import rules:
- Relative and absolute paths allowed
- Max depth: 5 hops
- Not evaluated in code blocks
## Modular Rules (.claude/rules/)
Organize rules by topic:
```
.claude/rules/
├── code-style.md
├── testing.md
├── security.md
└── api-design.md
```
### Path-Specific Rules
Use frontmatter to scope rules:
```markdown
---
paths: src/api/**/*.ts
---
# API Development Rules
- All endpoints must validate input
- Use consistent error response format
- Document with OpenAPI comments
```
### Glob Patterns
| Pattern | Matches |
|---------|---------|
| `**/*.ts` | All TypeScript files |
| `src/**/*` | All files under src/ |
| `*.md` | Markdown in root |
| `src/components/*.tsx` | React components |
| `src/**/*.{ts,tsx}` | TS and TSX in src/ |
## Memory Commands
| Command | Description |
|---------|-------------|
| `/memory` | View/edit memory files |
| `/init` | Bootstrap CLAUDE.md |
| `/memory user` | Edit user memory |
| `/memory project` | Edit project memory |
## Best Practices
### Be Specific
```markdown
# Good
- Use 2-space indentation
- Name React components with PascalCase
# Bad
- Format code properly
- Use good naming
```
### Use Structure
```markdown
# Build Commands
- `npm run build` - Production build
- `npm run dev` - Development server
# Test Commands
- `npm test` - Run all tests
- `npm test:watch` - Watch mode
```
### Keep Updated
Review and update memory as project evolves.
## Example: Full Project Memory
```markdown
# MyApp Project
## Overview
React + TypeScript web application with Express backend.
## Quick Commands
- Dev: `npm run dev`
- Test: `npm test`
- Build: `npm run build`
- Deploy: `npm run deploy`
## Code Style
- TypeScript strict mode
- Functional React components
- CSS Modules for styling
- Jest for testing
## Architecture
- `src/client/` - React frontend
- `src/server/` - Express backend
- `src/shared/` - Shared types
## Common Patterns
- Use `useQuery` for API calls
- Validate props with Zod schemas
- Log errors to Sentry
## Git Workflow
- Feature branches from `main`
- Squash merge PRs
- Conventional commit messages
```
## Symlinks
Share rules across projects:
```bash
# Symlink shared rules
ln -s ~/shared-rules .claude/rules/shared
# Symlink specific file
ln -s ~/company-security.md .claude/rules/security.md
```
Symlinks are followed during loading.
## Debugging
```bash
# View loaded memory
/memory
# Check what files are loaded
# Memory command shows all active files
```
---
For complete documentation, see:
- [memory-full.md](memory-full.md) - Complete memory reference
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.