'persistent memory' 검색 결과

Weekly-cadence engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. NOT for per-session or per-task reflection (see mk:memory / Phase 6 Reflect).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sync reusable frontend decisions into persistent project documentation after UI work. Use when frontend changes introduce or modify component APIs, variants, design-system tokens, styling conventions, layout behavior, accessibility rules, interaction patterns, responsive behavior, or agent operating instructions; when the user asks to reflect decisions in components.md, design system docs, AGENTS.md, CLAUDE.md, GEMINI.md, or similar project memory files; or before finalizing frontend work where future consistency depends on decisions made during implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sistemas de memória persistente para conversas com LLM, incluindo memória de curto prazo, longo prazo e baseada em entidades. Use quando: memória de conversa, lembrar, persistência de memória, memória de longo prazo, histórico de chat.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Um sistema híbrido de memória que oferece gerenciamento de conhecimento persistente e pesquisável para agentes de IA (Arquitetura, Padrões, Decisões).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when logging, scoring, and triaging a learner's persistent weak areas to drive intervention selection.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Search rad-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work like Manus: Use persistent markdown files as your "working memory on disk."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Safety-case design for always-on agents with episodic memory. Covers data hygiene, privacy and security risk surfaces, cost controls, scope, user dependency concerns, retention, incident containment, and responsible deployment evidence. It identifies hazards and asks for named controls, tests, owners, and residual uncertainty; it does not provide legal, clinical, youth-safety, or jurisdictional determinations. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.