“memory plugin”的搜索结果

Context engineering: compaction, progressive disclosure, structured notes via AgentDB. Triggers: tokens, compaction, memory, handoff, summarize, context window.

中文简介正在准备中。当前显示原文说明。

Checkpoint durable decisions, fixes, constraints, results, and open next steps from the current Codex task into scoped Waggle project memory.

中文简介正在准备中。当前显示原文说明。

Inspect and safely edit the Claude Code and Codex configuration surfaces exposed by CCAM. Use when auditing skills, agents, commands, plugins, marketplaces, MCP servers, hooks, settings, memory, keybindings, profiles, rules, or instruction files, and when a backup-backed allowlisted edit is required.

中文简介正在准备中。当前显示原文说明。

Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/, manifests/, agent_memory/) and resolves project naming.

中文简介正在准备中。当前显示原文说明。

Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures, SSM agent, container runtime, kernel panics, pod networking. Read-only. Not for cluster-wide provisioning (→ hyperpod-cluster-debugger), NCCL (→ hyperpod-nccl), or MFU (→ hyperpod-mfu-debugger).

中文简介正在准备中。当前显示原文说明。

Diagnose NCCL failures and adjacent training-pod failures on HyperPod GPU clusters (EKS or Slurm) — training hangs, AllReduce / collective-op timeouts, EFA or libfabric errors, rendezvous failures, EFA TCP fallback, /dev/shm or memlock issues, NCCL version mismatch across pods, container OOM / exit-137 / OOMKilled, GPU OOM (CUDA out of memory), CrashLoopBackOff / Pending pods, MASTER_ADDR DNS, NetworkPolicy blocking. Not for single-node hardware faults (→ hyperpod-node-debugger § G) or cluster-creation EFA / SSM failures (→ hyperpod-cluster-debugger § A / § F).

中文简介正在准备中。当前显示原文说明。

WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WP_Query, analyzing caching strategies, checking code before launch, or detecting anti-patterns, or when user mentions "performance review", "optimization audit", "slow WordPress", "slow queries", "high-traffic", "scale WordPress", "code review", "timeout", "500 error", "out of memory", or "site won't load". Detects anti-patterns in database queries, hooks, object caching, AJAX, and template loading.

中文简介正在准备中。当前显示原文说明。

Garnish — Craft CMS's built-in JavaScript UI toolkit for the control panel. ALWAYS load when writing, editing, or reviewing JavaScript that runs in the Craft CP — plugin CP assets, custom field type JS, element index JS, CP webpack config, or code importing garnishjs / referencing window.Garnish. Also for CP accessibility, keyboard interactions, drag-sort, and CP JS memory issues.

中文简介正在准备中。当前显示原文说明。

Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI orchestration. Use when: the task directly matches context manager responsibilities within plugin agent-orchestration. Do not use when: a more specific framework or task-focused skill is clearly a better match.

中文简介正在准备中。当前显示原文说明。

Post a sitrep (situation report) for a live incident, in its incident channel: a short fixed-layout update for people who haven't read the whole channel — the current picture and what moved since the previous update. Use on "sitrep", "status update", "where are we", "what's the latest", "catch me up", "summarize the incident so far", when asked to keep posting on a schedule ("post a sitrep every hour until resolved"), or when the oncall memory sets an update cadence for this severity and the incident owner asks Claude to keep it. Reads the channel, alert thread and findings posted, re-reads the one key signal, and writes: status line, TL;DR, impact, what changed since the last sitrep, what's in progress and who has it, what's needed, when the next update comes, one chart. Facts come only from what people said or Claude read first-hand; cause and recovery time are never guessed. Fits one phone screen. Not investigation (`incident-investigate`) or the write-up afterwards (`incident-postmortem`).

中文简介正在准备中。当前显示原文说明。

Write the postmortem for an incident, in its incident channel, once it is mitigated or resolved. Use on "write up this incident", "postmortem", "incident summary", "what happened here for people who weren't around", "draft the retro", or when the oncall memory says incidents of this severity get one. Reads the incident channel (and the alert thread it came from), the investigation findings and the data behind them, and writes a one-screen, zero-context write-up: what happened, impact with numbers, detection, timeline with durations, why it happened, what fixed it, follow-ups with proposed owners, and one before/during/after chart. Posted and pinned in the incident channel as its final pinned post, with edit requests updating that one pinned post in place — unless the person or the team's conventions say write-ups live elsewhere, in which case it is written there and only a link is posted, nothing pinned. A person edits and publishes it; never assigns blame.

中文简介正在准备中。当前显示原文说明。

Use HarnessKit to inventory, audit, enable, disable, and deploy skills, MCP servers, plugins, hooks, CLIs, configs, memory, and rules across multiple coding agents.

中文简介正在准备中。当前显示原文说明。

Self-knowledge for stella, the self-hosted AI assistant. Use when users ask about configuration, setup, onboarding, providers, models, agents, channels, webhooks, memory, schedules, workflows, goals, workers, skills, plugins, session compaction, notifications, self-update, multi-user behavior, or how stella works. Also use for changing models, setting up channels or webhooks, configuring providers, updating stella, onboarding, switching agents, reporting bugs, and goal status or acceptance.

中文简介正在准备中。当前显示原文说明。

Use when configuring DMA channels, circular buffer mode, double buffering, memory-to-peripheral transfers, or DMA IRQ completion on bare-metal MCUs. Not for cache theory: use cpu-cache-opt.

中文简介正在准备中。当前显示原文说明。

Use when writing CUDA kernels, managing the thread, block, and grid hierarchy, tiling shared memory, using streams, setting nvcc flags, or using Thrust. Not for kernel debugging: use cuda-debugging.

中文简介正在准备中。当前显示原文说明。

Use when choosing kernel spinlocks versus mutexes, using RCU, seqlocks, completions, or memory barriers, or debugging scheduling-while-atomic. Not for userspace atomics: use concurrency-debugging.

中文简介正在准备中。当前显示原文说明。

Use when collecting sampling profiles with perf record, reading perf report or perf annotate, measuring PMU counters with perf stat -e, or using PAPI instrumentation to interpret IPC, miss rates, MPKI, or memory bandwidth on Linux. Not for SVG rendering: use flamegraphs.

中文简介正在准备中。当前显示原文说明。

Use when profiling with Intel VTune or AMD uProf for hotspots, top-down pipeline stalls, memory-bound analysis, or roofline data. Not for raw perf stat counters: use linux-perf.

中文简介正在准备中。当前显示原文说明。

Use when diagnosing cache misses with perf, fixing false sharing, choosing AoS or SoA layout, or adding software prefetch. Not for cache theory: use memory-hierarchy-and-caches.

中文简介正在准备中。当前显示原文说明。

Use when tuning or profiling native code on Apple M-series Macs: unified memory, 16 KiB pages, Accelerate and Metal for matrix work, xctrace and leaks, Rosetta 2, or sysctl hardware queries.

中文简介正在准备中。当前显示原文说明。

Use when the user requests memory transfer to or from a named peer. Not for recalling a session: use history-recall. Not for store registration: use history-source-registry.

中文简介正在准备中。当前显示原文说明。

Use when the user and agent may hold different pictures of current state after a gap, sync request, or exposed stale claim. Not for persistence: use memory-update.

中文简介正在准备中。当前显示原文说明。

Use when asked to mine prior chats on a scheduled or watcher tick and maintain project memory. Not for remote, credential, publish, deploy, or irreversible mutation.

中文简介正在准备中。当前显示原文说明。

Use when C or C++ code needs memory-safety or undefined-behavior guarantees proved with CBMC, or ACSL contracts checked with Frama-C Eva or WP. Not for choosing the proof policy: use proof-driven.

中文简介正在准备中。当前显示原文说明。