ai-runtime-memory
AI Runtime分层记忆系统,支持SQL风格的事件查询、时间线管理,以及记忆的智能固化和检索,用于项目历史追踪和经验传承
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- ai-runtime-memory
- license
- MIT
- version
- 1.0.0
- description
- AI Runtime分层记忆系统,支持SQL风格的事件查询、时间线管理,以及记忆的智能固化和检索,用于项目历史追踪和经验传承
02 资源文件 4
- 脚本memory_cli.py4.1 KB
- 脚本memory_discovery.py14.7 KB
- 参考文档README.md1.6 KB
- 参考文档skill-report.json75.7 KB
03 SKILL.md 正文
AI Runtime 记忆系统
概述
AI Runtime的记忆系统采用分层架构,模拟人类大脑的记忆机制,实现持续存在和认知主体性。系统分为三个层次,通过专门的工具支持SQL风格查询和智能管理。
核心功能
三层记忆架构
- 短期记忆: 当前会话上下文,7±2组块限制
- 长期记忆: 跨项目技术知识,结构化知识图谱
- 情景记忆: 项目历史事件,支持复杂时间线查询
查询能力
- SQL风格条件查询(WHERE/ORDER BY/LIMIT)
- 多格式输出(table/json)
- 时间范围和标签过滤
- 全文搜索支持
快速开始
基本查询
# 进入记忆系统目录
cd .ai-runtime/memory
# 查看今天的事件
python3 memory_cli.py query --where "date='$(date +%Y-%m-%d)'"
# 查看架构决策
python3 memory_cli.py query --where "tags CONTAINS 'architecture' AND type='decision'"
使用便捷脚本
# 查看今天的事件
./scripts/memory-query.sh today
# 查看本周统计
./scripts/memory-query.sh week
# 搜索关键词
./scripts/memory-query.sh search "认证"
渐进式披露文档架构
基于 anthropics/skills 设计,按需加载详细信息:
核心架构
- 系统架构详解 - 分层记忆系统设计和实现原理
使用指南
- 工具使用指南 - memory_cli.py 和 memory_discovery.py 详细用法
高级主题
- 维护指南 - 记忆固化、清理和质量保证
实践示例
- 使用示例 - 从基础查询到高级分析的完整示例
事件记录格式
YAML Front Matter
---
id: unique-event-id
type: event|decision|error|meeting
level: day
timestamp: "2025-11-14T10:30:00"
tags: [architecture, decision]
---
目录结构
episodic/
└── 2025/11/14/
└── event-description.md
编程接口
from memory_discovery import MemoryDiscovery
# 初始化
discovery = MemoryDiscovery('.ai-runtime/memory')
# 查询
events = discovery.query(
where="date>='2025-11-14' AND tags CONTAINS 'architecture'",
order_by="timestamp desc",
limit=20
)
# 格式化输出
output = discovery.format_events(events, format_type="table")
相关命令
/runtime.remember- 记录新记忆事件/runtime.think- 基于记忆进行思考/runtime.explore- 探索和分析记忆模式
维护建议
- 定期运行
./scripts/memory-query.sh stats检查系统状态 - 每周审查
./scripts/memory-query.sh week的活动记录 - 每月归档重要事件到 long-term 记忆层
基于 anthropics/skills 渐进式披露架构设计
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.