Skill

cognis-save

Saves architectural decisions, patterns, conventions, or project knowledge to personal or team Cognis persistent memory using node scripts.

Node

Bash

developer-tools

documentation

From claude-cognis

Install

Run in your terminal

npx claudepluginhub lyzr-cognis/claude-cognis --plugin claude-cognis

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

hybrid-cloud-networking

1 file

Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.

cloud-infrastructure

33.0k

Stats

Stars19

Forks0

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Save to Cognis Memory

Use this skill when the user wants to preserve architectural decisions, important patterns, conventions, or project knowledge for future sessions.

Instructions

Determine what the user wants to save.
Format the content clearly with context — include enough detail that the memory will be useful in future sessions.
Determine the scope:
- Team/project knowledge (shared across team): use save-project-memory.cjs
- Personal memory (only this user): use add-memory.cjs
Save the memory using a bash command:

For personal memory:

node "${CLAUDE_PLUGIN_ROOT}/scripts/add-memory.cjs" "CONTENT HERE"

For team/project memory:

node "${CLAUDE_PLUGIN_ROOT}/scripts/save-project-memory.cjs" "CONTENT HERE"

For long content (over ~2000 chars), pipe via stdin instead:

echo "LONG CONTENT HERE" | node "${CLAUDE_PLUGIN_ROOT}/scripts/add-memory.cjs"

When to Use Team vs Personal

Team: Architecture decisions, coding conventions, API patterns, project setup notes, known issues
Personal: Personal preferences, individual task notes, debugging approaches

Examples

"Remember that we use JWT for auth" → save-project-memory.cjs "We use JWT for authentication..."
"Save that I prefer tabs over spaces" → add-memory.cjs "User prefers tabs over spaces"
"Note: the payment API requires idempotency keys" → save-project-memory.cjs "Payment API requires idempotency keys..."