Dashboardopencode-loreOpenCode skill, configuration, project-…

OpenCode skill, configuration, project-state, SSE, and V8 diagnostic contracts

Category: preference
Confidence: 1.00
ID: 01a0a72b-12aa-7eb9-bf74-fdff6c7b1667
Project ID: 6f4be9ff-ed84-4cca-a9e7-732a0b0b8677
Cross-project: No
Recalled in other projects: 1
Source session: 0IiwozJmFR9A6QyFo
Created: 2026-08-26 11:16:04
Updated: 2026-09-15 22:23:33

Cross-Project Recalls

ProjectHitsLast recalled
cli 2 8d ago

Content

OpenCode skill names must match folder names, use lowercase hyphenated text, and be at most 64 characters. Each skill needs a trigger-focused third-person description; use Use ONLY when... to avoid adjacent activation. In opencode.json, model names include the provider prefix, and each MCP requires type plus a string-array command. Store each project's path and Git remote together in a map keyed by project ID; separate globals cause cross-project races. Prefer request-specific chat.headers; use currentProject only when the fetch interceptor lacks a session ID. Bound SSE events and bytes per subscriber while preserving order and terminal events; allow one active stream per reconnecting TUI. On disconnect, cancellation, overflow, or failure, release responses, listeners, queues, and retained payloads. Unbounded cloned payloads can exhaust V8. For high RSS or CPU, or empty 502s, inspect Mark-Compact logs and heap_used_bytes; repeated GC near V8's ceiling indicates JavaScript retention. Capture heap snapshot before assigning ownership.

Move to: