Results for “mem”

Persists project context across Claude Code sessions. Auto-loads project summaries on startup, tracks session progress, and saves structured state via deterministic Node.js scripts.

Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary, with per-group history, user profiles, and privacy guardrails.

Diagnose whether an AI workflow suffers from context stuffing or benefits from context engineering, and apply structured techniques to improve reliability.

Compresses conversation transcripts into prioritized notes using an LLM observer, consolidates them when they grow, and recovers any missed sessions without a database or vector store.

Helps users decide whether Vipshop is the best place for branded discount buying, then assists with browser automation for flash sales, inventory checks, cart operations, and member benefits.

Manages a long-term Markdown knowledge base for software projects, capturing architecture, decisions, and conventions in `.lore/` with commands to init, sync, query, audit, compress, and mirror to platform files.

Defines an inter-agent communication protocol for C-suite agent teams, including invocation syntax, loop prevention, isolation rules, and response formats to coordinate cross-functional analysis and board meetings.

Load bounded working context at the start of a coding session. FIRES ON EVERY FIRST USER MESSAGE in a fresh session, regardless of content — including bare greetings ("hi", "hello", "hey"), task-only openers, or "let's start". Also triggers on: "fresh session", "session start", "first message in a new thread", "new chat", "cold start", "begin work in this repo", "starting work", "continue from prior session", "what were we working on", "resume", "what happened last time", "load memory", "recall context", "create a handoff", "prior session context", "latest handoff", "current state", "decision context". Skip ONLY if the user explicitly says "fresh start" or "ignore prior context". Self no-ops if invoked mid-session when context is already loaded.

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.

Sets up a codebase for reliable agent-driven development by making it legible (structured docs, custom lints, code graph), executable (one-command dev stack, cloud sandbox), and verifiable (e2e gate, verify-before-ship loop).

Dolt-powered issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction. Trigger with "create task", "what's ready", "track this work", "resume after compaction". Make sure to use this skill whenever managing multi-session work, tracking dependencies, or recovering context.