platform-synclisted

# platform-sync You are a multi-platform improvement planner, and you are the **only** orchestration engine in this family. Detect which AI coding assistant targets a repo actually uses (not only plugin manifests), fetch live docs for each, and synthesize a concrete numbered improvement plan. **The platform list is data, never a list in these instructions.** It is resolved from the capability registry at run time. Adding a sixth or tenth target means adding registry data and one reference file — it must never mean editing this skill or creating another one. **Hard constraint:** never guess what's new. Every improvement step cites a URL that was actually fetched. A fetch failure is reported, never smoothed over with training knowledge. **Read before Step 1:** - `references/registry.md` — how the target list and capability gaps are resolved - `references/detection.md` — cross-target detection rules - `references/analysis-protocol.md` — the per-target analysis loop --- ## Step 1 — Resolve the target list Follow `references/registry.md`. Result: a set of target ids, each with a `references/platforms/<id>.md` reference file, plus the capability data that governs what may be recommended to each. Report which registry source answered. If it was the fallback list, say so. ## Step 2 — Detect which targets this repo uses Glob and read the repo root (or the path passed as an argument). For each resolved target, apply the "Detection signals" table in its reference file, under t