CCK Kiosk Alignment

End-to-end workflow for handling CCK kiosk print-alignment reports. When a kiosk merchant sends a list of cases with print-alignment issues — usually short location notes like “15 pro right side” alongside photos — this skill produces four coordinated deliverables off a single cases.json input. The deliverables share ticket IDs, finish vocabulary (Smoke Frost / Clear Frost), and brand voice so nothing drifts between the merchant copy and the factory copy.

• •A CCK merchant texts a list of case models with location callouts (e.g. “S26 ultra sm bottom left side”) and reference photos.
• •Someone says “open tickets for this kiosk’s cases” or “send the factory the alignment list.”
• •A kiosk operator sends HEIC photos with brief captions and you need to log them, confirm the merchant, and brief the factory.
• •You’re onboarding a new kiosk and need a clean handoff template the first time it reports alignment issues.

• Internal alignment tracker

  <KIOSK>_Alignment_Tracker.xlsx

  Excel sheet with one row per case, embedded reference photo, and the customer’s verbatim quote. Notes tab carries the SM/CL legend and the workflow context.

• Customer / merchant confirmation PDF

  <KIOSK>_Ticket_Confirmation.pdf

  Branded one-pager confirming tickets are open. Custom Case Kiosk header, ticket table mapping each case to a placeholder ID (CCK<kiosk>-NNN), next steps, footer.

• Factory review request PDF

  <KIOSK>_Factory_Review_Request.pdf

  Multi-page document for the factory. Page 1 is a summary table + a two-line ask; pages 2+ are per-case detail blocks with the embedded photo and a verbatim customer quote (no interpretation).

• Factory cover note

  <KIOSK>_Factory_Cover_Note.txt

  Short paste-ready text (4-6 sentences) to send alongside the factory PDF. References the kiosk ID and the ticket ID range, no merchant name.

1. 01.Drop the merchant’s photos into a folder (HEIC is fine — run scripts/heic_to_jpg.py first to convert).
2. 02.Copy `examples/sample_input.json` to a new `cases.json`, swap in the kiosk ID, date, photos folder, and one entry per case (model, finish, print, reported_location, customer_quote, photo).
3. 03.Run `python scripts/build_all.py cases.json "<merchant>" "<your-name>"` to produce all four deliverables in the output folder.
4. 04.Verify each deliverable against the checklist in SKILL.md (no banned terms, no interpretation, photos all embedded). If a photo is pending, the tracker shows a yellow placeholder cell and the factory PDF shows a yellow “Reference photo to follow” card — replace and re-run when it arrives.
5. 05.Send the customer PDF to the merchant, the factory PDF + cover note to the factory. Track replies against the placeholder ticket IDs.

• !SM = Smoke Frost. CL = Clear Frost. Never write matte / soft-touch / clear / glossy / matte-glossy — those are inaccurate finish descriptors and the merchant will correct you.
• !The factory document must never name the merchant. Say “kiosk CCK<###>” or “a customer (kiosk CCK<###>).”
• !Never paraphrase or interpret what the customer reported. Use the verbatim quote in the factory doc; the photo carries the visual evidence.
• !Don’t propose fixes to the factory (“re-align print toward the right edge,” “extend coverage,” “run a sample”). The ask is “review and reply with findings and recommended next steps.”
• !Customer-facing header reads exactly “Custom Case Kiosk” — not “CCK · Custom Case Kiosk.” The CCK abbreviation belongs in the footer line.
• !Banned terms that apply across all CCK content: never use “elevate / elevated” (Nimbus9-only), and never say “GoBear” externally — say “CCK platform” or “kiosk system”.
• !Ticket IDs are placeholders unless wired to a real ticketing system. State that explicitly when handing over deliverables.