메뉴
Safety checks for editing system files — commands in .opencode/command/, skills in .opencode/skills/, agents in .opencode/agent/, or AGENTS.md itself. Load when creating or modifying any of these files.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user wants to find and add an original (non-remastered, non-deluxe, non-club-edition) CD pressing of an album to their Discogs wantlist, or decide which Discogs CD release to buy — e.g. "find an original US CD of X", "add the original pressing to my wantlist", "which CD pressing should I get", or avoiding remaster/deluxe/anniversary/club editions. Discogs-specific.
Apply the product management philosophy to PRDs, OKRs, strategy docs, roadmaps, product decisions, prioritization, and feature evaluation. Problem-first thinking, outcomes over outputs, empowered teams.
Set up or upgrade vitest tests for Cloudflare Workers using @cloudflare/vitest-pool-workers. Use when scaffolding tests in a new Worker, when an existing Worker is on pool-workers <0.13 (vitest 2/3) and needs to upgrade, or when the test suite hits "Isolated storage failed" / "Expected .sqlite, got .sqlite-shm" errors. Pins the modern stack (vitest 4 + pool-workers ≥0.15 + Node 22) and documents the v2→v4 migration recipe.
Builds a self-contained interactive HTML visualisation that makes a process, algorithm, decision logic, or system visually and experientially understandable. Primary input is a linear walkthrough, but works directly from code, documents, or concept descriptions too — and can invoke the linear-walkthrough skill as an intermediate step if the source material lacks sufficient clarity or structure. Use when the user wants to "see how this works", wants an interactive version of a walkthrough, wants to explain a process visually to an audience, or asks to "visualise", "animate", or "build an interactive explanation" of anything. Richer and more interactive is always preferred, as long as it makes the logic clearer rather than decorating it.
Use when the user reports their Mac is slow, sluggish, laggy, or unresponsive — or asks what's using CPU, memory, or battery. Also triggers on "check system performance", "what's eating my CPU", "Mac is hot", "fan is loud", or any request to diagnose macOS resource usage. Covers CPU hogs, memory pressure, swap thrashing, and runaway system daemons.
Discord bot development on Cloudflare Workers — Discord API, Developer Portal, slash commands, Gateway WebSocket, Interactions Endpoint, bot permissions, intents, and Ed25519 verification.
| name | system-file-guardrails |
| description | Safety checks for editing system files — commands in .opencode/command/, skills in .opencode/skills/, agents in .opencode/agent/, or AGENTS.md itself. Load when creating or modifying any of these files. |
Follow these checks when editing system files: commands (.opencode/command/), skills (.opencode/skills/), agents (.opencode/agent/), or AGENTS.md itself.
| Check | What to verify |
|---|---|
| Inbound references | Search for the file's name across .opencode/command/, .opencode/skills/, .opencode/agent/, and AGENTS.md. Note files whose assumptions could break if this file changes. |
| Outbound references | What skills, agents, or commands does this file reference? Verify each exists on disk. |
If broken outbound references are found, warn before proceeding (the edit might be fixing them).
| Check | What to verify |
|---|---|
| Frontmatter | description present |
$ARGUMENTS | Parsed and handled (if command accepts arguments) |
| Skill loading | Lazy — no loading during research phases |
| Token efficiency | Compact tables over prose. Nothing duplicated from AGENTS.md |
| MCP tool references | Correct tool names, fallback behavior if tools are unavailable |
| Check | What to verify |
|---|---|
| Frontmatter | name, description present. Agents: mode, tools also present |
| Description accuracy | Frontmatter description matches what the file actually does |
| Stale references | No references to commands, tools, files, or skills that don't exist |
| Agent quality checklist | Present and covers the agent's actual scope |
When 2+ system files are modified in a session, offer a coherence check before wrapping up:
"You modified N system files this session — running a quick coherence check."
| Check | What to verify |
|---|---|
| Cross-references | Do modified files' references to other files still resolve? |
| Scope alignment | If a convention spans multiple files, do they use consistent language? |
| Displaced content | Were any existing sections accidentally removed or overwritten? |
