plolink/cursor-to-claude-code

Overview

This skill provides a complete, phase-based guide to migrate a project from Cursor development mode to Claude Code development mode. It defines a master Agent + SubAgent workflow, recommended document structures (CLAUDE.md, rules/, agent_docs/, AGENTS.md), and verification checkpoints to ensure a safe, incremental migration. The approach emphasizes abstraction, progressive disclosure, and compounding engineering so improvements become permanent knowledge.

How this skill works

The skill breaks the migration into six phases: analysis, configuration migration, experience capture, documentation structuring, context engineering optimization, and compounding engineering. A Master Agent designs the plan and delegates concrete tasks to SubAgents that explore the codebase, create files, and run verification tasks. Each phase includes explicit deliverables and validation checks to ensure traceability and correctness.

When to use it

• When switching a project from Cursor IDE workflows to Claude Code CLI workflows
• When you need an AI-agent-friendly configuration and documentation layout
• When consolidating implicit team knowledge into an explicit knowledge base
• When standardizing rules, workflows, and troubleshooting for agent automation
• When introducing continuous improvement mechanisms (Git hooks, templates)

Best practices

• Keep CLAUDE.md as an index under 500 lines; point to detailed docs for specifics
• Adopt progressive disclosure: index (CLAUDE.md) → rules/ → agent_docs/
• Store each rule in its own document with problem, correct/incorrect examples, and references
• Use file:line pointers instead of code copies to keep docs synchronized with code
• Treat the Master Agent as planner; SubAgents perform actions and a separate validator verifies results

Example use cases

• Migrate .cursorrules and .cursor/ configuration into CLAUDE.md and rules/ with clear WHAT/WHY/HOW sections
• Extract TODO/FIXME/HACK comments into AGENTS.md entries documenting traps and fixes
• Add Git hooks and templates to enforce documentation updates on commits and merges
• Create rules/rule-name.md files with positive and negative code examples for linters and reviewers
• Run validation tasks after each phase to ensure documentation, references, and configs are consistent