mcpField
M
mastra-framework-guide

mastra-framework-guide

github.com/efoo-teamDevelopment050 installsUpdated 1w ago
Repository

About mastra-framework-guide

A guide for developers building AI applications with Mastra, covering API lookup, documentation discovery, and version migrations. It prioritizes documentation bundled with installed packages to match the project's version.

Key features

  1. 01Prioritize documentation in installed packages
  2. 02Find references based on the question
  3. 03Verify current APIs before coding
  4. 04Distinguish agent and workflow use
  5. 05Look up common errors and fixes
  6. 06Guidance for version migrations

Use cases

  1. 01Implementing features with current Mastra APIs
  2. 02Finding component docs after installing packages
  3. 03Investigating type or constructor errors
  4. 04Planning a Mastra version upgrade

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/efoo-team/skills --skill mastra-framework-guide

After installing, type/mastra-framework-guidein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
common-errors.md
create-mastra.md
embedded-docs.md
migration-guide.md
remote-docs.md

Details

From the project README

Mastra Framework Guide

Last verified: 2026-07(Mastra v1.50.1 / @mastra/core 同梱 docs / https://mastra.ai で検証。DOCTOR.md の四半期鮮度チェックの対象)

Build AI applications with Mastra. This skill teaches you how to find current documentation and build agents and workflows.

このスキルは Mastra の利用・更新ガイド(API 検証・ドキュメント探索・バージョン移行)である。設計上の責務分離・単一エージェント優先などの設計原則は、設計憲章スキル mastra-ai-architecture-rules(編集禁止)に従うこと。本ガイド = どう使い最新仕様に追従するか、憲章 = どう設計すべきか、という棲み分けである。

⚠️ Critical: Do not trust internal knowledge

Everything you know about Mastra is likely outdated or wrong. Never rely on memory. Always verify against current documentation.

Your training data contains obsolete APIs, deprecated patterns, and incorrect usage. Mastra evolves rapidly - APIs change between versions, constructor signatures shift, and patterns get refactored.

Prerequisites

Before writing any Mastra code, check if packages are installed:

ls node_modules/@mastra/
  • If packages exist: Use embedded docs first (most reliable)
  • If no packages: Install first or use remote docs

Documentation lookup guide

Quick Reference
User QuestionFirst CheckHow To
"Create/install Mastra project"references/create-mastra.mdSetup guide with CLI and manual steps
"How do I use Agent/Workflow/Tool?"references/embedded-docs.mdLook up in node_modules/@mastra/*/dist/docs/
"How do I use X?" (no packages)references/remote-docs.mdFetch from https://mastra.ai/llms.txt
"I'm getting an error..."references/common-errors.mdCommon errors and solutions
"Upgrade from v0.x to v1.x"references/migration-guide.mdVersion upgrade workflows
Priority order for writing code

⚠️ Never write code without checking current docs first

  1. Embedded docs first (if packages installed)

    # First locate SOURCE_MAP.json (its location can move between versions)
    ls node_modules/@mastra/core/dist/docs/
    
    # Check what's available (current layout keeps it under assets/)
    cat node_modules/@mastra/core/dist/docs/assets/SOURCE_MAP.json | grep '"Agent"'
    
    # Read the actual type definition
    cat node_modules/@mastra/core/dist/[path-from-source-map]
    
  2. Remote docs second (if packages not installed)

    # Fetch latest docs
    # https://mastra.ai/llms.txt
    
    • Why: Latest published docs (may be ahead of installed version)
    • Use when: Packages not installed or exploring new features
    • See: references/remote-docs.md

Core concepts

Agents vs workflows

Agent: Autonomous, makes decisions, uses tools Use for: Open-ended tasks (support, research, analysis)

Workflow: Structured sequence of steps Use for: Defined processes (pipelines, approvals, ETL)

Key components
  • Tools: Extend agent capabilities (APIs, databases, external services)
  • Memory: Maintain context (message history, working memory, semantic recall)
  • RAG: Query external knowledge (vector stores, graph relationships)
  • Storage: Persist data (Postgres, LibSQL, MongoDB)

Critical requirements

TypeScript config

Mastra requires ES2022 modules. CommonJS will fail.

{
  "compilerOptions": {
    "target": "ES2022",
    "module": "ES2022",
    "moduleResolution": "bundler"
  }
}
Model format

Always use "provider/model-name":

  • "openai/gpt-5.5"
  • "anthropic/claude-sonnet-4-6"
  • "google/gemini-2.5-pro"

(モデル ID は例示であり必ず陳腐化する。実際に使える ID は現行ドキュメントで確認する)

When you see errors

Type errors often mean your knowledge is outdated.

Common signs of outdated knowledge:

  • Property X does not exist on type Y
  • Cannot find module
  • Type mismatch errors
  • Constructor parameter errors

What to do:

  1. Check references/common-errors.md
  2. Verify current API in embedded docs
  3. Don't assume the error is a user mistake - it might be your outdated knowledge

Development workflow

Always verify before writing code:

  1. Check packages installed

    ls node_modules/@mastra/
    
  2. Look up current API

  3. Write code based on current docs

  4. Test in Studio

    pnpm dev  # http://localhost:4111
    

Resources

Comments

Markdown supported