菜单
Validate and diagnose startup context files — CLAUDE.md, AGENTS.md, rules, and .cursorrules — that inject instructions into the model context at session start across Claude Code, Cursor, and Codex.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Copy processed MP3s and WAVs to NAS storage. Use after Apple Music import or when re-archiving corrected files.
Move processed ZIPs to archive and clean up extraction folders. Use after album processing is complete.
Copy finished MP3s into Apple Music via the auto-import folder and verify the album lands correctly. Use once metadata is finalized and the user wants tracks added to their library — e.g. "add this to Apple Music" or "import these tracks" — even if they don't say "auto-import" explicitly. Also use to diagnose a bad import, e.g. "it showed up as separate tracks instead of one album."
Inspect and update MP3 tags: genre, artist, album, track count, compilation flag. Use when checking or fixing music file metadata — including diagnostic questions like "why do these show up as separate tracks" or "is this folder's metadata consistent," not just explicit tag-editing requests.
End-to-end processing of downloaded music purchases: extract ZIPs, verify metadata, import to Apple Music, archive to NAS, clean up. Use when processing new music downloads.
Reclaim local disk by offloading cloud-backed Apple Music downloads. Audit iCloud status, build an offload playlist that protects your DJ crates and lossless files, then Remove Download. Use when the Mac is low on disk.
| name | startup-context |
| description | Validate and diagnose startup context files — CLAUDE.md, AGENTS.md, rules, and .cursorrules — that inject instructions into the model context at session start across Claude Code, Cursor, and Codex. |
Use this skill when working with files that inject instructions at startup — validating format, diagnosing why instructions aren't being read, or understanding load order and precedence per vendor.
What startup context is: Files that are automatically loaded into the model's context before any user prompt. Each vendor uses different file names and locations. All serve the same purpose: priming the model with project-specific or harness-level instructions.
Vendor mapping:
| Vendor | Primary file | Rules format | Legacy |
|---|---|---|---|
| Claude Code | CLAUDE.md | .claude/rules/*.md | — |
| Cursor | .cursor/rules/*.mdc | .cursor/rules/*.mdc | .cursorrules (root) |
| Codex | AGENTS.md | NOT SUPPORTED in plugins | — |
Load order (Claude Code): User CLAUDE.md (~/.claude/CLAUDE.md) → Project CLAUDE.md → Plugin CLAUDE.md (via @-import). Rules in .claude/rules/ are loaded after CLAUDE.md.
The @AGENTS.md workaround (Claude Code): Claude Code does not natively read AGENTS.md. When ynh exports for Claude, it writes a CLAUDE.md containing only @AGENTS.md — using Claude's @-import syntax to pull in the cross-vendor instructions file without duplicating content.
Diagnostic checklist:
