mcp-integration-patterns

Integrate ruvector memory and morph editing into yellow-plugins commands with graceful degradation.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/KingInYellows/yellow-plugins --skill mcp-integration-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration-patterns
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/plugins/yellow-core/skills/mcp-integration-patterns
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill mcp-integration-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical patterns for integrating ruvector memory and morph editing across yellow-plugins commands and agents. All patterns degrade gracefully when tools are not installed.

Core Features & Use Cases

  • Pattern 1: Recall-Before-Act ensures past learnings are consulted before actions.
  • Pattern 2: Tiered-Remember-After-Act records learnings after workflow completion with automated or prompted persistence.
  • Pattern 3: Morph-Discovery discovers morph tools at runtime for large edits and intent-based code search.
  • Provides runtime ToolSearch discovery, graceful degradation, and robust error handling.

Quick Start

Consult these MCP integration patterns when authoring commands or agents that rely on memory recall or morph editing tools.

Frequently Asked Questions about mcp-integration-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate memory recall into plugin commands before taking action?

To integrate memory recall into plugin commands, apply the Recall-Before-Act pattern to query past learnings from ruvector memory before executing workflows, ensuring actions are informed by institutional memory.

What is graceful degradation when memory or editing tools are unavailable?

Graceful degradation ensures that commands and agents continue functioning when ruvector memory or morph editing tools are not installed, utilizing runtime ToolSearch discovery and robust error handling to avoid failures.

How do I persist learnings after a workflow completes in yellow-plugins?

Persist learnings in yellow-plugins by applying the Tiered-Remember-After-Act pattern, which records workflow outcomes through automated or prompted persistence into ruvector memory after completion.

Can I discover morph editing tools at runtime for large code edits?

Yes, you can discover morph editing tools at runtime for large edits and intent-based code search by applying the Morph-Discovery pattern, which locates available tools dynamically during workflow execution.

What are the anti-patterns to avoid when integrating memory and editing across plugins?

When integrating memory and editing across plugins, avoid anti-patterns that bypass runtime ToolSearch, skip error handling for unavailable tools, or fail to follow recall-before-act and remember-after-act sequences.

Do I need ruvector and morph installed to use commands built with these integration patterns?

No, you do not need ruvector or morph installed; the integration patterns specify behavior for graceful degradation, allowing commands to operate without these tools and handle their absence robustly.