Instruction file imported from ZenRay/CursorTemplate (
.cursor/rules/06-migration-guide.mdc). Copyright stays with the author.
Migration Guide
Scenario A: Greenfield (New Project)
Use /paradigm-init for:
- New projects with no existing code
- Starting from scratch
Steps:
- Run
/paradigm-initin empty project directory - Answer 5 questions (project name, type, tech stack, etc.)
- AI auto-executes 7-step initialization
- Review and commit initial setup
Scenario B: Brownfield (Existing Project)
Use /paradigm-adopt for:
- Legacy projects adopting CursorHarness
- Gradual migration per module
Steps:
- Run
/paradigm-adoptin project root - AI audits current structure
- Select modules to adopt (confirm each)
- Per-module migration with verification
- Update documentation
Scenario C: Sync Template Updates
Use /paradigm-sync for:
- Projects already using CursorHarness
- Getting latest template improvements
Steps:
- Run
/paradigm-sync - AI compares local vs template version
- Review changes (tiered report)
- Select changes to apply
- Auto-merge non-breaking changes
- Manual review for breaking changes
Manual Migration Checklist
If commands not available:
-
Copy template files:
.cursor/directorydocs/standards/AGENTS.md,STATE.md
-
Adapt to project:
- Update
AGENTS.mdproject name/description - Adjust
02-code-style.mdcfor your stack - Update
00-project-overview.mdc
- Update
-
Configure Hooks:
- Ensure
jqis installed for JSON parsing - Make scripts executable:
chmod +x .cursor/hooks/*.sh - Test with sample commands
- Ensure
-
Initialize state:
- Create
docs/private/state/wip.md - Create
docs/private/state/handoff.md - Update
STATE.mdwith initial status
- Create
-
First commit:
git add . git commit -m "feat: init CursorHarness paradigm"