writing-memories
Writes or updates memory files with proper YAML frontmatter in the agent's memories directory. Use when saving new project learnings or updating existing memory files.
When & Why to Use This Skill
This Claude skill enables agents to maintain persistent project knowledge by creating and updating structured memory files with standardized YAML frontmatter. It optimizes long-term context retention, allowing the agent to store, organize, and recall critical project learnings, architectural decisions, and operational workflows, effectively solving the challenge of context loss in long-term development cycles.
Use Cases
- Case 1: Documenting project-specific architectural patterns and tech stack details to ensure consistency across multiple coding sessions.
- Case 2: Recording 'lessons learned' and specific edge-case solutions after resolving complex bugs to prevent future regressions.
- Case 3: Consolidating fragmented project notes into concise, structured memory files to optimize the agent's context window and improve information retrieval speed.
- Case 4: Maintaining a persistent record of frequently used repository commands, environment variables, and deployment sequences for streamlined DevOps tasks.
| name | writing-memories |
|---|---|
| description | Writes or updates memory files with proper YAML frontmatter in the agent's memories directory. Use when saving new project learnings or updating existing memory files. |
- Write to `./.{AGENT_NAME}/skills/memories//SKILL.md`.
- Create the directory if needed.
- Prepend the required header if missing.
- Path: `./.{AGENT_NAME}/skills/memories//SKILL.md`
- The `` is the memory name using hyphens (e.g., `project-overview`, `suggested-commands`)
- The file must be named `SKILL.md` (uppercase)
- The header uses YAML frontmatter (between `---` delimiters)
- **Required fields:**
- `name` - the memory name (must match the folder name)
- `description` - brief description of what this memory contains and when to use it
- The `description` field must NOT contain colons (`:`) after the initial one
- Good: `description: Brief summary of project structure`
- Bad: `description: Project structure: components and layout`
- Keep the description on a single line
- Do NOT add extra fields like `type` or `mutable` - only `name` and `description` are required
Every `SKILL.md` file **must** have this exact header format:
```
---
name:
description:
---
```
- Existing memory? Update if the info is the same topic; otherwise create a new file.
- Multiple small notes? Consolidate into one concise memory. If you see more than 10 memories it is a good idea to consolidate them into 5 memories.
- Concise and actionable
- No duplication with other memories
- Sources or file paths included when relevant
- Missing description: add a short, specific summary.
- Wrong path: keep memories under `./.{AGENT_NAME}/skills/memories/`.
Example:
---
name: project-overview
description: Skillrena repo purpose and structure
---