--- name: convention-sync-3dc97fad04d4 description: Use when syncing HARNESS.md conventions to Cursor, Copilot, and Windsurf convention files — reads Context and Constraints sections and generates tool-specific output so all AI coding tools share the same project rules --- # Convention Sync Across AI Tools ## Overview Teams using multiple AI coding tools hit convention drift: HARNESS.md declares the project's conventions and constraints, but Cursor, Copilot, and Windsurf each have their own convention file format. Without sync, those tools operate blind — or worse, with stale copies of rules that were updated in HARNESS.md weeks ago. This skill reads the Context and Constraints sections of HARNESS.md and generates the corresponding convention files for each supported tool. HARNESS.md is the single source of truth. Sync is one-way only: HARNESS.md drives the other files. No tool-specific file feeds back into HARNESS.md. --- ## What Gets Synced | HARNESS.md Section | Target Content | | --- | --- | | Context > Stack | Tool description / context block — languages, build system, test framework | | Context > Conventions | Convention rules — naming, file structure, error handling, documentation | | Constraints (each entry) | One rule block per constraint with enforcement level and scope | | Constraint `Scope` field | Cursor glob pattern (falls back to `**/*` when Scope is absent) | Sections outside Context and Constraints (Garbage Collection, Status) are not synced — they are harness-internal and have no equivalent in other tools. --- ## Running the Sync Invoke via the slash command: ```text /convention-sync ``` Or ask the agent directly: "Sync my HARNESS.md conventions to Cursor, Copilot, and Windsurf." The agent will: 1. Read HARNESS.md from the project root 2. Parse the Context and Constraints sections 3. Generate or update each target file 4. Report what changed in a summary table --- ## Output Format Reference ### Cursor Generates two files in `.cursor/rules/`: #### `.cursor/rules/conventions.mdc` Contains the Context section from HARNESS.md. Frontmatter format: ```text --- description: Project conventions synced from HARNESS.md globs: **/* alwaysApply: true --- # Project Conventions ## Stack - Primary languages: Go 1.22 - Build system: make ... ## Conventions - Naming: snake_case for files, PascalCase for types ... ``` #### `.cursor/rules/constraints.mdc` Contains one rule block per constraint. Each constraint becomes a section with its enforcement level and scope. The `globs` frontmatter field is set from the constraint's `Scope` field if present, otherwise defaults to `**/*`. ```text --- description: Project constraints synced from HARNESS.md globs: **/* alwaysApply: true --- # Project Constraints ## Consistent formatting - Rule: All source files must pass the project's configured formatter without changes - Enforcement: unverified - Scope: commit ## No secrets in source - Rule: No API keys, tokens, passwords, or private keys may appear in committed source files - Enforcement: deterministic - Scope: commit ``` ### Copilot Generates a single flat markdown file: #### `.github/copilot-instructions.md` Combines Context and Constraints into one document. No frontmatter — Copilot reads plain markdown. ```markdown # Project Conventions These conventions are synced from HARNESS.md. Do not edit this file directly — run `/convention-sync` to regenerate. ## Stack - Primary languages: Go 1.22 ... ## Conventions - Naming: snake_case for files, PascalCase for types ... ## Constraints ### Consistent formatting - Rule: All source files must pass the project's configured formatter without changes - Enforcement: unverified - Scope: commit ### No secrets in source - Rule: No API keys, tokens, passwords, or private keys may appear in committed source files - Enforcement: deterministic - Scope: commit ``` ### Windsurf Generates two files in `.windsurf/rules/`: #### `.windsurf/rules/conventions.md` Same content structure as the Cursor conventions file but without frontmatter globs (Windsurf does not support glob scoping). ```markdown # Project Conventions These conventions are synced from HARNESS.md. Do not edit this file directly — run `/convention-sync` to regenerate. ## Stack - Primary languages: Go 1.22 ... ## Conventions - Naming: snake_case for files, PascalCase for types ... ``` #### `.windsurf/rules/constraints.md` Same content structure as the Cursor constraints file but without frontmatter. ```markdown # Project Constraints These constraints are synced from HARNESS.md. Do not edit this file directly — run `/convention-sync` to regenerate. ## Consistent formatting - Rule: All source files must pass the project's configured formatter without changes - Enforcement: unverified - Scope: commit ``` --- ## Conflict Resolution When a target file already exists: 1. Generate the new content from HARNESS.md 2. Diff the generated content against the existing file 3. If the files are identical, report "unchanged" and move on 4. If they differ, show the user what changed and ask before overwriting 5. If the user declines, report "skipped" for that file **HARNESS.md always wins.** The target files are generated output. Any manual edits to them will be overwritten on the next sync unless the user explicitly skips the file. The correct workflow for adding tool-specific rules that do not belong in HARNESS.md is to create a separate rule file that the sync does not manage. --- ## Verification After generating all files, spot-check that every constraint from HARNESS.md appears in each output file: 1. List every constraint heading from HARNESS.md 2. For each target file, confirm the constraint heading appears 3. Report any missing constraints If a constraint is missing from any output, the generation has a bug. Do not silently skip constraints. --- Source attribution: Habitat-Thinking Original project: https://github.com/Habitat-Thinking/ai-literacy-superpowers/blob/a50b8136e8e170a828b7a61aa3e8815475b56bc9/ai-literacy-superpowers/skills/convention-sync/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean, as defined by Sections 1 through 9 of this document, any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works of the Work, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by the combined work of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or any Contribution embodied within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, You must include a readable copy of the attribution notices contained within such NOTICE file, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or in addition to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own license statement for Your modifications and may provide additional grant of rights to use, reproduce, modify, and distribute Your modifications, or for such Derivative Works as a whole, under terms and conditions that You define, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or reproducing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or exemplary damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may charge only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format in use. It is also recommended that a file or directory "NOTICE" is included with your work that provides attribution notices that are separate from the LICENSE file. Copyright 2026 Russ Miles Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: Habitat-Thinking Original project: https://github.com/Habitat-Thinking/ai-literacy-superpowers/blob/a50b8136e8e170a828b7a61aa3e8815475b56bc9/ai-literacy-superpowers/skills/convention-sync/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, Frontend Developer, Full-Stack Developer, Product Manager Specialties: API Tools: GitHub Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 243d2ff000d3e61035d5f94a198c424498b1e9f21eb93fd06acbeeb97b6d9924