菜单
One-time migration: modernize a Joyride project's copilot-instructions.md to use bundled skills instead of duplicated API docs or fetch URLs. Use when: the instructions file tells you to check for migration, or the user asks about updating their Joyride AI context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | joyride-update-llm-contexts |
| description | One-time migration: modernize a Joyride project's copilot-instructions.md to use bundled skills instead of duplicated API docs or fetch URLs. Use when: the instructions file tells you to check for migration, or the user asks about updating their Joyride AI context. |
One-time migration skill. The Joyride extension now bundles skills with
comprehensive API documentation and pattern guidance. Older installations
may have a copilot-instructions.md that duplicates this content or
fetches it from GitHub URLs.
Look for ~/.config/joyride/.github/llm-contexts-0.0.73.txt. If this file
exists, migration has already been done — inform the user and stop.
If the file does not exist, proceed with the migration.
Read ~/.config/joyride/.github/copilot-instructions.md and classify:
| Situation | Markers |
|---|---|
| Old template | Contains fetch_webpage URLs pointing to llm-contexts/, title "Joyride User Scripts Project Assistant", duplicated API docs |
| Already modern | Short file (~25 lines), references bundled skills, has "Project Inventory" section |
| Custom content | User-written content with no old template markers |
| Mixed | Old template sections plus user-added custom sections |
| Missing | File does not exist |
If the file is already modern or missing, skip to Step 4.
The modern copilot-instructions.md is a short project inventory (~25 lines) that defers all API documentation to the extension's bundled skills. No fetch URLs, no duplicated docs. The format:
---
description: 'Joyride User project — scripts and source files available across all VS Code windows'
applyTo: '**'
---
# Joyride User Project
This is your Joyride User project at `~/.config/joyride/`. Scripts and
source files here are available globally across all VS Code windows.
The Joyride extension bundles skills with comprehensive API documentation
and pattern guidance. These instructions focus on this project's specific
content.
## Project Inventory
- `scripts/user_activate.cljs` — Activation script, manages disposables
- (list actual files found in scripts/ and src/)
## Development
Use the REPL (`joyride_evaluate_code`) as your primary tool. Develop
incrementally, evaluate subexpressions, only update files when asked.
Prefer structural editing tools when editing Clojure files.
As new scripts and source files are added to this project, update the
inventory above.
Build a migration plan based on the assessment:
Present the plan to the user showing:
Wait for explicit user approval before making any changes.
Apply the approved changes (if any), then create the marker file:
~/.config/joyride/.github/llm-contexts-0.0.73.txt
Write a single line: Joyride LLM contexts updated to version 0.0.73 bundled skills.
This prevents the migration from being offered again.
Joyride core — REPL evaluation, async patterns, VS Code API access, Flares, JS interop, and available libraries. Use when: working with Joyride evaluation, writing ClojureScript in any Joyride context, creating Flares/WebViews, exploring VS Code APIs via the REPL, or using joyride_evaluate_code.
Joyride User scope scripting — scripts and source files in ~/.config/joyride/. Covers user activation scripts, global keyboard shortcuts, disposable management, and npm dependencies. Use when: creating or editing User scripts/source files, setting up user_activate.cljs, or configuring global keybindings.
Joyride Workspace scope scripting — scripts and source files in <workspace>/.joyride/. Covers workspace activation, project-specific automation, workspace vs user scope precedence, and team sharing. Use when: creating or editing Workspace scripts/source files, setting up workspace_activate.cljs, or building project-specific automation.
Joyride extension internals — subsystem contracts, state architecture, activation sequences, and namespace reference. Use when: modifying core extension code, debugging state issues, working with app-db or SCI context, understanding activation or script execution flow, investigating nREPL or when-context behavior, or working with the output or disposable system.
Test Joyride features in the examples workspace. Covers output terminal verification, who-tracking, REPL log queries, and evaluation result validation. Use when: testing Joyride features.