memory-md

Included with Lifetime

$97 forever

Maintains concise repository MEMORY.md notes for gotchas, stale memory corrections, and durable user preferences. Use at the start of repository conversations, when the user mentions MEMORY.md, when an error should be remembered to avoid repeating it, or when MEMORY.md content may be wrong.

Writing & Docs

What this skill does

# MEMORY.md

Use `MEMORY.md` as a concise repository-local memory file. It is not automatically loaded, so check for it explicitly at the start of repository conversations and whenever prior project context may matter.

## When To Read

- At the start of a repository conversation, check whether `MEMORY.md` exists and skim it for relevant context before planning or editing.
- Check it again before non-trivial debugging, design work, workflow changes, or skill maintenance where past project choices may affect the answer.
- Treat a missing `MEMORY.md` as normal. Do not invent entries or assume the file exists.
- Use current repository evidence as the source of truth when memory and files disagree.

## When To Update

- Add or revise an entry after a mistake, discovery, or user preference when it will help avoid repeating the same issue.
- If an existing `MEMORY.md` entry is wrong, stale, or contradicted by current evidence, correct that entry instead of adding a conflicting note.
- Keep entries short, reusable, and grounded in the current repo.
- Never store secrets or sensitive data in `MEMORY.md`, including credentials, tokens, API keys, cookies, private endpoints, proprietary/internal-only details, or sensitive personal data.
- When a gotcha or preference involves sensitive material, record only the sanitized lesson, not the secret or identifying detail.
- Do not add task logs, transient status, broad summaries, or speculative plans.

## Required Shape

- Keep exactly these top-level sections: `## GOTCHA` and `## TASTE`.
- Use `## GOTCHA` for traps, failure modes, commands that behave unexpectedly, and verified recovery steps.
- Use `## TASTE` for durable project or user preferences that shape future edits.
- Prefer one concise bullet per entry. If a similar entry already exists, revise it instead of adding a duplicate.

## Entry Pattern

For gotchas, capture the failure and the fix:

```markdown
- Symptom: <what went wrong>. Cause: <why>. Fix: <specific future action>.
```

For taste, capture the preference and its practical effect:

```markdown
- Prefer <choice> when <context>; avoid <alternative> because <reason>.
```

## Examples

- `GOTCHA`: command failed because a tool needed `UV_CACHE_DIR=/tmp/uv-cache`; record the symptom, cause, and future command pattern.
- `TASTE`: the user prefers thin skills with only `SKILL.md` unless supporting files solve a concrete problem.
- Do not record: "finished PR #12" or "ran tests today." Those are task logs, not reusable memory.

Files: 2

Size: 3.1 KB

Complexity: 9/100

Category: Writing & Docs

Source: https://github.com/narumiruna/agent-skills/tree/main/skills/memory-md

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts