菜单
Core development philosophy - fix platform code, not mod content. Load when making decisions about what to fix or implement.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | platform-first |
| description | Core development philosophy - fix platform code, not mod content. Load when making decisions about what to fix or implement. |
Fix the platform, not the content.
At this stage of development, all agents focus on platform code (core/, scenes/, Sparkling Editor), NOT mod content (mods/).
The Captain (user) creates all mod content exactly as a real modder would. This ensures:
| Symptom | Wrong Response | Correct Response |
|---|---|---|
| Character data is malformed | Fix the .tres file | Fix the Sparkling Editor component that generated it |
| Battle doesn't load correctly | Edit the battle resource | Fix BattleManager or MapMetadataLoader |
| Item stats are wrong | Edit the item resource | Fix the item editor or validation |
| Cinematic breaks | Edit the JSON file | Fix CinematicLoader or the cinematic editor |
mods/*/data/Direct mod content changes are acceptable ONLY when:
If a modder would hit the same problem the Captain hit, the platform is broken. Fix the platform.
GDScript coding standards for The Sparkling Farce. Use when writing or reviewing code for style compliance.
Where to place game content vs platform code. Use when creating new files or moving existing code.
Run the project test suite. Use when user mentions "diagnostics", "run level 1 diagnostics", or asks to run tests.
Correct patterns for accessing game resources via ModLoader registry. Use when loading characters, items, abilities, or any mod content.
View the newest screenshot(s) from the user's Screenshots folder. Use when user says SNS, SNS2, SNS3, or asks to see a screenshot.
Reference for preferred UNIX tools over LLM processing. Use when processing JSON, text, searching files, or doing batch operations.