references-synclisted

Sync llms.txt-style dependency reference docs into docs/references/ so the agent has library docs in-context — scans package manifests and fetches known vendor references. Use when working with a third-party library whose docs aren't yet local.
tansuasici/claude-code-kit · ★ 1 · AI & Automation · score 77

Install: claude install-skill tansuasici/claude-code-kit

# References Sync ## Core Rule This skill is for **in-repo agent context**, not SEO. Google explicitly says `llms.txt` does not affect Search visibility (see [AI Optimization Guide, "Mythbusting"](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)). The skill exists so the agent has dependency docs in its working set — `docs/references/` files are read alongside code, not published to the web. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections (Top Rules + index) If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/references-sync` when: - A new dependency is added and you want its docs in the agent's context - A dependency is bumped to a major version (refresh the reference) - Onboarding to a project — populate `docs/references/` for the existing manifest - As a scheduled background task (`/loop monthly /references-sync`) to keep references fresh ## Default Behavior When the user asks to sync, refresh, populate, or "set up references" for dependencies, produce the full references-sync workflow automatically using the Process and Output Format sections below. Do not require the user to specify which packages — the skill scans manifests itself. This skill **writes files*