install-rules

Install rules into Cursor or Trae IDE with conflict detection and user confirmation.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill install-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-rules
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/install-rules
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill install-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Install rules from source repository into Cursor or Trae IDE with explicit confirmation and conflict detection before any write.

Core Features & Use Cases

  • Parse rules from a source repository or local rules; build a list of installable rules.
  • Analyze target state to identify conflicts and duplicates.
  • Show an explicit installation plan with actions (create/skip/conflict/update) and target paths.
  • Require user consent before writing any files to Cursor or Trae.
  • Write rules to Cursor (.mdc) or Trae managed blocks, and report results.

Quick Start

Review the proposed install plan and confirm to apply the selected rules to Cursor or Trae.

Frequently Asked Questions about install-rules

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

FAQPage Schema
How do I install rules into Cursor or Trae without overwriting existing files?

To install rules safely, this tool analyzes existing target directories for conflicts and builds a conservative plan showing create, skip, update, or conflict actions. It enforces idempotent writes and requires explicit user confirmation before modifying any files.

Can I sync project-level rules from a source repository to the Trae IDE?

Yes, you can install rules from a source repository or local directory into Trae. The system supports both project-level and user-level destinations, parsing the source rules and writing them to Trae managed blocks after you approve the installation plan.

What happens when conflicting rule files are detected during a Cursor IDE setup?

When conflicting rule files are detected during Cursor setup, the tool surfaces a conflict action in the installation plan. It holds approval before modifying any files, allowing you to review the create, skip, update, or conflict actions and explicitly confirm which rules to apply.

Does the Cursor rules installation process generate a post-install summary?

Yes, the Cursor rules installation process generates a post-install summary. After writing the rules to Cursor (.mdc) files or Trae managed blocks, the system reports the results, ensuring you have a clear record of all applied, skipped, or conflicted actions.

What is the best way to manage duplicate Cursor .mdc rule files during deployment?

The best way to manage duplicate Cursor .mdc files is using an installation plan that identifies duplicates and conflicts. The tool builds a conservative plan with explicit actions, enforcing idempotent writes to prevent redundant deployments and requiring consent before writing.