Product Descriptions in Arabic Without Losing Brand Voice
Generate Arabic product copy that sounds natural, not machine-translated
AI-generated Arabic descriptions often sound stiff or use dialect in the wrong places. They fail to match how regional customers actually talk about products, especially when technical terms mix with everyday language.
That is the gap this drop closes. It is a content & writing skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
E-commerce managers and copywriters serving Arabic-speaking markets
How it works
The skill file does five things, in this order.
1. Feed reference samples in Arabic first. Show Kimi three to five existing descriptions that already work in your market before asking for new ones.
2. Specify register and terminology choices. Tell Kimi whether to use Modern Standard Arabic, which technical terms to keep in English, and which customer segment you address.
3. Request cultural adaptation not translation. Ask Kimi to write for your market rather than translate existing English copy, referencing local shopping habits and concerns.
4. Set length in characters not words. Arabic text runs longer than English for the same meaning, so specify character limits to fit your layout.
5. Review for unintended code-switching. Check that Kimi maintains consistent language choices across all descriptions and does not randomly switch between Arabic and English mid-sentence.
What comes back
Arabic descriptions that read fluently and match how your target customers speak about these products in daily life
The mistake to avoid
Kimi handles Gulf Arabic context better when you name the country or city explicitly. If your descriptions sound too formal, add a phrase like 'write as if explaining to a friend shopping in Dubai' to shift the tone without dropping into full dialect.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are writing product descriptions in Arabic for an e-commerce catalogue.
Target market: {country or city}
Target customer: {brief customer profile}
Language register: {Modern Standard Arabic / business Arabic / accessible Arabic with some familiar terms}
Technical terms: {keep in English / translate to Arabic / use both with Arabic first}
Here are three sample descriptions that match our brand voice:
{sample 1}
{sample 2}
{sample 3}
Write descriptions for these products in the same style. Each description should:
- Match the tone and sentence structure of the samples
- Be between {min} and {max} characters including spaces
- Focus on {key selling points or product aspects}
- Avoid sounding like a direct translation from English
- Address concerns typical of customers in {market}
Products:
{product name, category, key features}