Auto-detect first; manual choice is saved
Auto-detect first; manual choice is saved
Your First Maker Message: What Should Be Sent First?
The first message does not need the entire order file. Begin with the character, scene, existing items, and open questions; add exact SKU wording, top-ups, lead time, order notes, and photo permission as the conversation develops.
Contents
Now · The first message: start with the character, not the whole order file
Quick take
The first line can be simple: name the character version, use scene, references already available, existing items, and the questions that still need the maker’s judgment. Once the conversation is open, add exact SKU wording, link type, top-up mapping, lead time, rework terms, and photo permission. The interest stays warm, but the order gains a place to land.
The first message: start with the character, not the whole order file
A first inquiry rarely begins empty-handed. Character art, buyer photographs, unboxing clips, and close-ups may already be saved everywhere. The part that freezes is the first message: which image should go first, whether to ask about price, or whether to ask if the idea is even workable.
The first message does not need to become a thesis. It only needs the character and version, intended scene, references and existing items already available, and the questions that still need the maker’s judgment. Measurements, top-ups, order notes, and adjustment terms can follow after the maker agrees to continue.
- Open with the character and version, not the entire saved folder.
- Name the scene: home try-on, head-and-shoulder photos, studio shoot, offline event, or event deadline.
- List existing items: head shell, wig, costume, shoes or socks, old Kig skin, or non-baselayer accessories.
- Mark uncertain items directly: material direction, endpoints, access openings, top-ups, lead time, and after-sales terms.
Character page: version, reference groups, and no-go details
The saved folder can stay lively, but the maker needs a reading order. Front view, back view, side view, hair, headwear, eyes, mouth shape, cuffs, collar, socks, shoes, and skirt or hem lines should be grouped by use instead of dropped as one image waterfall.
Separate what must stay, what may change, and what is unacceptable. A calm closed-mouth expression, covered wrists, feet that appear in close-up, or a tone that must not drift gray are all useful notes. For niche characters, outfits with many variants, or masculine character directions, precise local references and version labels matter more than image count.

- Separate front, back, and side views first.
- Mark hair, headwear, eyes, mouth shape, and expression separately.
- Write costume coverage, exposed areas, socks, shoes, collar, and cuff state.
- Separate must-keep, adjustable, and unacceptable items.
- If hands, feet, collar, or wrist appear in close-up, provide local references.
Shell, tone, measurements, and light belong on one page
The head shell is not isolated. In photos, the fragile area is often the lower shell rim, wig coverage, ear zone, neck, and Kig skin tone meeting in one ring. Front, side, lower rim, wig blocking, tone references, and measurements should be read together.
Measurements are not body judgment; they make the pattern executable. Height, weight, shoulder width, bust, waist, hips, arm length, leg length, hand size, and shoe size should follow the maker's measurement sheet and one unit system. If a measurement photo is needed, crop out face, room privacy, platform UI, watermarks, and unrelated background.

- Show front, side, and lower-rim views of the head shell, plus whether wig hair covers ear zones and shell edges.
- Use tone samples or old-skin samples, and label daylight, indoor white light, and target shooting light.
- Separate hood, hard shell, blank shell, full head, and partial coverage wording; do not assume a full neck transition is included.
- Use the maker's measurement sheet and one unit system; mark uncertain values as pending.
- Hand size, shoe size, finger/toe endpoints, and old fit issues deserve separate notes.
Endpoints and access openings serve use before polish
Hands and feet are honest in close-up. Attached hands, split fingers, five-finger fabric hands, long gloves, nail pieces, full-cover feet, five-toe sock feet, shoe-compatible feet, and external foot covers should be written as setup items. Ask not only whether they are included, but also whether color, fabric, wrist connection, fingertip thickness, object handling, and rework are covered.
Access opening1s are not decoration. Face windows, back zippers, large-U access, and hand openings serve dressing, hydration, restroom use, sweat management, vision checks, adjustment, and safe exit. When a page mentions a zipper pull or other zipper wording, ask whether it belongs to the shell, a display item, or an actual back, hand, face-window, or large-U opening.

- Hands: attached, split-finger, five-finger fabric, long glove, nail piece, or hand zipper.
- Feet: full cover, five-toe sock feet, shoe-compatible feet, or external foot cover.
- Wrist and ankle: seamless edge, costume cover, zipper, hook-and-loop, or add-on.
- Access: face window, back zipper, large U, hand or palm-side opening.
- Confirm same tone and material, phone/bag/drink use, and rework or replacement terms.
Before checkout: link type, SKU wording, page-state cues, and add-on mapping
Before opening the payment page, identify the kind of link: main item, deposit, final payment, top-up, special listing, display page, or reference-only page. If the entry point is wrong, the rest of the order can drift.
Keep the search result, product-page display, selected SKU wording, and maker-confirmed delivered total separate. A discounted page state is only a dated page condition; it does not replace confirmation that the discount applies to the selected SKU and the complete order.
Top-up and special-listing links do not enter the budget alone. Tie each one to the main item, selected SKU, amount, corresponding option, whether it must be purchased, whether it ships together, any effect on the queue, lead time, and adjustment scope. If that relationship is unclear, pause.
- Copy the selected SKU wording exactly; keep a dated screenshot, then repeat the text in the order note where it is easier to review.
- Confirm whether the selected SKU is preorder, reservation, or in stock; for stock, ask which piece, size, flaws, whether photos already exist, and whether the item is exactly the shown piece.
- For preorder, ask cut-off, batch, production window, delay handling, and event deadline.
- Break all-inclusive wording into body skin, endpoints, access openings, special accessories, storage, shipping, and rework.
- Hard shell, wig, eye plates, headwear, costume, and props stay separate unless explicitly included.
Order notes turn a promise into checkable fields
A maker saying ‘we can do it’ is good news, but it is not yet the final page of the order. Rewrite the reply as specific fields: character version, main link, selected SKU, tone, measurements, hand and foot setup, access openings, inclusions, exclusions, delivered total, top-up links, deposit and final payment, shipping wording, and adjustment terms. Delivery can then be checked against a record rather than memory.
Custom items may not follow ordinary return rules, but that does not mean there is no after-sales path. Before payment, ask about the feedback window, required photographs, round-trip shipping, material fees, number of adjustments, and expected turnaround.
- Order note fields: character/version [ ]; main link/title [ ]; selected SKU wording [ ]; material/tone [ ]; measurement sheet [sent/pending].
- Setup fields: hands [ ]; feet [ ]; access openings [ ]; included [ ]; excluded [ ].
- Payment fields: maker-confirmed delivered total [ ]; shipping [included / separate / collect-on-delivery / pending]; add-on/top-up/special listing [title + amount + mapped setup + required or optional]; deposit/final payment [amount + node + refundability].
- Timing fields: lead-time start [payment / final brief / queue date]; shipping context [preorder / in stock / expected date].
- Rework fields: feedback window, photo requirements, shipping, material fee, change count, and rework lead time.
Photo permission and problem records stay separate
Keep three uses separate. Photographs shared publicly should be anonymous and free of interfaces, watermarks, order details, and private backgrounds. Images sent to the maker should focus on the character, measurements, selected options, and the exact problem. Try-ons, flatlays, maintenance, failed actions, unboxing, and after-sales records usually stay private.
Write down photo permission as well. Finished photographs, flatlays, local details, or masked structure images should not become maker samples without a separate confirmation. Measurement, try-on, adjustment, and private-background photographs are not public by default.
When a problem needs photographs, follow the order-note fields: daylight and indoor white light, front, back, side, palm, hand back, fingertips, wrist, toes, sole, ankle, zipper, and access openings. The message can then name the exact field that differs instead of relying on ‘it feels wrong.’
- Public: anonymous, clear, no platform UI, no watermark, no private background.
- Maker-facing: character references, necessary measurement images, setup confirmation, and problem close-ups.
- Keep private: try-on, flat lay, maintenance, failed-action, unboxing, and after-sales records.
- Permission field: may show [finished photo / flatlay / local detail / masked structure / not allowed]; never public by default [measurement / try-on / rework / private background / platform UI].
- Problem photographs follow the order fields instead of memory.
Copy cards: first line, extra material, checkout check, and order note
The final notes are not a full customer-service script and should not be sent as one giant message. The first opens the conversation, the second adds references, the third checks the link before payment, and the fourth becomes the order note. Replace the blanks with the actual character, link, SKU wording, and confirmed details.

- First line: I want to make [character/version] Kig skin for [scene]. I have references and an existing-item list, and I want to confirm whether this direction can be discussed.
- Extra material: I can send front/back references, exposed areas, shell/tone references, measurements, endpoint needs, and access-opening questions. [Items] are still pending maker judgment.
- Checkout check: I found [title/link]. Please confirm whether it is the main item, deposit, final payment, add-on, special listing, or display page. Selected SKU wording [ ]; search entry [ ]; product-page display [ ]; discounted page state [ ]; maker-confirmed delivered total [ ]; lead time and rework terms [ ].
- Order note: character/version [ ]; main item [ ]; SKU wording [ ]; tone/measurements [ ]; hands/feet/access [ ]; inclusions/exclusions [ ]; delivered total/shipping [ ]; add-on mapping [ ]; preorder/in-stock and after-sales [ ]; photo permission [ ].
Reading notes
- This guide organizes order-brief information only; shop choice, payment nodes, and page context still rely on the reader’s own confirmation and order notes, not seller rankings, payment advice, or reusable price anchors.
- Search entries, product-page displays, discounted page states, SKU wording, and maker-confirmed totals must stay separate; listing claims and page copy are clues, not tests or guarantees.
- All-inclusive wording, deposits, final payments, add-ons, special listings, display pages, and top-ups must be separated before order notes are written.
Continue reading
The Night Before Your First Kig: What Comes After a Saved Image?
The image that keeps reopening in a late-night favorites folder usually arrives before the shopping cart. The useful question is not ‘what should I buy immediately?’ but what held the eye: the character face, the complete silhouette, the mood of the photograph, or the thought of meeting the character in a real place. That answer changes where the first budget belongs—perhaps a head shell, a Kig skin, an outfit, a short try-on, or a low-pressure studio session.
Continue reading →Kig Budget Calculator: After the Low-Price Spark, How Far Should This Order Go?
A Kig photograph, a character idea, and a low entry price can make the order feel suddenly reachable. The budget page separates search-result prices, selected options, payment stages, top-up links, storage, rework, and event logistics, then leaves four sensible outcomes: a trial, custom planning, a clearer order, or saving the idea for later.
Continue reading →Before Payment: Read the Photo, Product Page, and Maker Reply Separately
A strong Kig photo, a low entry price, or one happy review can make an order immediately tempting. The purpose here is not to kill that interest, but to keep each claim within its proper scope: what the main product and selected SKU say, what each top-up link belongs to, whether additions are separate, when lead time starts, and how after-sales is described. The result is not a shop ranking; it is a clearer maker question and a calmer delivery review.
Continue reading →

