Revolution Superfix 持妝控油光澤妝前乳金色款

Name: Revolution Superfix 持妝控油光澤妝前乳 金色款
Brand: Revolutionbeauty
SKU: SKU-280267-default
Price: 4 USD
Availability: InStock

Revolution Superfix 持妝控油光澤妝前乳金色款 - Main image

Revolution Superfix Grip Super Glow Primer Gold

$4 ~~$7.99~~ In stock

Category: 臉部妝前乳

認識我們的 Revolution Superglow Grip Primer，一款能讓妝容持久一整天的光澤凝膠配方！

靈感來自我們的 Superfix Grip Primer，這款輕盈配方能打底並牢牢抓住妝容，讓您整天散發光采！注入超強效維生素 C 配方以提亮膚色、玻尿酸以保濕，以及蘆薈以平滑肌膚。

我們愛 SUPERGLOW GRIP PRIMER 的原因：
- 持妝與光澤兼具 – 保濕並提亮膚色，讓底妝完美服貼，牢牢鎖住。
- 抓住光澤，鎖住妝容 - 清爽凝膠配方
- 超強效維生素 C、玻尿酸與蘆薈配方
- 持久妝效的絕佳搭配 – 與 Superfix Glow Mist 完美搭配

如何使用 SUPERGLOW GRIP PRIMER：
取 1-2 泵塗抹於潔淨乾燥的肌膚上。待其乾燥後，再上妝。

純素且無殘忍動物實驗。

Related Products

${"translated":"I Heart Revolution 奶昔草莓打底霜"} Wait, the instruction says to preserve brand names and product names exactly unless source explicitly requires translation. The source is a product name. It says "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So product names should be preserved exactly? But the instruction also says "Product/category names: concise, searchable, and faithful. Do not add marketing adjectives not present in the source." That suggests we might translate product names? But the hard rule says preserve product names exactly. Let me re-read. "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So product names should be preserved exactly. But then the content-type rules say "Product/category names: concise, searchable, and faithful." That might mean if we do translate, we keep it concise. But the hard rule is clear: preserve product names exactly. So we should not translate the product name. But the source is "I Heart Revolution Milkshake Strawberry Whipped Primer" - that is a product name. So we should keep it as is. However, the target language is zh-TW, and the instruction says "Do not translate the brand name 'Revolutionbeauty' unless it has an established localized form." But this is "I Heart Revolution" which is a sub-brand. The instruction says preserve brand names. So we should keep "I Heart Revolution" as is. Also "Milkshake Strawberry Whipped Primer" is part of the product name. So we should keep the entire string unchanged. But wait, the content_type is "商品" (product) and field_name is "商品名称" (product name). The instruction says "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So we must preserve the product name exactly. So the translation should be the same string. But the instruction also says "Localization rules for every target language: Use natural native phrasing for the target language and region." That might apply to descriptions, not product names. Since product names are proper nouns, we keep them. So the output should be the same content. But the instruction says "If source_language and target_language are the same language, return the original content unchanged." Here they are different, so we need to translate? But the hard rule says preserve product names. So we should not translate. However, the content_type rule says "Product/category names: concise, searchable, and faithful." That might mean if we do translate, we keep it concise. But the hard rule overrides. Let me check the example: The instruction says "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So we must preserve the product name exactly. So the translation should be the same string. But then why would they ask to translate? Maybe they want to localize the product name for the target market? But the rule says preserve. So I think we should output the same string. However, the instruction also says "Do not add explanations, notes, disclaimers, markdown, or code fences. Output STRICT JSON only: {"translated":"<translated content>"}" So the translated content should be the same as the source. But wait, the source_language is en-US, target_language is zh-TW. The content is a product name. The rule says preserve product names exactly. So we output the same. But let me double-check: "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So yes, we must preserve. Therefore, the translated content is the same string. But the instruction also says "Localization rules for every target language: Use natural native phrasing for the target language and region." That might apply to other fields, but not to product names. So I'll output the same. But wait, the content_type is "商品" and field_name is "商品名称" - that is product name. So we keep it. Thus, the output is {"translated":"I Heart Revolution Milkshake Strawberry Whipped Primer"} But let me think: Is there any exception? The instruction says "unless the source explicitly requires translation." The source does not explicitly require translation. So we keep. So final answer.<｜end▁of▁thinking｜>{"translated":"I Heart Revolution Milkshake Strawberry Whipped Primer"}$
{"translated":"I Heart Revolution 奶昔草莓打底霜"} Wait, the instruction says to preserve brand names and product names exactly unless source explicitly requires translation. The source is a product name. It says "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So product names should be preserved exactly? But the instruction also says "Product/category names: concise, searchable, and faithful. Do not add marketing adjectives not present in the source." That suggests we might translate product names? But the hard rule says preserve product names exactly. Let me re-read. "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So product names should be preserved exactly. But then the content-type rules say "Product/category names: concise, searchable, and faithful." That might mean if we do translate, we keep it concise. But the hard rule is clear: preserve product names exactly. So we should not translate the product name. But the source is "I Heart Revolution Milkshake Strawberry Whipped Primer" - that is a product name. So we should keep it as is. However, the target language is zh-TW, and the instruction says "Do not translate the brand name 'Revolutionbeauty' unless it has an established localized form." But this is "I Heart Revolution" which is a sub-brand. The instruction says preserve brand names. So we should keep "I Heart Revolution" as is. Also "Milkshake Strawberry Whipped Primer" is part of the product name. So we should keep the entire string unchanged. But wait, the content_type is "商品" (product) and field_name is "商品名称" (product name). The instruction says "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So we must preserve the product name exactly. So the translation should be the same string. But the instruction also says "Localization rules for every target language: Use natural native phrasing for the target language and region." That might apply to descriptions, not product names. Since product names are proper nouns, we keep them. So the output should be the same content. But the instruction says "If source_language and target_language are the same language, return the original content unchanged." Here they are different, so we need to translate? But the hard rule says preserve product names. So we should not translate. However, the content_type rule says "Product/category names: concise, searchable, and faithful." That might mean if we do translate, we keep it concise. But the hard rule overrides. Let me check the example: The instruction says "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So we must preserve the product name exactly. So the translation should be the same string. But then why would they ask to translate? Maybe they want to localize the product name for the target market? But the rule says preserve. So I think we should output the same string. However, the instruction also says "Do not add explanations, notes, disclaimers, markdown, or code fences. Output STRICT JSON only: {"translated":"<translated content>"}" So the translated content should be the same as the source. But wait, the source_language is en-US, target_language is zh-TW. The content is a product name. The rule says preserve product names exactly. So we output the same. But let me double-check: "Preserve brand names, product names, SKUs, model codes, URLs, email addresses, numbers, measurements, sizes, colors, ingredients, compatibility claims, prices, currency symbols, HTML tags, attributes, and JSON keys exactly unless the source explicitly requires translation." So yes, we must preserve. Therefore, the translated content is the same string. But the instruction also says "Localization rules for every target language: Use natural native phrasing for the target language and region." That might apply to other fields, but not to product names. So I'll output the same. But wait, the content_type is "商品" and field_name is "商品名称" - that is product name. So we keep it. Thus, the output is {"translated":"I Heart Revolution Milkshake Strawberry Whipped Primer"} But let me think: Is there any exception? The instruction says "unless the source explicitly requires translation." The source does not explicitly require translation. So we keep. So final answer.<｜end▁of▁thinking｜>{"translated":"I Heart Revolution Milkshake Strawberry Whipped Primer"}
$3.50
Relove Fix Stick 柔焦妝前乳
$2.50
Revolution 保濕妝前乳
$3.50
I Heart Revolution 蜜桃控油妝前乳
$3.00
Relove H2O Hydrate Primer
$2.00
Revolution 色彩校正妝前乳
$3.50
Revolution Pro Blur & Fine Line Filler
$3.50
I Heart Revolution 西瓜保濕妝前乳
$3.00
Revolution 毛孔隱形妝前乳
$3.50
Revolution Pro 即時撫紋筆
$3.50

Revolution Superfix 持妝控油光澤妝前乳 金色款

Related Products

Relove Fix Stick 柔焦妝前乳

Revolution 保濕妝前乳

I Heart Revolution 蜜桃控油妝前乳

Relove H2O Hydrate Primer

Revolution 色彩校正妝前乳

Revolution Pro Blur & Fine Line Filler

I Heart Revolution 西瓜保濕妝前乳

Revolution 毛孔隱形妝前乳

Revolution Pro 即時撫紋筆

Revolution Superfix 持妝控油光澤妝前乳金色款