generate-style

Generate the host repository STYLE.md with one or more art-style templates plus a primary art pipeline and allowed alternatives. Use when creating or replacing the project visual contract.

SKILL.md

GitHub

When to use

Use when ../STYLE.md is missing or when the user wants to regenerate it after changing the repository art style mix.

Workflow

  1. If ../STYLE.md is missing, ask the user which templates from ./.styles/ apply unless the user already named the desired style. Default the art pipeline to PROOF_TO_MODEL unless the user names another one.
  2. Support multiple templates for mixed art-direction repositories.
  3. Normalize imagegen to CLOUD, use canonical LOCAL for direct Bubo generation, normalize proof-to-model, proof to model, or 2d-to-3d to PROOF_TO_MODEL, threejs to CODE, and blender, blend, or bpy to BLENDER. Record exactly one primary and repeatable allowed alternatives.
  4. Add repeatable optional external library roots only when the user explicitly configures them. Preserve existing entries during regeneration unless the user replaces or clears them; never prompt for them during startup or initial setup.
  5. Generate ../STYLE.md from the selected style and pipeline templates using concise read directives by default.
  6. Use inline mode only when the user explicitly asks for fully embedded template content.
  7. Validate the generated contract and treat it as authoritative afterward.

Output

  • A STYLE.md containing at least one style, exactly one primary pipeline, allowed pipelines, prompt-override scope, no-silent-fallback policy, and optional read-only external library roots.
  • Style-contract validation output.

Guardrails

  • Default new contracts to PROOF_TO_MODEL; this never authorizes image generation, downloads, or promotion. Reject CSS3/CSS/vector/css-vector selections with migration guidance.
  • Do not silently select a different pipeline when the chosen one is unavailable.
  • Do not use a task-local override to rewrite STYLE.md.
  • Do not invent, require, or probe an external asset-library path when none is configured.
  • LOCAL selection configures policy only. Use use-bubo-local-generation for separate readiness, authorized setup and bounded execution; keep exact model/tool pins in Bubo and preserve existing media budgets/reviews.

Commands

  • ./commands/generate-style.sh "<STYLE1>" ["STYLE2" ...]
  • ./commands/generate-style.sh --pipeline CLOUD --allow-pipeline CODE "<STYLE1>"
  • ./commands/generate-style.sh --pipeline BLENDER --allow-pipeline PROOF_TO_MODEL "<STYLE1>"
  • ./commands/generate-style.sh --asset-library studio=/absolute/path/to/models "<STYLE1>"
  • ./commands/generate-style.sh --clear-asset-libraries "<STYLE1>"
  • ./commands/generate-style.sh --inline "<STYLE1>" ["STYLE2" ...]
  • ./commands/validate-style-contract.sh [STYLE.md]