sync-y3maker-to-claude

Migrate legacy Y3Maker assets into Claude Code's .claude directory structure.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill sync-y3maker-to-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-y3maker-to-claude
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/sync-y3maker-to-claude
Command: npx skills add https://github.com/WindXRan/y3td --skill sync-y3maker-to-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It solves the problem of legacy Y3Maker/CodeMaker helper systems being incompatible with Claude Code’s native project structure, causing fragmented knowledge, broken paths, and unreliable MCP configuration.

Core Features & Use Cases

  • Workspace inventory & migration planning: Detects which legacy and Claude Code surfaces exist and prepares a detailed migration plan without touching the original .y3maker/.
  • Idempotent apply with safe merge semantics: Creates or updates .claude/ copies, normalizes SKILL.md frontmatter, rewrites legacy path references, and records outcomes in .claude/migration/y3maker-manifest.json.
  • Optional MCP configuration conversion with explicit user control: Converts .y3maker/mcp_settings.json into either project-level .mcp.json, user-level ~/.claude.json, or skips—without silently modifying MCP config.

Quick Start

Run the skill for a dry run on your workspace to preview what it would create or update: node "./scripts/run-migration.js" apply --workspace "." --dry-run --mcp-scope project --pretty

Frequently Asked Questions about sync-y3maker-to-claude

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

FAQPage Schema
How do I migrate Y3Maker assistant assets to Claude Code project structure?

To migrate Y3Maker assistant assets to Claude Code, run the migration script with a dry run to preview changes. It safely converts knowledge, memory, rules, and skills from the .y3maker directory into Claude Code's native .claude directory structure.

Does Y3Maker migration modify my existing MCP configuration silently?

Y3Maker migration does not modify MCP configuration silently. It requires explicit user control to convert mcp_settings.json into project-level .mcp.json or user-level config, and provides a skip option to prevent unauthorized changes to your MCP setup.

What is idempotent sync for legacy path rewriting during migration?

Idempotent sync for legacy path rewriting ensures repeated migration runs produce consistent results without duplication. It uses a manifest file to track synchronization outcomes, allowing you to safely apply migrations multiple times without breaking references.

Can I preview workspace changes before applying the Y3Maker to Claude Code migration?

You can preview workspace changes before applying the migration by running the script with the dry-run flag. This inventories legacy and Claude Code surfaces, generates a detailed migration plan, and displays expected updates without modifying any files.

How does the migration handle SKILL.md frontmatter normalization?

SKILL.md frontmatter normalization updates legacy metadata fields to match Claude Code's expected format during the migration apply phase. It safely merges semantic updates into .claude copies while preserving the original knowledge content.

When should I avoid using an automated migration for Y3Maker workspaces?

You should avoid automated migration for unsafe workspaces lacking proper structure. The skill explicitly refuses to process directories that do not meet safety requirements, preventing broken paths and unreliable configuration in your Claude Code environment.