cipher-memory

Format memory content for Cipher cross-IDE persistence with a projectPath.

1|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/abdullah1854/ClaudeSuperSkills --skill cipher-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cipher-memory
Source: https://github.com/abdullah1854/ClaudeSuperSkills/tree/main/cipher-memory
Command: npx skills add https://github.com/abdullah1854/ClaudeSuperSkills --skill cipher-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Formats messages for cross-IDE memory persistence with project-scoped context.

Core Features & Use Cases

  • Memory Semantics: Recall, decision, learning, milestone, blocker.
  • Project-Scoped: Keeps memory within a given project path.

Quick Start

Store a decision for a given project path and recall later.

Frequently Asked Questions about cipher-memory

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

FAQPage Schema
How do I persist project memory across different IDEs?

Cross-IDE memory persistence formats and stores project-scoped content through Cipher, enabling you to recall decisions, learnings, and milestones consistently regardless of which IDE you're using. The Skill applies proper projectPath context to each memory operation so information stays tied to your specific project.

What memory semantics does cross-IDE persistence support?

Cross-IDE memory persistence supports five semantic types: recall (retrieve stored information), decision (log choices made), learning (capture insights), milestone (mark progress), and blocker (note obstacles). Each generates action-specific formatted messages for consistent project-scoped storage and retrieval.

How do I store and recall project decisions for later reference?

Format your decision content with the target projectPath, and the Skill generates a Cipher MCP call payload that stores it under project scope. Later, use the recall semantic to retrieve that decision from the same projectPath, keeping all project context isolated and queryable.

Can I use project memory persistence with my existing IDE workflows?

Yes, project memory persistence works across IDEs by routing all memory operations through Cipher's cross-IDE layer. As long as your environment supports Cipher MCP calls and you provide consistent projectPath identifiers, memory remains synchronized and accessible from any IDE.

What happens if I don't specify a projectPath for memory operations?

ProjectPath is required for project-scoped memory operations. Without it, the Skill cannot generate a valid Cipher MCP call payload, and your memory content won't be correctly isolated or retrievable. Always provide the target projectPath when invoking recall, decision, learning, milestone, or blocker actions.

Is cross-IDE memory persistence suitable for team projects?

Cross-IDE memory persistence maintains individual project-scoped memory through Cipher. While designed for project-level context, team coordination depends on whether your Cipher backend supports shared projectPath access and collaborative memory semantics across team members.