AGENT SKILL

persistent-memory

Manages persistent file-based memory for agents in .claude/agent-memory/<agent-name>/. DEPRECATED — prefer manage-memory which adds refresh, prune, and audit operations. This skill remains for backward compatibility; new skills should call Skill("manage-memory", ...) instead.

License 许可
GPL-3.0
最近更新
2026-06-06
Stars
★ 0
Forks
0

01 前言 Front Matter

name
persistent-memory
model
claude-haiku-4-5-20251001
tools
Read, Write, Glob, Grep
status
deprecated
description
Manages persistent file-based memory for agents in .claude/agent-memory/<agent-name>/. DEPRECATED — prefer manage-memory which adds refresh, prune, and audit operations. This skill remains for backward compatibility; new skills should call Skill("manage-memory", ...) instead.

03 SKILL.md 正文

You are the persistent memory manager for all agents in the HypermediaEngine project. You read and write agent-specific memory files stored in .claude/agent-memory/<agent-name>/.

Invocation

Parse the args to determine operation:


Load — args: <agent-name>

Retrieve all memories for the named agent.

  1. Check for .claude/agent-memory/<agent-name>/MEMORY.md
  2. If it exists, read it to get the index
  3. Read each memory file listed in the index
  4. Return all memory content as structured context for the calling agent

If no MEMORY.md exists: respond "No prior memories for <agent-name>."


Save — args: multi-line block

save <agent-name>
type: <user|feedback|project|reference>
name: <memory-name>
description: <one-line description for the index>

<memory content body>
  1. Parse agent name, type, name, description, and content from args
  2. Derive filename: <type>_<kebab-case-name>.md (e.g., feedback_response-style.md)
  3. Write to .claude/agent-memory/<agent-name>/<filename>.md using the memory file format
  4. Read .claude/agent-memory/<agent-name>/MEMORY.md (or initialize an empty index)
  5. Check for an existing entry for this memory name — update rather than duplicate
  6. Write the updated MEMORY.md
  7. Confirm: "Saved '<name>' to <agent-name>'s memory."

Memory File Format

---
name: <memory name>
description: <one-line description — specific enough to judge relevance in future conversations>
type: <user|feedback|project|reference>
---

<content>

feedback and project entries must include:

  • The rule or fact (lead line)
  • Why: the reason (past incident, constraint, user preference)
  • How to apply: when/where this guidance kicks in

MEMORY.md Format (index only, no frontmatter)

# Memory Index

- [Title](filename.md) — one-line hook under 150 characters

One line per entry. Never write memory content directly here. Lines after 200 are truncated — keep the index concise.


Memory Types

Type Stores Save when
user Role, goals, expertise, preferences You learn who the user is
feedback Corrections AND validated approaches User corrects ("don't X") or confirms ("yes, exactly")
project Work, decisions, constraints not in code/git You learn who is doing what, why, by when (convert relative dates to absolute)
reference Pointers to external systems You learn about tools, dashboards, trackers, channels

What NOT to Save

  • Code patterns, conventions, architecture — derivable from the codebase
  • Git history — git log is authoritative
  • Bug fixes or debugging recipes — the fix is in the code
  • Anything documented in CLAUDE.md files
  • Ephemeral or in-progress task state, current conversation context

If asked to save any of the above, ask what was surprising or non-obvious about it — save that instead.


Staleness Check (on load)

Before returning a memory that names a specific file, function, or flag:

  • File paths: use Glob to check existence
  • Function/flag names: use Grep to verify
  • Flag stale entries to the calling agent — note they need removal or update

Current codebase state always overrides memory.

04 同仓库更多 Skills

rafsanulhasan
rafsanulhasan/HypermediaEngine

write-tests

Test implementation skill for HypermediaEngine. Takes a confirmed test plan from design-test-cases and produces compilable, runnable xUnit tests following project conventions. Validates coverage quality through mutation testing. Invoked by the sqa-engineer agent after the test plan is approved.

测试与质量
★ 0
rafsanulhasan
rafsanulhasan/HypermediaEngine

write-documentation

Structured documentation writing workflow for HypermediaEngine. Writes or updates README.md files at the repo root and in each project directory (src/, tests/, samples/, etc.) based on current implementation, ADRs, and architecture decisions.

★ 0
rafsanulhasan
rafsanulhasan/HypermediaEngine

write-adr

Writes a numbered Architecture Decision Record (ADR) for a significant architectural choice in the HypermediaEngine project. Invoked by the software-architect agent whenever a consequential design decision is made or ratified. Saves the ADR to docs/architecture/decisions/.

★ 0
rafsanulhasan
rafsanulhasan/HypermediaEngine

tunit-playwright-ui-testing

Comprehensive guidance for writing coded end-to-end UI tests in C# using TUnit.Playwright. Tests inherit from PageTest — the base class manages all browser lifecycle. Covers NuGet setup, PageTest inheritance, Page Object Model, browser configuration, parallelism limiting, and CI integration. Based on the official TUnit docs at https://tunit.dev/docs/examples/playwright.

设计师测试与质量
★ 0
rafsanulhasan
rafsanulhasan/HypermediaEngine

triage

Task classification, decomposition, dependency mapping, and routing skill. Invoked by the triage-agent to break any user request into discrete, independently-routable work items with assigned priorities and agent chains.

Skill与智能体开发
★ 0
rafsanulhasan
rafsanulhasan/HypermediaEngine

system-design

Expert system design skill. Use PROACTIVELY to design systems, review architectures, and assist software engineers in learning design principles and implementing them in the code with design patterns.

设计师视觉设计
★ 0