migrate-to-claude

Migrate .cursor project assets to Claude Code's .claude directory structure.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/a35506322/Lab.Todo --skill migrate-to-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-claude
Source: https://github.com/a35506322/Lab.Todo/tree/main/.cursor/skills/migrate-to-claude
Command: npx skills add https://github.com/a35506322/Lab.Todo --skill migrate-to-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of rewriting .cursor project rules, settings, commands, skills, and agents to fit Claude Code's required directory structure and file format, saving developers hours of repetitive copy-paste and format adjustment effort.

Core Features & Use Cases

  • 1:1 Asset Migration: Maps all .cursor project assets directly to Claude Code's .claude directory structure without altering original content or semantics.
  • Minimal Format Alignment: Only applies the smallest necessary format changes (e.g. renaming .mdc rule files to .md, adding required YAML frontmatter for agent files) to meet Claude Code's specifications.
  • Use Case: You have a project with custom .cursor rules for .NET backend development and Vue frontend workflows; use this Skill to migrate all existing standards to Claude Code in one go, so you can reuse the same development guidelines when working with Claude.

Quick Start

Use the migrate-to-claude skill to transfer all .cursor project rules, settings, and skills from your current project to the .claude directory structure for Claude Code.

Frequently Asked Questions about migrate-to-claude

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

FAQPage Schema
How do I migrate .cursor project rules to Claude Code?

Migrating .cursor project rules to Claude Code involves transferring configuration assets like rules, settings, and commands directly into the required .claude directory structure while preserving the original content and semantics for 1:1 parity.

Can I reuse my existing .cursor development workflows in Claude Code?

Yes, you can reuse existing .cursor development workflows in Claude Code by migrating project standards including custom rules and agent configurations, ensuring the same development guidelines apply when working with Claude.

What format changes are required when moving .cursor rules to the .claude directory?

Moving .cursor rules to the .claude directory requires minimal format alignment, specifically renaming .mdc rule files to .md and adding required YAML frontmatter for agent files, without modifying the original content or semantics.

Does migrating .cursor settings to Claude Code alter my original project configurations?

No, migrating .cursor settings to Claude Code does not alter original project configurations. The process applies only minimal necessary format adjustments to meet specifications while ensuring 1:1 parity with source .cursor assets.

What is the best way to convert .cursor agents and skills for Claude Code?

The best way to convert .cursor agents and skills for Claude Code is to map them directly to the .claude directory structure, applying only required format adjustments like adding YAML frontmatter to agent files without changing their processing semantics.