菜单
Narrow file-writing skill for creating only a Digitable game folder and game.json after the user explicitly asks to scaffold project metadata or after new-game-discovery has established the title, player count, component scope, and prototype direction.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Automate browser interactions, test web pages and work with Playwright tests.
Define typed, serializable error variants with defineErrors from wellcrafted. Use when creating error types, handling domain errors, or reviewing error definitions.
Error handling patterns using wellcrafted trySync and tryAsync. Use when writing or reviewing try-catch blocks, refactoring try-catch to linear control flow, working with Result types, or returning HTTP error responses from route handlers.
Architectural patterns for code that uses wellcrafted. Covers control flow with trySync/tryAsync, factory function composition, service layers with Result types, error composition across boundaries, and the single-or-array pattern.
Working with Result types, Ok, Err, trySync, tryAsync, and utility functions from wellcrafted. Use when wrapping unsafe code, handling errors with Results, or destructuring { data, error } responses.
Explore board game component directions for Digitable, generating several distinct options for cards, boards, resources, factions, powers, scoring, conflict, economy, or unusual mechanics before the user commits to implementation.
| name | game-metadata-scaffold |
| description | Narrow file-writing skill for creating only a Digitable game folder and game.json after the user explicitly asks to scaffold project metadata or after new-game-discovery has established the title, player count, component scope, and prototype direction. |
| compatibility | opencode |
| metadata | {"digitable-kind":"game-creation"} |
Use this skill only when the user wants to scaffold a new Digitable game project folder and game.json.
This is not the main entry point for vague or early-stage game ideas.
Use new-game-discovery first when the user says they want to make, start, create, design, or prototype a new game and they are still discovering the fantasy, mechanics, scope, component structure, or first playable loop.
Use game-metadata-scaffold once the required metadata is known or when the user explicitly wants to scaffold the folder and game.json now.
If the user says "I want to create a new game" and describes an idea, theme, genre, mechanism, target experience, or component concept, do not use this skill first. Hand off to new-game-discovery.
references/game-metadata-schema.json.game.json into that folder.game.json must be valid JSON, not Markdown.Use new-game-discovery before scaffolding when the game idea is still taking shape, and after scaffolding if the user wants to continue toward a first playable prototype. Use rules-explorer if the user already has rules that need hardening.