sync-ruleslisted

# sync-rules Use this skill to close an AI-assisted development iteration by extracting durable knowledge from actual changes and routing it to the right target. Do not treat every invocation as a full sync across all layers. ## Targets | Target | Use For | Default Policy | | --- | --- | --- | | K1 personal knowledge base | Reusable lessons, decisions, research, plan evolution | Preview, then append history and update current view if present | | K2 project docs | Feature summaries, usage docs, generated superpower docs, implementation docs | Scoped edits to relevant docs | | K3 agent memory suggestion | Durable user preferences and cross-project working style | Suggest only unless user explicitly says to remember | | K4 project instructions | Stable rules future agents must obey, such as `AGENTS.md` or `CLAUDE.md` | Confirm before editing | ## Core Rules 1. Route before writing. Decide K1/K2/K3/K4 from the user's intent and the evidence; do not update all targets by default. 2. Distill next-useful knowledge, not a work log. Avoid relative dates and process narration. 3. Preserve historical thinking in K1. Keep research, requirements analysis, original plans, and decision rationale as history; append dated adjustments. Keep a separate current note or current section up to date for latest architecture, behavior, usage, and run instructions. 4. Create missing K1 files when appropriate. If the knowledge-base path is configured but no matching note exists, p