ttc-blueprint

Create or edit a TTC blueprint

Blueprints are the design templates of a TTC project, one JSON file each in data/blueprints/.

First read ${CLAUDE_PLUGIN_ROOT}/docs/ttc-guidelines.md (all sections) and the blueprint section of ${CLAUDE_PLUGIN_ROOT}/docs/ttc-file-format.md.

Steps

1. Validate the project folder; read existing blueprints (and the sets that reference the one being edited). Back up before modifying.
2. Clarify the design intent if underspecified: component size in mm, bleed, front and back content, which panels must be editable per item.
3. New blueprint: create data/blueprints/<uuid4>.json with a single entry in the blueprints array. Set a unique name, type (usually "card"), layout_size_mm, bleeding_size_mm, shape_settings.radius, hint_order_index = max existing + 1, and at least one front layer. Add a background procedural panel as the last panel, extending into the bleed (negative position, oversize). Give back sides at least an empty layer.
4. Edit blueprint: modify the existing file. When renaming a blueprint, update blueprint_name in every set that references it. When renaming or deleting a panel, update or remove matching details[].name entries in the sets' items.
5. Panel design rules:
   • order panels from foreground (first) to background (last);
   • organize panels into named layers by what moves together (e.g. sfondo for background/frame, contenuto for foreground, one layer per repeated region such as tracks or headers); layers render last-to-first like panels, so foreground layers come first and background last. Avoid a single catch-all layer, and re-group the panels of any existing blueprint you edit;
   • a {tag} in a value can be a variable OR a reference to another panel of the component (see "Tag resolution" in the file-format doc). Use {panel} references to mirror a field (e.g. the same cost number on all four corners), {panel}_suffix patterns to derive assets ({yokai}_ico), {{panel}_suffix} nesting for variable families;
   • don't give a variable the same code as a panel name: variables resolve first and shadow the panel;
   • mark decorative/fixed panels "panel_editable": "False"; leave item-specific panels editable;
   • image values are asset paths without extension or Category/name library icon ids.
6. Validate (guidelines section 6) and remind the user to reload the project in TTC.