setup-commands

Migrate legacy command configurations to Cursor's skills-based architecture.

27|4|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/markmhendrickson/neotoma --skill setup-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-commands
Source: https://github.com/markmhendrickson/neotoma/tree/main/.cursor/skills/setup-commands
Command: npx skills add https://github.com/markmhendrickson/neotoma --skill setup-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the transition from legacy command installations to the modern skills-based architecture, ensuring users can still access foundational functionalities.

Core Features & Use Cases

  • Guides Migration: Informs users about the shift from .cursor/commands to .cursor/skills.
  • Facilitates Setup: Directs users to the setup-cursor-copies skill for updating their .cursor/rules and .cursor/skills directories.
  • Use Case: When a user encounters an older setup instruction referencing .cursor/commands, this skill clarifies the new process and points them to the correct tool.

Quick Start

Run the setup-cursor-copies skill to update your foundation rules and skills.

Frequently Asked Questions about setup-commands

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

FAQPage Schema
How do I migrate legacy commands to skills in Cursor?

To migrate legacy commands to skills in Cursor, you transition your configurations from the deprecated `.cursor/commands` directory into the new `.cursor/skills` architecture. This ensures continued access to foundational functionalities.

Why are my .cursor/commands not working anymore?

Your `.cursor/commands` are not working because the directory is deprecated in favor of the `.cursor/skills` architecture. You must migrate your configurations to the new workspace structure to restore functionality.

What is the difference between .cursor/commands and .cursor/skills?

The difference is that `.cursor/commands` is the deprecated legacy directory, while `.cursor/skills` is the modern architecture. Migrating to `.cursor/skills` ensures your workspace foundation rules are correctly updated.

How do I update my foundation rules and skills directories in Cursor?

To update your `.cursor/rules` and `.cursor/skills` directories, you run the setup-cursor-copies skill. This facilitates the setup process and migrates your legacy configurations to the new architecture.

Can I still use older setup instructions referencing .cursor/commands?

You cannot use older setup instructions referencing `.cursor/commands` directly. The setup-commands migration process clarifies the new workflow and directs you to the correct tools for updating your workspace.

Do I need to manually copy files from .cursor/commands to .cursor/skills?

You do not need to manually copy files from `.cursor/commands` to `.cursor/skills`. The migration process directs you to use the setup-cursor-copies skill to update your directories automatically.