asset-spec

Generate per-asset visual specifications and AI prompts from design documents.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill asset-spec-solace-ill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asset-spec
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/asset-spec
Command: npx skills add https://github.com/solace-ill/vector-flow --skill asset-spec-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Asset spec generation streamlines turning GDDs, art bibles, and character profiles into concrete, production-ready asset specifications and AI prompts, reducing handoffs and inconsistencies.

Core Features & Use Cases

  • Generates per-asset visual specifications and generation prompts from design documents.
  • Updates the master asset manifest and flags un-specced assets for production planning.
  • Supports a multi-phase workflow (context gathering, asset identification, spec generation, and integration with art/tech pipelines).

Quick Start

Run /asset-spec system:<name> to generate specs for the next unspecced asset using the art bible and GDDs.

Frequently Asked Questions about asset-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate asset specifications from a game design document?

You can generate asset specifications from a game design document by running the /asset-spec command, which identifies unspecced assets, applies art bible standards, and outputs ready-to-use prompts and visual specs.

What is the best way to automate AI generation prompts for game art assets?

Automating AI generation prompts for game art assets is best handled by extracting visual requirements from design documents and character profiles, then converting them into structured, ready-to-use prompts for art teams.

How do I update the master asset manifest during pre-production?

You update the master asset manifest during pre-production by generating per-asset visual specifications, which automatically log new specs and flag missing assets for production planning.

Can I use design docs to enforce art bible standards across engineering teams?

Yes, you can enforce art bible standards across engineering teams by generating structured asset specifications and automated cross-team handoffs directly from approved design documents.

What are the limitations of automated asset spec generation?

Automated asset spec generation is limited to pre-production workflows after art bible and design document approval, meaning it cannot enforce standards or generate specs for unapproved or incomplete design docs.