Tattoo pipeline + LMASK two-stage production workflow.
The workflow is now more app-like: tattoos generate their own tmask support files, while LMASK uses a guided Project Studio for Stage 1 approval, Stage 2 mapping profiles, prompt export, and new-chat handoff packs.
Main tattoo PNG plus tattoo support files generated together: design_mask.png and design_blur.png. tmask is merged into the tattoo workflow, not separate.
Stage 1: generate a high-quality real-life wrestler mask design. This preserves the pipeline that creates great-looking masks.
R1.0.5 guided app workflow: save one project locally, select a profile, build the prompt, and download a new-chat handoff pack.
Stage 2: upload the approved mask image in a new chat and use a modular mapping profile loaded from /profiles/lmask/.
CakeView, CakeHook, Tribute 26, DDS export, UV placement, multi-slot setup, custom material slots, and troubleshooting.
First generate a beautiful mask. Then approve it. Then use Project Studio to produce a project brief, upload checklist, prompt TXT, and selected profile JSON for the separate new-chat mapping handoff. This avoids undefined profile-name-only prompts and low-quality test-looking textures.