46 lines
6.5 KiB
Markdown
46 lines
6.5 KiB
Markdown
# Prompt for a New Card-Generation Session
|
||
|
||
Copy the block below and replace the bracketed fields. Illustration approval precedes assembly. Existing proof scripts are subject-specific; inspect the selected tier's proof before adapting a build.
|
||
|
||
```text
|
||
Use $sanctification-card-production for Sanctification card production.
|
||
If unavailable through skill discovery, read sanctification/.agents/skills/sanctification-card-production/SKILL.md directly.
|
||
|
||
Card brief:
|
||
- Subject/name: [name]
|
||
- Canonical rarity: [Common / Uncommon / Rare / Extraordinary / Legendary]
|
||
- Subject type: [catalog type]
|
||
- Scene or governing idea: [one concrete sentence]
|
||
- Scripture/quote: [reference and translation; propose wording if needed]
|
||
- Optional subtitle: [short descriptor, or omit]
|
||
- Catalogue card ID: [exact master-catalogue ID, e.g. BP-045]
|
||
- Revision: [v01 / v02 / …]
|
||
- Output folder: [sanctification/in-progress/cards/[ID-title]/revisions/[revision]/]
|
||
- Requested phase: [art prototyping / assembly of explicitly approved art]
|
||
- Approved artwork source: [path and revision for assembly; otherwise pending]
|
||
- Frame/backing set: [tier/version under artifacts/layers, or a bespoke Legendary template/source; pending during art exploration]
|
||
- Optional Legendary overlap: [element and intended impression, or omit; identify selected adapted foreground sources for assembly]
|
||
|
||
Use the catalogue ID as cardId, the display title as title, and an ID-title slug as folderName. Resolve paths through the index rather than deriving identity from a title.
|
||
|
||
Before starting, follow docs/card-workspace.md and scaffold the working revision with tools/card-production/card_workspace.py new. Keep card-specific content and build inputs in the revision; shared sources/reviews sit outside low/med/high exports. Use low=500×700, med=1000×1400, high=2000×2800, each with normal/boundless/borderless/textless folders.
|
||
|
||
For art prototyping:
|
||
Read docs/card-art-brief.md's Shared Illustration Rules, requested rarity profile, and Illustration Review, plus the card-specific scene and selected layout guide. These paths are relative to sanctification/.
|
||
Use the available image-generation skill/tool. Follow the compact brief without loading broad product, assembly, or material documents by default.
|
||
Retain native source, exact generation/edit prompts, and recorded uniform crop/scale into the 2000 × 2800 canvas. Do not call an upscale native high-resolution art.
|
||
Inspect at standard and thumbnail sizes against the chosen guide. For Legendary overlaps, follow the brief's Legendary profile: preserve visual connection and the shared glass medium, but allow the foreground to be artistically adapted rather than matching the covered base art exactly. If I request a composed preview, use real shared lettering to assess complete form, join, silhouette and text clearance; keep that preview provisional. Retain edited donor sources/prompts/fit separately from the base art. Deliver source art and review images, then await explicit artwork approval, including any selected adapted foreground.
|
||
Defer frame/backing rendering, typography, masks, four-printing exports, runtime assets, and production validation during the art loop unless I specifically request an intermediate preview.
|
||
|
||
After explicit artwork approval:
|
||
Read relevant sections of docs/art-direction.md, docs/card-layer-pipeline.md, card-harness/CURRENT-DEFAULTS.md, and the selected proof's README, layout, card data, build and validation.
|
||
Read docs/functional-spec-v2.md only for relevant catalog or instance-property choices.
|
||
For Common through Extraordinary, load the pinned shared tier/version from artifacts/layers using library.load_tier; verify its manifest hashes and use its layout and canonical assets directly. Do not copy shared layers into the card folder or regenerate them during a card build. Current v2 candidates await visual approval; preserve old card versions. Reuse selected tier frame/backing geometry; verify wording and attribution and typeset deterministic text. Follow docs/art-direction.md’s typography role table: P052-Bold.otf at 700 for titles, and SanctificationP052-Medium.otf at 500 for verses/excerpts, references and approved descriptors. Reference the exact shared font files and their license directly from fonts/ (paths relative to sanctification/). Do not create a proof-local fonts folder or copy fonts/licenses from another proof; validate the shared manifest hash and glyph coverage.
|
||
For a bespoke Legendary, retain its selected frame/backing geometry and component hashes rather than requiring a shared-tier template. Follow docs/art-direction.md's Legendary Bespoke Composition and docs/card-layer-pipeline.md's Legendary Foreground Composition. Use explicit per-printing selections and preserve shared font roles. Analyze the adapted foreground for finish coverage as well as the base art, then resolve visible finish through the same alpha/order as the face. Do not count an illustrated overlap as backing protection, copy the underlying base mask into revised cloth, or assume a flat-overlay builder handles this automatically.
|
||
Follow the pipeline's printing definitions, opaque runtime-corner contract, per-printing finish coverage, glyph protection, and validation. For new stained-glass cards, use tools/card-production/finish_masks.py and the approved raw-ridges-v1 recipe: regenerate raw confidence directly from fitted artwork, reuse illustration analysis across printings, and compile actual visible overlay/lettering alpha. Do not copy legacy saturation/value finish code from a proof or add continuity filtering, bridging or manual repair patches to v1. Record recipe/source/component hashes and tool versions. Preserve existing shader settings and comparison fixtures; do not migrate older cards unless requested.
|
||
Deliver retained sources/prompts and metadata, editable layers/SVG, reproducible build, all four printings at master/1000/500 widths, matching finish maps and applicable text maps, review sheets, and an honest validation report.
|
||
Moving-light review may remain pending if WebGL is unavailable.
|
||
|
||
Keep work in the requested working revision and preserve unrelated edits. Track art-review/assembly-review in the manifests and refresh/validate them after production assembly. After explicit final card approval for that exact revision, use card_workspace.py approve with the user’s approval wording to move it into artifacts/cards/[ID-title]/. Illustration approval alone does not authorize that promotion. Do not publish or replace harness fixtures unless requested. Report agent review, user approval, and runtime review separately.
|
||
```
|