asset-spec
Per-asset visual specs plus AI generation prompts from GDDs and character profiles. After the art bible.
HYClub · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add HYClub/deepseek-harness-game-studios --skill asset-spec技能说明
name: asset-spec description: "Per-asset visual specs plus AI generation prompts from GDDs and character profiles. After the art bible." argument-hint: "[system: | level: | character:] [--review full|lean|solo]" user-invocable: true allowed-tools: Read, Glob, Grep, Write, Edit, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/asset-spec/../../hooks/yaml-helper.sh" resolve_config *) model: sonnet
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation
If no argument is provided, check whether design/assets/entity-inventory.md exists:
- If it exists: read it, find the first entity or screen with status "Needed" but no spec file yet, and use
AskUserQuestion:- Prompt: "The next unspecced item is [name]. Generate specs for it?"
- Options:
[A] Yes — spec [name]/[B] Pick a different item/[C] Stop here
- If no entity inventory: check
design/assets/asset-manifest.md. If manifest exists, same flow above but reading from manifest. - If neither exists: start the Entity & Screen Inventory flow (Phase 0b below) rather than failing.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt). Note: actually invoking an external image
generator (calling an image API) always prompts regardless of
modes.automation — it is an irreversible external action guarded
unconditionally, independent of whether external_calls is listed in
automation_always_ask. (Today this skill only emits generation-prompt
text; the guard applies if live generation is ever wired in.)
Phase 0b: Entity & Screen Inventory (runs when no arguments and no existing inventory)
This flow produces design/assets/entity-inventory.md — the master list of everything
the game needs visually. Run once before asset spec work begins.
Step 1 — Gather from docs
Read all available source material in parallel:
design/gdd/systems-index.md— extract every system listed- GDD asset content — do not full-read every GDD. The two wanted sections are
standard headings, and named entities live in the registry:
For named entities (characters, enemies, buildings, items), readGrep pattern="## (Visual/Audio Requirements|UI Requirements)" glob="design/gdd/*.md" output_mode="content" -A 25design/registry/entities.yaml(entities/items) if it exists and has entries; otherwise grep the GDDs for named content. Full-read a GDD only when its Visual/Audio section is missing or reads[To be designed](Phase 1 already handles that case). VFX events surface in the Visual/Audio grep context. design/art/art-bible.md— extract: any named visual categories, asset type expectationsdesign/narrative/— scan for any character or world entity documents if they exist (optional — not required)
Step 2 — Build proposed inventory
Organize everything found into categories:
Characters / Protagonists
Enemies / Creatures
Buildings / Structures
Environment / Terrain
Items / Props
VFX / Particles
UI Screens (list each screen by name)
HUD Elements
Audio (SFX, music — descriptions only, no generation prompts)
Other
For each item, note the source doc it was found in.
Step 3 — Present and collaborate
Present the full proposed inventory to the user in conversation. Then use AskUserQuestion:
- Prompt: "I found [N] visual entities and [N] UI screens across your GDDs and art bible. Review the list — what's missing, what's not needed?"
- Options:
[A] Looks good — save this inventory[B] Add items I'll describe[C] Remove items that don't apply[D] Both add and remove — let me edit
If [B] or [D]: ask the user to describe additional items. Accept brief descriptions ("a medieval keep, used as a level background") or detailed ones — either works. Work through them collaboratively until the user is satisfied.
If [C] or [D]: ask which items to remove and why. Remove them from the list.
Step 4 — Write inventory
After user approval, ask: "May I write the entity inventory to design/assets/entity-inventory.md?"
Write the file:
# Visual Entity & Screen Inventory
> Generated: [date]
> Sources: [list of source docs read]
## Entities
| # | Name | Type | Description | Source | Status |
|---|------|------|-------------|--------|--------|
| 1 | [name] | Character / Enemy / Building / Environment / Item / Other | [brief description] | [source doc] | Needed |
## UI Screens
| # | Screen Name | Description | Source | Status |
|---|-------------|-------------|--------|--------|
| 1 | Main Menu | [description] | [source] | Needed |
## HUD Elements
| # | Element | Description | Source | Status |
|---|---------|-------------|--------|--------|
## Audio
| # | Name | Type (SFX / Music / Ambient) | Description | Source | Status |
|---|------|------------------------------|-------------|--------|--------|
After writing, tell the user:
"Entity inventory saved. Next steps:
- Run
/ux-design [screen name]for each UI screen in the inventory- Run
/asset-spec system:[name],level:[name]orcharacter:[name]for each visual entity — whichever of the three the entity belongs to- Or run
/asset-specagain to work through the inventory one item at a time"
Phase 0: Parse Arguments
Extract:
- Target type:
system,level, orcharacter - Target name: the name after the colon (normalize to kebab-case)
- Review mode:
--review [full|lean|solo]if present
The effective mode is the one already resolved at the top of this skill via
resolve_config --keys review_mode, which applies the full chain; with nothing
set it follows modes.rigor — solo at minimal (the default), lean at
standard, full at full. A --review argument overrides it for this
run only.
Mode behavior:
- `f