Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

mastra-memory

Sterne3

Forks0

Aktualisiert9. Juli 2026 um 19:24

Mastra Memory system guide - storage backends, message history, observational memory, working memory, semantic recall, and thread management

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

artsmc

artsmc/claude-dev-agents

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

name	mastra-memory
description	Mastra Memory system guide - storage backends, message history, observational memory, working memory, semantic recall, and thread management

Mastra Memory System Development

Comprehensive guide for configuring Mastra memory systems. Covers storage backends, message history, observational memory (auto fact extraction), working memory (structured state), semantic recall (embedding-based), and thread management. Memory features are configured via options, not processor classes.

Usage

/mastra-memory

Provides context for:

Memory class constructor with options-based config
Storage backends (LibSQLStore, PostgresStore, UpstashStore)
options.lastMessages for message history
options.semanticRecall for embedding-based recall
options.workingMemory for structured state
options.observationalMemory for fact extraction
Thread management and cloning
Agent integration via memory property

Mehr aus diesem Repository

gleiches Repository

start-phase-execute

artsmc/claude-dev-agents

Structured task execution with quality gates, parallel waves, and pm-db tracking — solo or with multi-agent teams (--team). Use this skill when the user wants to execute a task list, run implementation tasks, start building a feature from a plan, run tasks in parallel with a team of agents, or says things like 'execute these tasks', 'start building', 'run the implementation', 'execute the plan', 'execute with a team', or 'start phase execute'. Also triggers on '/start-phase execute' and '/start-phase-execute-team' commands.

2026-07-093

architecture-quality-assess

artsmc/claude-dev-agents

Assess and score codebase architecture health — layer separation, SOLID compliance, module coupling (FAN-IN/FAN-OUT), circular dependencies, drift from documented patterns. Use whenever the user asks to assess/review/grade architecture quality, wants an architecture score, or asks how healthy the codebase's architecture is. Analysis-only report + refactoring tasks; for docs-vs-code drift use document-hub-analyze.

2026-07-093

code-duplication

artsmc/claude-dev-agents

Deep analysis of codebase for code duplication. Detects exact, structural, and pattern-level duplicates, generates comprehensive reports with refactoring suggestions and metrics.

2026-07-093

diagnose-from-raw-symptom

artsmc/claude-dev-agents

Use when Mark reports a bug by pasting a raw artifact with little or no prose — a stack trace, an HTTP request/response trace (URL + method + status like 500/403/404/502), a console/React/Prisma error, a ChunkLoadError, a shell error, or a screenshot of a visual defect — or when he says things like 'still failing', 'clicking X does nothing', 'no inline editor on the rendered page', 'do we have local postgres/pgvector?', or 'identify the true error'. This is the front-to-back debugging procedure — extract the trigger and reproduction from terse input, probe whether the underlying plumbing even exists, localize by contrasting known-good vs broken, and drive to a durable root cause rather than a workaround. Reach for this BEFORE proposing any fix.

2026-07-093

document-hub-analyze

artsmc/claude-dev-agents

Deep analysis of codebase vs documentation alignment (cline-docs/). Detects drift, identifies undocumented code, extracts missing glossary terms, and provides actionable recommendations without making changes. Use this skill when the user asks "are the docs up to date", "check documentation quality", "what's missing from the docs", or wants a read-only audit before deciding what to update. For actually making changes, use document-hub-update instead.

2026-07-093

document-hub-initialize

artsmc/claude-dev-agents

Bootstrap a new project's documentation hub by creating the four core documentation files (systemArchitecture.md, keyPairResponsibility.md, glossary.md, techStack.md) with initial content based on codebase analysis.

2026-07-093

Jeden Skill mit einem Klick ausführen