Agent skill · kochetkov-ma

memory-sync-setup

Generates a project-tailored memory-sync skill: memory surface batches, checkable-fact catalogue, non-growth sync, independent verify, self-sync, agent re-audit. Triggers: memory sync init, generate memory sync, sync memory skill, установи memory-sync, синхронизируй память

What it needs

About 12k tokens when loaded.

What this skill does

<!-- brewcode-meta: version=6.2.0 contentversion=6.2.0 generatedby=brewdoc:memory-sync-setup --> Memory Sync Generator (brewdoc:memory-sync-setup) ROLE: GENERATOR. It analyzes the TARGET project, then WRITES a self-contained, project-local .claude/skills/memory-sync/ into that repo. It NEVER syncs memory itself -- it emits the skill that does. WHY a generator: generic memory sync produces generic results. Only a skill that already knows THIS repo's batches, invariants, fact-verification commands, agent roster and language policy can keep instruction memory truthful. A generic sweep cannot tell an intentional Russian trigger alias from a language violation, cannot tell a stale lint-rule claim from a correct one, and cannot prove a removed fact is gone from REALITY rather than merely deleted from a doc. OUTPUT: <target>/.claude/skills/memory-sync/ -- SKILL.md + references/memory-guide.md + references/agent-audit.md + references/hard-sync.md + references/prompting-guide.md. Nothing else is written; no agent is created, no rule is installed, no hook is registered. Prompt contract Position 1 of $ARGUMENTS is a free-form prompt (RU/EN) -- modes and the fine-tune text are optional and may follow in any order. Nobody types keys: resolve mode + scope FROM the prompt. 1. Strip flags. An explicit mode token anywhere wins outright, no scoring. 2. Else score modes by distinct whole-word keyword hits (table in ## Modes below). Highest unique score wins. Tie with a destructive mode -> AskUserQuestion; tie with status -> status; tie of two mutating modes -> the keyword appearing first; all zero -> status if installed, else install. 3. Empty arguments -> status if installed, else install; ask ONE scoping AskUserQuestion only when the answer changes what gets written. A read-only run asks nothing. 4. Outcome-changing ambiguity -> ONE AskUserQuestion (max 4 questions) BEFORE any work. 5. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills kochetkov-ma/memory-sync-setup

View the source on GitHub

Browse the @skills marketplace