padosoft-agent-instructions-synclisted

Use this skill whenever a file that instructs a coding agent is created, changed or deleted — CLAUDE.md, AGENTS.md, a rule or skill folder, a Copilot instructions file, a Gemini or Cursor or Codex configuration — in a repository where more than one agent is used. Also when the user says one agent follows a rule the others ignore, that a convention was applied by one tool and not another, that an instructions file was truncated, or asks how to keep the instruction files aligned. It gives the one-source-many-targets contract, the per-target limits that force a transformation, and the checks that catch a target left behind. Do not use it to write the content of a rule, nor to build a skill for publication (padosoft-skill-creator covers that).
padosoft/skills · ★ 1 · AI & Automation · score 80

Install: claude install-skill padosoft/skills

# Agent instructions sync A repository used with more than one coding agent has the same rules written in several places, in formats that are not interchangeable. Change one and the others keep instructing the old behaviour — silently, because nothing in a repository fails when two instruction files disagree. **The rule: one authoritative source, every other file derived from it in the same change. A rule one agent knows and the others do not is worse than no rule, because the disagreement gets attributed to the code.** --- ## 1. Declare the source and the targets, once Write the mapping down in the repository, next to the source. It is the contract, and it is the thing that tells the next person what they are about to leave behind. | Source (authoritative) | Target A | Target B | |---|---|---| | the per-topic rule files | one instruction file each, path-scoped | one section each, appended to a single file | | the top-level project instructions | the tool's own top-level instructions file | a section in the same single file | | skills, packaged workflows | not supported — inline the critical part | not supported — inline the critical part | | subagent definitions | not supported — record the gap | not supported — record the gap | Two things this table is for: telling you which targets exist at all, and **making the unsupported cells visible**. A capability that one agent has and another does not is a gap you accept on purpose, not one you discover when the second agent