菜单
Persistent cross-session memory for AI coding agents. Use when working across multiple sessions, recalling past context, saving decisions, or searching historical observations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | agentmemory |
| description | Persistent cross-session memory for AI coding agents. Use when working across multiple sessions, recalling past context, saving decisions, or searching historical observations. |
Provides persistent memory capabilities for coding agents using the agentmemory MCP server.
Save an insight, decision, or fact to long-term memory.
memory_save(
content: "We chose jose over jsonwebtoken for Edge Runtime compatibility",
concepts: ["jwt-auth", "edge-runtime", "jose-library", "auth-middleware"],
files: ["src/middleware/auth.ts"],
type: "architecture"
)
Search past observations by exact keywords.
memory_recall(query: "jwt auth setup", limit: 5)
Hybrid semantic+keyword search. Use for fuzzy or conceptual queries.
memory_smart_search(query: "how did we handle database performance", limit: 10)
List recent sessions with status and observation counts.
memory_sessions(limit: 10)
Get past observations about specific files across all sessions. Call before editing a file.
memory_file_history(files: ["src/middleware/auth.ts"])
Save and retrieve lessons learned with confidence scoring.
memory_lesson_save(
content: "Always validate JWT expiry before decoding payload",
concepts: ["jwt-validation", "security"],
domain: "backend"
)
memory_lesson_recall(query: "jwt security", limit: 5)
Delete specific memories. Requires explicit user confirmation.
Detect recurring patterns across sessions.
Run the 4-tier memory consolidation pipeline.
memory_sessions when the user asks about project history or past work.memory_file_history before editing files to surface past issues or decisions about that file.agentmemory_memory_ prefix in the tool list. Use the exact names as listed.http://localhost:3111 by defaulthttp://localhost:3113npx @agentmemory/agentmemoryExecute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.
Production dashboard UI patterns for Flutter: animation tokens system with spring physics and page transitions, glassmorphism cards with staggered entrance, gradient stat cards with animated counters, shimmer loading skeletons, error state with shake animation, empty state with animated entrance, consistent section headers, status badges, store selector with bottom sheet, multi-tenant store selection with persistence, schema-based feature visibility, state provider integration with Riverpod, and responsive metric card layouts.
Multi-microservice Dio networking patterns for Flutter: cookie-based session auth with cookie_jar, shared PersistCookieJar across multiple Dio instances, Bearer token fallback, AuthInterceptor with 401 detection on both onResponse and onError, static cross-cutting logout callback, ApiService thin typed wrapper with response envelope validation, dual-format envelope parser (status/success), cursor-based pagination, and dual-layer error hierarchy (Exception + Failure). Designed for production Flutter apps connecting to multiple backend microservices.
Complete Flutter state management and architecture skill covering Bloc (Cubit vs Bloc, BlocProvider, BlocListener, BlocBuilder, BlocSelector, BlocConsumer), Riverpod (StateNotifierProvider, NotifierProvider, FutureProvider, StreamProvider, ref.watch/read/listen, autoDispose, family), GoRouter (declarative routing, deep links, redirect guards, ShellRoute for nested navigation, StatefulShellRoute, typed routes), Dio (interceptors, error handling, retry with dio_smart_retry, request cancellation, logging), Clean Architecture (data/domain/presentation layers, repository pattern, use cases, dependency injection), and testing (bloc_test, Riverpod test, widget test with ProviderScope, mocktail, unit testing repository/use cases). Designed for the Flutter Developer agent building production-grade Flutter applications.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Global installation strategy for opencode-agent-kit: cross-platform config paths, symlink-based per-project setup, environment variable overrides, and upgrade workflow.