원클릭으로 Manus에서 모든 스킬 실행

memory-hygiene

스타6

포크20

업데이트2026년 7월 12일 15:02

Audit and maintain the Claude auto-memory store (MEMORY.md index + single-fact *.md files under ~/.claude/projects/C--GitHub-shidler/memory/). Use periodically, before a /compact, after a session that wrote new memories, or when MEMORY.md grows past ~25 entries. Runs validate_memory.py to find broken index links (errors), dangling [[name]] cross-refs and orphan files (warnings), and missing frontmatter. Auto-activates on `/memory-hygiene`.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

adamwstauffer

adamwstauffer/shidler

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Memory Hygiene Skill

Keeps this project's Claude memory store coherent as it grows. The store is the external per-project memory dir — MEMORY.md (the index loaded each session) plus the single-fact *.md files under C:/Users/adamw/.claude/projects/C--GitHub-shidler/memory/. It is not a repo directory; the validator lives in the repo and operates on it.

When to invoke

Periodically (every ~10 sessions) or when MEMORY.md passes ~25 index lines.
Before a /compact — a clean index survives summarization better.
After a session wrote memories — confirm new entries are indexed and cross-refs resolve.
When you notice drift — a [[link]] that 404s, an entry describing a deleted/moved file.

Step 1 — run the validator

python .claude/skills/memory-hygiene/validate_memory.py \
  --memory-dir "$HOME/.claude/projects/C--GitHub-shidler/memory"
# add --strict to exit non-zero on warnings; --json for a machine-readable report

On Windows PowerShell:

python .claude/skills/memory-hygiene/validate_memory.py `
  --memory-dir "$env:USERPROFILE\.claude\projects\C--GitHub-shidler\memory"

Step 2 — triage findings

Finding	Severity	Fix
`MEMORY.md links to missing file: X`	ERROR	The index points at a deleted/renamed file. Update or remove the index line.
`missing required frontmatter key 'name'`	ERROR	Add a `name:` slug to the file's frontmatter.
`dangling [[slug]]`	warning	Either a typo (usually a missing `feedback_`/`project_` prefix — fix it) or a deliberate forward-ref to a memory not yet written (leave it). If it points at a decision memo / spec, that's a misuse of `[[ ]]` — convert to a plain path reference.
`not referenced in MEMORY.md (orphan)`	warning	Add a one-line index pointer, or delete if the fact is obsolete/wrong.
`missing description` / `missing type`	warning	Backfill the frontmatter opportunistically when you touch the file.

A [[name]] that doesn't resolve is not automatically a bug — the memory convention allows forward-refs. Only fix the ones that are typos (wrong/missing prefix) or mis-targeted (pointing at a non-memory doc).

Step 3 — organize (optional, when the index is crowded)

If MEMORY.md is past ~25 lines, group by type so recall stays cheap: keep the feedback_* (grading/house rules) together and the project_* (ongoing work) together. Don't rewrite content — this is index organization, not fact editing. Delete memories that turn out to be wrong (per the memory rules) rather than letting them accumulate.

Guardrails

Never put fact content in MEMORY.md — it's an index; one line per memory, no frontmatter, pointer only.
One fact per file — if a fact file has grown to cover two things, that's a split candidate, not a hygiene error.
Don't store what the repo already records — code structure, past fixes, git history, CLAUDE.md content. If you find such a memory, flag it for deletion.

이 저장소의 다른 Skills

같은 저장소

breakpoint

adamwstauffer/shidler

Emit a structured "pickup prompt" before a context break so work survives compaction or a new session. Auto-activates when running `/breakpoint`, when the user says "pickup prompt", "breakpoint", "hand off", "checkpoint this", or is about to run `/compact` or `/clear` mid-task. Reads git, open/merged PRs, branch/worktree state, the task list, and in-flight decision memos + grading passes, then writes a copy-paste-ready resume block to the conversation AND persists it to a dated file. CLAUDE.md prose alone gets skipped under load — this makes the handoff mechanical.

2026-07-126

claude-md-audit

adamwstauffer/shidler

Audit CLAUDE.md and the memory store (MEMORY.md + fact files) for drift — stale path citations, cross-file contradictions, duplicated facts, and bloat. Use periodically (monthly, or after a big restructure), not on every change. Read-only by default; reports findings by severity with file:line + suggested fix, and routes anything not fixed this session to a follow-up note. Auto-activates on `/claude-md-audit`.

2026-07-126

design-critique

adamwstauffer/shidler

Brand-anchored critique of UH Mānoa-branded materials (HTML pages, slide decks, PDFs, branded Markdown) against the design tokens in docs/_branding/design.json and the brand-guidelines skill. Flags off-brand and generic "AI-slop" patterns, scores on UH-anchored dimensions, and emits a prioritized fix list. Advisory only — does not apply fixes. Auto-activates on `/design-critique`.

2026-07-126

grill-me

adamwstauffer/shidler

Use when the user types "/grill-me", says "grill me", "stress-test this", or "interrogate the plan" — a sequential, one-question-at-a-time interrogation that converges decisions BEFORE they calcify in a decision memo, a course/stage restructure, a rubric, or a template. Augments (does not replace) brainstorming: brainstorming expands the option space, grill-me converges it. Includes a mandatory Auto-Pushback Pass and a Repo Convergence Check that enforces this repo's "no speculative restructuring" principle.

2026-07-126

brand-guidelines

adamwstauffer/shidler

Applies University of Hawaiʻi at Mānoa official brand colors, typography, and design standards to any artifact that benefits from UH Mānoa's institutional look-and-feel. Use when brand colors or style guidelines, visual formatting, document styling, presentation design, or university design standards apply. Also use when creating materials for Shidler College of Business courses.

2026-02-196

docx

adamwstauffer/shidler

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

2026-02-156

name	memory-hygiene
description	Audit and maintain the Claude auto-memory store (MEMORY.md index + single-fact *.md files under ~/.claude/projects/C--GitHub-shidler/memory/). Use periodically, before a /compact, after a session that wrote new memories, or when MEMORY.md grows past ~25 entries. Runs validate_memory.py to find broken index links (errors), dangling [[name]] cross-refs and orphan files (warnings), and missing frontmatter. Auto-activates on `/memory-hygiene`.
tools	["Bash","Read","Edit","Write","Grep","Glob"]

Memory Hygiene Skill

When to invoke

Periodically (every ~10 sessions) or when MEMORY.md passes ~25 index lines.
Before a /compact — a clean index survives summarization better.
After a session wrote memories — confirm new entries are indexed and cross-refs resolve.
When you notice drift — a [[link]] that 404s, an entry describing a deleted/moved file.

Step 1 — run the validator

python .claude/skills/memory-hygiene/validate_memory.py \
  --memory-dir "$HOME/.claude/projects/C--GitHub-shidler/memory"
# add --strict to exit non-zero on warnings; --json for a machine-readable report

On Windows PowerShell:

python .claude/skills/memory-hygiene/validate_memory.py `
  --memory-dir "$env:USERPROFILE\.claude\projects\C--GitHub-shidler\memory"

Step 2 — triage findings

Finding	Severity	Fix
`MEMORY.md links to missing file: X`	ERROR	The index points at a deleted/renamed file. Update or remove the index line.
`missing required frontmatter key 'name'`	ERROR	Add a `name:` slug to the file's frontmatter.
`dangling [[slug]]`	warning	Either a typo (usually a missing `feedback_`/`project_` prefix — fix it) or a deliberate forward-ref to a memory not yet written (leave it). If it points at a decision memo / spec, that's a misuse of `[[ ]]` — convert to a plain path reference.
`not referenced in MEMORY.md (orphan)`	warning	Add a one-line index pointer, or delete if the fact is obsolete/wrong.
`missing description` / `missing type`	warning	Backfill the frontmatter opportunistically when you touch the file.

Step 3 — organize (optional, when the index is crowded)

Guardrails

Never put fact content in MEMORY.md — it's an index; one line per memory, no frontmatter, pointer only.
One fact per file — if a fact file has grown to cover two things, that's a split candidate, not a hygiene error.
Don't store what the repo already records — code structure, past fixes, git history, CLAUDE.md content. If you find such a memory, flag it for deletion.