amcs-style-generator

Generate a validated style specification with SHA-256 provenance hash.

1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/miethe/MeatyMusic --skill amcs-style-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amcs-style-generator
Source: https://github.com/miethe/MeatyMusic/tree/main/.claude/skills/workflow/style
Command: npx skills add https://github.com/miethe/MeatyMusic --skill amcs-style-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts SDS style preferences into a validated style specification that respects blueprint constraints, resolves tag conflicts with a first-seen-wins strategy, clamps tempo to blueprint ranges, and hashes the final style for provenance.

Core Features & Use Cases

  • Blueprint loading: Tempo ranges, defaults, tag priorities
  • Tag conflict resolution: First-seen-wins to eliminate conflicting tags
  • Tempo clamping: Ensure tempo stays within blueprint ranges
  • Instrumentation control: Limit to 3 items
  • Provenance: SHA-256 hash of final style

Quick Start

  1. Provide SDS style + plan
  2. Run the STYLE skill
  3. Validate output against blueprint

Frequently Asked Questions about amcs-style-generator

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

FAQPage Schema
How do I generate a validated style specification from SDS preferences?

Style generation converts SDS style preferences into a validated specification that respects blueprint constraints, resolves tag conflicts using first-seen-wins logic, clamps tempo to blueprint ranges, and produces a SHA-256 provenance hash for the final output.

What does blueprint-compliant style mean in the AMCS workflow?

Blueprint-compliant style enforces tempo ranges, default values, tag priorities, and instrumentation limits defined in your blueprint. The style generator validates against these constraints before outputting the specification.

How are tag conflicts resolved during style generation?

Tag conflicts use a first-seen-wins strategy, where the first occurrence of a tag is retained and conflicting duplicates are eliminated, ensuring a clean, non-contradictory style specification.

Can I limit instrumentation in the generated style?

Yes, the style generator restricts instrumentation to a maximum of 3 items while applying blueprint defaults and ensuring all selections comply with your specified constraints.

What input does the style generator require?

Provide SDS style preferences and a plan output from the AMCS workflow. The generator validates tempo, resolves tags, and applies blueprint constraints to produce a deterministic style specification.

Why is a SHA-256 provenance hash included in the output?

The hash provides deterministic versioning and traceability of the final style specification, allowing you to verify that the exact same preferences and constraints always generate identical output.