Style Profiles

IntentEmoji ships with six built-in style profiles. Each profile defines a density range, preload ratio target, and tone guidelines that control how emoji is placed in text. Profiles can be selected per request via the API, SDK, or extension.

Profile Overview

Profile	Density	Preload Ratio	Use Case
`casual`	High (1 per 1-2 sentences)	50-60%	Social media, chat, personal messages
`professional`	Moderate (1 per 2-4 sentences)	70-80%	Business email, Slack, team updates
`technical`	Low (1 per section or heading)	80-90%	Documentation, READMEs, changelogs
`marketing`	High (1 per 1-2 sentences)	60-70%	Landing pages, ads, newsletters
`educational`	Moderate (1 per 2-3 sentences)	75-85%	Tutorials, courses, explainers
`ai_output`	Moderate (1 per 2-4 sentences)	70-80%	Chatbot responses, generated summaries

casual

Casual

Density: High Preload: 50-60% Emoji per sentence: 1 per 1-2

The casual profile is designed for informal, expressive communication. Social media posts, text messages, Discord servers, casual Slack channels. Emoji density is high because the audience expects and responds to it. The preload ratio is lower than other profiles because postloaded emoji is natural in conversational text (reactions, punchlines, emphasis).

Tone Guidelines

Emoji should feel natural and spontaneous, not calculated
Mix of preloaded (to lead thoughts) and postloaded (to react)
Common emoji preferred over obscure ones
Multiple emoji per message is acceptable
Inline emoji can be used for emphasis on individual words

Example

Input:

Just finished the redesign. The new color scheme looks way better. Still need to fix the mobile nav though.

Output:

✨ Just finished the redesign. The new color scheme looks way better 🔥 Still need to fix the mobile nav though 🛠️

professional

Professional

Density: Moderate Preload: 70-80% Emoji per sentence: 1 per 2-4

The professional profile is for workplace communication where emoji is welcome but restraint is expected. Team updates in Slack, internal emails, project status reports, release announcements. Emoji adds visual structure without undermining the tone.

Tone Guidelines

Emoji should feel intentional and purposeful, never frivolous
Strong preference for preloaded position (leading thoughts)
Avoid playful or ambiguous emoji (no 😂, 🤪, 💀)
Prefer structural emoji: checkmarks, arrows, categories
One emoji per paragraph or key point, not per sentence

Example

Input:

Q1 results are in. Revenue exceeded projections by 12%. The sales team closed 34 new accounts. We're expanding the engineering team by 5 headcount next quarter.

Output:

📊 Q1 results are in. Revenue exceeded projections by 12%.

💼 The sales team closed 34 new accounts.

🚀 We're expanding the engineering team by 5 headcount next quarter.

technical

Technical

Density: Low Preload: 80-90% Emoji per sentence: 1 per section

The technical profile uses emoji sparingly and almost exclusively in the preload position. Its purpose is structural: creating visual anchors in dense content so readers can scan quickly. Documentation, API guides, changelogs, and READMEs benefit from this approach without feeling casual.

Tone Guidelines

Emoji appears at section headings and key transitions only
Nearly all emoji is preloaded (section markers)
Prefer semantic emoji that maps to the content type (📦 for packages, 🔑 for auth, ⚠️ for warnings)
Never use emoji inside code blocks or inline code
Consistency is critical. Same emoji for same concept throughout

Example

Input:

Installation

Install the package via npm. Requires Node.js 18 or higher.

Configuration

Set your API key as an environment variable. The client reads from INTENTEMOJI_API_KEY by default.

Usage

Import the client and call the enhance method with your text.

Output:

📦 Installation

Install the package via npm. Requires Node.js 18 or higher.

🔧 Configuration

Set your API key as an environment variable. The client reads from INTENTEMOJI_API_KEY by default.

⚡ Usage

Import the client and call the enhance method with your text.

marketing

Marketing

Density: High Preload: 60-70% Emoji per sentence: 1 per 1-2

The marketing profile maximizes visual impact and engagement. Landing pages, email subject lines, ad copy, newsletter headers. Emoji density is high because the content competes for attention in noisy environments. The preload ratio is moderate because postloaded emoji can serve as effective punctuation in short-form persuasive copy.

Tone Guidelines

Emoji should amplify urgency, excitement, or value
Preloaded emoji frames benefits. Postloaded emoji punctuates claims.
Use high-energy emoji: 🚀, 🔥, ✨, 💡, ⚡
Email subject lines: always preloaded (first character captures the scan)
A/B test density. Some audiences respond to more, some to less.

Example

Input:

Introducing our fastest plan ever. Unlimited API calls. Custom profiles. Dedicated support. Available now.

Output:

⚡ Introducing our fastest plan ever.
✅ Unlimited API calls. Custom profiles. Dedicated support.
🚀 Available now.

educational

Educational

Density: Moderate Preload: 75-85% Emoji per sentence: 1 per 2-3

The educational profile creates learning-friendly content. Tutorials, course materials, explainers, onboarding flows. Emoji serves as cognitive scaffolding, helping learners identify concepts, steps, and key takeaways. Preloading is strongly preferred because it helps the reader anticipate what kind of information is coming.

Tone Guidelines

Emoji marks concept types: 💡 for insights, ⚠️ for pitfalls, ✅ for best practices
Consistent emoji-to-concept mapping throughout a document
Preloaded emoji helps learners scan and revisit specific sections
Avoid decorative emoji. Every emoji should carry meaning.
Step-by-step instructions benefit from numbered emoji (1️⃣, 2️⃣, 3️⃣) or action emoji

Example

Input:

Variables store data that your program can use later. Think of a variable as a labeled box. You put something in the box, give it a name, and then refer to it by that name whenever you need it. Important: variable names are case-sensitive in most languages.

Output:

📦 Variables store data that your program can use later. Think of a variable as a labeled box. You put something in the box, give it a name, and refer to it by that name whenever you need it.

⚠️ Variable names are case-sensitive in most languages.

ai_output

AI Output

Density: Moderate Preload: 70-80% Emoji per sentence: 1 per 2-4

The ai_output profile is specifically designed to make LLM-generated text feel more human and scannable. Chatbot responses, AI-generated summaries, automated reports, and assistant interfaces. Without emoji, AI output tends to feel flat, correct, and forgettable. This profile adds just enough visual structure to break the "wall of competent text" effect.

Tone Guidelines

Emoji should break up long responses into scannable sections
Preloaded emoji at the start of key paragraphs or list items
Avoid over-using emoji. AI text with too many emoji feels like it is trying too hard.
Match emoji to the subject matter, not the sentiment
For multi-step answers, use emoji as step markers

Example

Input (raw AI output):

There are three main approaches to caching in web applications. The first is browser caching, which stores assets locally on the user's device. The second is CDN caching, which stores content at edge nodes closer to the user. The third is application-level caching, which stores computed results in memory or a dedicated cache store like Redis.

Output:

There are three main approaches to caching in web applications.

🌐 Browser caching stores assets locally on the user's device.

🌍 CDN caching stores content at edge nodes closer to the user.

⚡ Application-level caching stores computed results in memory or a dedicated store like Redis.

Custom Profiles (Enterprise)

Enterprise customers can create custom profiles with specific density ranges, preload ratios, allowed emoji sets, and tone rules. Custom profiles are managed through the API or the team dashboard.

Contact [email protected] for details.