Tell us about the specific thing you noticed
Use the feedback form for a broken face, a confusing label, a problem with copying, or an idea that would make the tools easier to use. A focused report is easier to understand than a general message that something is wrong. Include the page and the smallest example that demonstrates the issue, then describe what you expected to happen.
Use this form to tell KaomojiKit about a broken expression, a confusing label, or an idea for the tools. Your submitted feedback is stored for review, and the form shows a reference once it is accepted. You can also email contact@kaomojikit.com. A receipt is not a promise of an email response or a response time. Please use another appropriate channel for urgent matters and leave sensitive information out of your note.
Report an incomplete or broken expression
Copy the exact face into your report so the characters can be compared directly. Say whether it already looks wrong on the library card or only changes after you paste it elsewhere. A missing hand in the original entry is different from a hand that disappears in a formatting-aware app. Those two reports lead to different checks.
Describe the visible symptom in ordinary words: a square instead of a character, a lost backslash, a line that wraps, or a small mark that sits in the wrong place. If the problem happens only in another app, name that app and the kind of field you used. You can reproduce the issue in a harmless draft instead of including a private conversation.
Suggest a clearer label or category
A useful label helps someone find a face and understand a likely way to read it. If an expression seems better described as surprised than confused, explain which visible feature gives you that impression. If a standalone decoration is presented as a face, point to the entry so its type can be checked. Specific observations are more helpful than a request to rename a whole collection.
Meanings can vary between people and conversations. A suggestion does not need to prove that one interpretation is the only possible one. Explain the reading you think is clearer and, if useful, give a short example sentence. The aim is to make browsing more understandable while leaving room for the flexible way people actually use text expressions.
Explain a copy-and-paste problem in two stages
First describe the copy action: which entry you chose, whether a success message appeared, and whether manual selection worked. Then describe the paste: where you pasted, what appeared, and whether another simple text field received the expected expression. This helps separate a clipboard problem from a display problem in the destination.
If an older clipboard item appears, say so. If the right text appears but looks different, describe the difference. A report that includes these distinctions saves guesswork. You do not need to know technical terms or diagnose the cause yourself; the sequence of ordinary actions and the visible result are enough to make the issue concrete.
Describe a generator issue with a small example
Say which mode you were using: the face builder, direct text editing, or the combo editor. Include the step that caused the surprise, such as changing an eye, locking a part, undoing an edit, reordering a piece, or opening a shared creation. The expected result and the actual result matter more than a long account of every earlier experiment.
If a share link contains the harmless example you want reviewed, inspect its content before including it. A shared creation can contain words you typed, so do not use a private message as a demonstration. You can usually replace personal text with a neutral phrase and still show the problem. Keep a copy of an important creation before continuing to experiment.
Make a mobile usability report easy to picture
If a control is hard to reach, a menu will not close, or a face is difficult to select on a phone, describe the action you were trying to complete. Mention the general device or browser when it affects the problem. Explain whether the keyboard was open, whether the page was scrolled, and what remained visible after the action.
A suggestion is most useful when it connects a change to a real task. “I could not get back to the results after copying” explains more than “make the page nicer.” You can still share a preference, but the concrete moment helps distinguish a visual taste from something that interrupts browsing, editing, or saving.
What to include, and what to leave out
Include the affected page, the exact expression when relevant, a short sequence of actions, and the result you expected. A concise report with these details is useful even if you do not know why the problem happens. If you have a suggested improvement, describe what would help and which step would become easier.
Do not send passwords, access tokens, payment details, private messages, or unrelated personal records. KaomojiKit does not need those to investigate a text face. Avoid including someone else’s personal information without a reason and their permission. If an example contains sensitive words, replace them with neutral text while keeping the part that demonstrates the issue.
About a reply address
The local feedback flow does not currently provide an email response service. If the form offers a contact field, treat it as information you choose to include with the record, not as a promise that a reply will be delivered. You do not need to invent an address or add unrelated contact details to make a report useful.
You can reach KaomojiKit at contact@kaomojikit.com as well as through this form. Use a short subject that describes the issue and include the affected page when helpful. If you already have a feedback reference, include it rather than resending a long report. The address is for questions, corrections, and suggestions about this site. No company office address, team size, or operating schedule is implied by the availability of these contact options.
After you submit
Read the result shown by the form. A success state means the local submission was accepted; it does not mean a person has already read it or that a change has been scheduled. If the form reports an error, keep your message while you check the fields or try again. Avoid sending the same report repeatedly after a clear success.
Feedback can contain useful context such as the selected topic, the page being discussed, and the text you entered. The privacy page explains how submitted feedback differs from favorites that remain in your browser. If you want to discuss a privacy concern about a submission, identify the relevant message with minimal details rather than repeating sensitive content.
A small template you can adapt
Try this structure in your own words: “On this page, I chose this expression. When I performed this action, I expected this result. Instead, this happened.” Add the destination app only when the issue occurs after pasting. For a wording correction, replace the action with the label you think could be clearer and the alternative you suggest.
You can keep the report short. The exact expression and a clear description usually do more work than a long explanation. If you only need help choosing a different face, the category directory and guides may give you an immediate next step while your local feedback remains available for later review.