sdcorejs-memories

Write and load durable SDCoreJS cross-session memories for angular-portal, nestjs, and nextjs workflows.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-memories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdcorejs-memories
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-memories
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-memories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates repeated onboarding and forgotten conventions by making durable SDLC knowledge persist across coding sessions.

Core Features & Use Cases

  • Durable cross-session memory: Save lasting facts like conventions, stakeholder constraints, and recurring anti-patterns so future sessions treat them as authoritative.
  • Session start READ mode: Loads memory frontmatter first, then bodies on demand based on the current task match.
  • Explicit WRITE mode triggers: Writes or updates memories when users request it (e.g., “ghi nhớ”) or when the agent detects durable user corrections/constraints.
  • Track-aware routing: Applies to angular-portal, nestjs, and nextjs by storing per-track memory files under .sdcorejs/memories/<track>/.
  • Claude Code mirror (best-effort): When running inside Claude Code, copies the exact memory bytes into Claude’s local per-project memory directory for automatic surfacing.

Quick Start

Ask the agent to save a durable rule by saying “ghi nhớ: prefer anchor v2 for long detail pages with more than 6 fields.”

Frequently Asked Questions about sdcorejs-memories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist project conventions across Claude Code agent sessions?

To persist project conventions across Claude Code agent sessions, this Skill writes durable memories to a local project directory, loading frontmatter at session start and full content on demand. It also mirrors memory bytes directly into Claude Code's local per-project directory for automatic surfacing.

What is cross-session memory for agent workflows and when do I need it?

Cross-session memory for agent workflows is durable storage that saves lasting facts like stakeholder constraints and recurring anti-patterns. You need it when onboarding repeats across coding sessions and forgotten conventions cause future agents to disregard established project rules.

How do I save durable knowledge for NestJS or NextJS workflows during an agent run?

To save durable knowledge for NestJS or NextJS workflows, trigger a write by explicitly requesting it or making a durable correction. The agent stores per-track memory files under a dedicated memories directory, organizing knowledge by the specific workflow track.

Does this memory Skill require a Git repository to resolve project paths?

Yes, this memory Skill requires a Git repository to function correctly. It resolves the target project root using Git, which establishes the base directory path needed to read and write memory files within the project structure.

How does the agent handle duplicate topics when writing cross-session memories?

The agent handles duplicate topics by applying slug and index guidance during the memory write process. This duplicate detection mechanism ensures that recurring conventions are updated accurately rather than creating redundant memory files.

What are the limitations of using file-based memory for software development lifecycle knowledge?

Limitations of file-based SDLC memory include best-effort mirroring into Claude Code's directory, which is not guaranteed outside that environment. It also requires explicit user triggers or detected durable corrections to write, meaning transient session details are not captured automatically.