菜单
Root conf.json schema, defaults, size rules, preview handling, and reload requirements for Dartsnut projects.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Dartsnut asset manifest, loader-helper, placeholder, and apply-mode workflow for art-bearing entities.
Dartsnut workspace scaffold rules, just-in-time skill loading, file constraints, and emulator verification workflow.
Dartsnut display and framebuffer mapping rules for panels, physical screens, layout, clipping, and fonts.
Legacy Dartsnut runtime index that routes to the granular pydartsnut, conf, display, and asset skills.
Pixel-perfect compact UI guidance for console-style Dartsnut games and widgets.
Dartsnut game dart slot color mapping based on dart_index modulo four.
| name | conf-contract |
| description | Root conf.json schema, defaults, size rules, preview handling, and reload requirements for Dartsnut projects. |
| license | MIT |
Load this before write_file on root conf.json. Use recorded intake metadata (read_workspace_conf / host context) for type, size, and widget display size when available.
id, type, name, author, version, description, size, fields
preview: include for new projects as [""] unless the user omits it explicitly.type: "game" or "widget" per intake metadata when present.size: two-element integer array [width, height] — never a string like "128x160".fields: JSON array; use [] when no custom fields.| Key | Default |
|---|---|
id | kebab-case slug from project name |
author | "Dartsnut Team" or "Unknown" |
version | "0.1.0" or "1.0.0" (pick one scheme per project) |
description | one-sentence summary of what it does |
[128, 160] unless context overrides.size must match the recorded widget display size when intake provided one.{
"id": "<slug>",
"type": "game",
"name": "<Title>",
"author": "Dartsnut Team",
"version": "0.1.0",
"description": "<one sentence>",
"size": [128, 160],
"fields": [],
"preview": [""]
}
For widgets, set "type": "widget" and size from intake metadata (e.g. [128, 128]).
After creating or materially changing conf.json, call reload_emulator then get_emulator_logs so the preview sees the new config and Python started cleanly.