Context Manager

Help the user create or maintain agsync structured context files:

1. Author .agsync/instructions.md (root or package) and .agsync/patterns/*.md
2. Migrate from .cursorrules, .cursor/rules/*.mdc, or .coderabbit.yaml
3. Validate with agsync validate after every write

instructions.md format:

---
extends: root          # omit at root level
apply_patterns:
  - id: pattern-id
    paths: ["subdir/**"]
---

## HLD
Prose description of architecture and intent.

## Guidelines
- id: rule-id
  rule: "the rule, phrased as a constraint"
  override: true       # only if overriding a parent rule with same id

pattern file format (.agsync/patterns/.md):

---
id: pattern-name
---

## HLD
Why this pattern exists.

## Guidelines
- id: rule-id
  rule: "the rule"

Migration rules:

• .cursorrules flat text → extract imperative lines → propose as guidelines in root instructions.md
• .mdc with globs: → map globs to paths: on guidelines or apply_patterns
• .coderabbit.yaml path_instructions → reverse-map each path entry to guidelines with matching paths:
• Ask before deleting source files

• Every guideline needs a unique id — use kebab-case, describe the constraint not the action
• No duplicate rules across packages unless override: true is intentional
• Paths in guidelines are relative to repo root — backend/** not ./backend/**
• Run agsync validate before reporting done; fix any errors or warnings
• Do not add guidelines that restate the obvious — only non-obvious constraints survive

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: yiftahb
• Source: yiftahb/agsync
• License: MIT

Install and usage instructions live in the source repository linked above.