kortix-memory

Store durable project knowledge in version-controlled markdown files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill kortix-memory-jbreel77888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kortix-memory
Source: https://github.com/jbreel77888/Agent-AiNorx/tree/main/.kortix/opencode/skills/kortix-memory
Command: npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill kortix-memory-jbreel77888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the problem of lost project context and duplicated work across AI agent sessions by providing a structured, version-controlled system for storing and curating durable project knowledge that is accessible to all team sessions.

Core Features & Use Cases

  • Structured Memory Organization: Uses a clear index file and topic-specific markdown files for overview, integrations, conventions, and decisions to keep knowledge organized and easy to locate.
  • Relevance Rubric: Includes a defined set of rules for what knowledge to keep and what to discard, ensuring the memory stays up-to-date and free of irrelevant or transient information.
  • Standardized Update Workflow: Enforces a change request process for all memory edits, so all changes are reviewed, versioned, and safely merged to the main branch.
  • Use Case: For a team building a SaaS product, use this Skill to record architectural decisions like "we use Supabase for user authentication" and integration details like "our Stripe webhook endpoint is /api/webhooks/stripe" so new agents never have to re-derive this information from scratch.

Quick Start

Use the kortix-memory skill to document the team's decision to use PostgreSQL for all user data storage in the project's memory.

Frequently Asked Questions about kortix-memory

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

FAQPage Schema
How do I keep project context persistent across AI agent sessions?

You can store durable project knowledge like architectural decisions and integration details in structured, version-controlled markdown files so new agents access vetted context without re-deriving it.

What is the best way to manage coding conventions and architectural decisions for AI agents?

Managing coding conventions and architectural decisions for AI agents requires a shared knowledge base with a relevance rubric that filters out transient information and keeps only durable, vetted project context.

How do I safely update shared project memory without losing previous context?

You update shared project memory safely by enforcing a standardized change request workflow where all edits are reviewed, versioned, and safely merged to the main branch.

Can I use a rubric-governed memory system for SaaS integration details and operational runbooks?

Yes, a rubric-governed memory system supports storing SaaS integration details and operational runbooks by keeping knowledge organized in topic-specific markdown files accessible to all team sessions.

What should I exclude from project memory to avoid storing irrelevant agent context?

You should exclude transient, sensitive, or non-durable information from project memory to ensure the knowledge base remains up-to-date and free of irrelevant data.