8.0 KiB
name, description
| name | description |
|---|---|
| sanctification-card-production | Create, revise, or review Sanctification card illustrations, layered printings, and finish masks using the repository art direction and production contract. Use for card asset production, not general app UI or unrelated shader work. |
Sanctification Card Production
Use this skill from the Sanctification repository. Resolve repository links relative to this file; keep detailed geometry and material guidance in the maintained documents rather than copying them here.
Read for the Assigned Work
- Art generation, edits, and illustration review: read Card Art Brief's Shared Illustration Rules, the requested rarity profile, and Illustration Review. Read the card-specific scene/prompt and selected layout guide. During an art-only loop, do not load broad product guidance, assembly scripts, harness defaults, or unrelated rarity profiles by default. Pass only relevant style rules and the scene brief to image generation.
- Frames, lettering, product presentation, or printings: read relevant sections of Art Direction. Illustration rules are maintained in the compact brief; do not duplicate them here or in product guidance.
- Production assembly after artwork approval: read Card Layer Pipeline and Harness Defaults, plus the selected proof's README, layout, content, build script, and validation. The session brief supplies task fields and phase-specific deliverables for a new card.
Read relevant functional specification sections only when choosing catalog content or instance properties. Timothy is the Common assembly reference; Burning Bush is a Rare proof with pending visual decisions. Proof scripts are subject-specific, not a general batch engine. Draft document coordinates do not override a selected versioned layout.
Organize Card Work
Follow Card work and approval. Use the exact master-catalogue ID as cardId, the catalogue title as title, and an ID-title directory as folderName; select revisions by ID through the index. New card production belongs in in-progress/cards/[ID-title]/revisions/[revision]/, with revision-specific content/build/source/review records and low/med/high printing exports. Use the workspace scaffold and manifests to track art-review and assembly-review. Keep pipeline, material, font, branding and harness experiments in spikes/; do not create new card-production spike folders. After explicit final card approval for an exact revision, promote it through card_workspace.py approve, recording the approval wording. Artwork approval alone is not final card approval. Accepted content lives directly in artifacts/cards/[ID-title]/ (no revision folder); keep the exact revision in the manifest. Preserve earlier accepted packages in working history when replacing them, and freeze approved revisions.
Execute the Requested Scope
For new or revised illustrations, use the available image-generation skill/tool and apply the compact art brief. Retain exact prompts and native source, and record the uniform crop/scale into the 2000 × 2800 canvas. Inspect against the brief's Illustration Review criteria; finish coverage cannot supply missing illustration structure. Within-segment light/color modeling belongs to the base art and does not call for runtime reflection or roughness changes.
Art Prototyping Loop
Until the user explicitly approves, locks, or otherwise concludes that the artwork is ready, treat illustration work as an art-only loop. For each iteration, update only the native generated/edit source, its prompt or edit record, the recorded fit into the common canvas, and review images needed to judge composition, style, and focal placement. A non-exported template guide may help review placement.
Do not run final assembly during this loop: do not regenerate frame or backing assets, text layers, glyph-protection masks, finish masks, four-printing faces, runtime fixtures, or production validation. Preserve approved reusable layers and previous proof outputs as comparison inputs. If a user specifically asks for an intermediate composed card or material test, make only that requested preview and label it as provisional.
Begin the production assembly only after explicit artwork approval. Then use the selected final art to rebuild every affected derived export once, so registrations, active-overlay occlusion, and material data are consistent. A source-art change after approval reopens this loop unless the user asks to proceed directly to a final rebuild.
For new stained-glass assembly, use the approved raw-ridges-v1 shared finish module, following Finish Coverage. Regenerate raw confidence from fitted artwork once and compile each printing from its actual visible overlay/lettering alpha. Use the versioned recipe without adding continuity filtering, bridging or manual repair patches. Record recipe/source/component hashes; inspect retained texture flecks in motion. Existing cards and fixtures keep their selected recipes unless migration is requested. Alternatives are separate reviewed experiments; no extra runtime pane/lead textures are required.
Reuse the selected tier’s versioned frame/backing geometry from the shared layer library. Pin the tier/version in card data, verify the layer manifest, and reference canonical assets directly without proof-local layer copies or regeneration. Current candidate review status is recorded in the library; preserve historical proofs and existing cards’ pinned versions. Typeset lettering separately using the exact shared faces in Art Direction’s typography role table; reference shared fonts/licenses directly and do not create or copy card-local font folders. Validate the shared manifest hash and glyph coverage. Non-Legendary text uses #263f50 on base #f4ead4. Measure actual unclipped glyph bounds and revise overflow rather than silently shrinking text. Export Normal, Textless, Borderless, and Boundless with exactly their prescribed components when a full card production task requests them.
Keep every layer/map on the same canvas and transform. Runtime faces are opaque rectangles; Three.js geometry owns the rounded silhouette. Preserve solid framed corners, protected joins, and data-map conventions: finish white receives coating; lead/glyph protection white excludes treatment. Removing lettering/backings removes only their associated protection, not lead protection.
Use existing SVG/Inkscape, ImageMagick, and proof-specific scripts where suitable. Keep originals and comparison fixtures, and preserve unrelated working-tree edits. A request to review or adjust documentation does not authorize regenerating or publishing assets. New proofs remain in the requested output folder unless fixture replacement is part of the user’s request.
Verify and Deliver
During art prototyping, inspect only the illustration and requested review images. After production assembly, run the selected proof's relevant structural/export checks and inspect composed cards, finish maps, and any tested pane/lead inputs. Compare Printed ink, Foil, and Holographic under matching light/camera settings in motion when available. Correct material regions before proposing changes to shared shader coefficients.
Deliver reproducible inputs/exports and an honest report of structural checks, static visual assessment, moving-light review, and pending decisions. Never call agent review user approval or claim GPU validation when WebGL is unavailable. For documentation-only work, validate references and skill structure without generating card art or running unrelated renderer tests.