convention-sync

Syncs HARNESS.md conventions to Cursor, Copilot and Windsurf rule files.

44|6|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Habitat-Thinking/ai-literacy-superpowers --skill convention-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convention-sync
Source: https://github.com/Habitat-Thinking/ai-literacy-superpowers/tree/main/ai-literacy-superpowers/skills/convention-sync
Command: npx skills add https://github.com/Habitat-Thinking/ai-literacy-superpowers --skill convention-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Divergent convention files across Cursor, Copilot, and Windsurf cause tool-specific behavior to drift away from HARNESS.md's master rules. This skill reads HARNESS.md and generates or updates the corresponding convention files so all tools reflect the same project standards.

Core Features & Use Cases

  • One-way synchronization from HARNESS.md to Cursor, Copilot, and Windsurf convention files.
  • Generates or updates .cursor/rules/conventions.mdc, .cursor/rules/constraints.mdc, .github/copilot-instructions.md, and .windsurf/rules/conventions.md / .windsurf/rules/constraints.md based on HARNESS.md sections.
  • Supports conflict resolution by diffing against existing files and prompting before overwrite to preserve manual edits when desired.

Quick Start

Invoke by running /convention-sync to synchronize conventions from HARNESS.md to all supported tools.

Frequently Asked Questions about convention-sync

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

FAQPage Schema
How do I keep AI coding conventions in sync across Cursor, Copilot, and Windsurf?

You can sync AI coding conventions by running a one-way synchronization from a master HARNESS.md file to generate or update target rules files for Cursor, Copilot, and Windsurf automatically.

What is the best way to prevent divergent convention files across multiple AI code editors?

Using a single source of truth like HARNESS.md to generate tool-specific convention files prevents divergent behavior by applying master project standards across all supported AI editors.

Does convention-sync overwrite manual edits in my .cursor/rules or copilot-instructions files?

No, it uses a diff-and-prompt conflict workflow that diffs against existing files and prompts before overwriting, allowing you to preserve manual edits in your convention files.

Can I synchronize project constraints and context rules to .github/copilot-instructions.md from one config?

Yes, you can synchronize constraints and context by running the tool to read HARNESS.md sections and output corresponding rules directly to .github/copilot-instructions.md.

Do I need a HARNESS.md file before syncing conventions to Windsurf and Cursor?

Yes, a HARNESS.md file is required as the master config because the tool performs a one-way synchronization from HARNESS.md sections to target tool-specific convention files.

How to update Windsurf conventions and constraints without losing existing project rules?

You can update Windsurf conventions safely by executing a sync that diffs against existing .windsurf/rules files and prompts before overwriting to resolve any conflicts with manual edits.