Brand Voice Guidelines & Jargon Elimination

What it does

Brand Voice Guidelines & Jargon Elimination is a Cursor skill: a SKILL.md playbook that AgenticKit installs at .cursor/skills/brand-voice-guide. Cursor's agent loads it when the task matches the skill description, instead of stuffing the same rules into every chat.

Establishing a concise, direct brand voice for developer products: eliminate fluff, avoid corporate buzzwords, and communicate with technical precision.

Clear tone rules, banned buzzwords, technical accuracy, and personality. The file is domain knowledge, not a slash macro. You do not type it. The agent reads it when the job is brand voice guide.

Why it exists

Default Cursor has no memory of how your team ships positioning, copy, and launch assets. Founders paste the same conventions into chat, then watch the model drift on the next turn. This skill exists so those conventions live on disk and load only when relevant.

It ships in the Marketing Kit. It is wired to the Brand Identity & Tone Lead (brand-voice) and Direct Response Copywriter (copywriter) agents. It is wired to the /define-brand-voice: Brand Voice & Style Guide Creator and /landing-page: High-Converting Landing Page Copy Architect commands. That graph is the point: the skill is the standard, the agent is the role, the command is the trigger.

When to use it

• Use Brand Voice Guidelines & Jargon Elimination when the work is specifically about clear tone rules, banned buzzwords, technical accuracy, and personality.
• Load it before a long session that will touch this surface more than once. A one-line edit does not need the full playbook.
• Use it when you are writing something a buyer will see: landing copy, launch posts, SEO pages, or positioning docs.

When not to use it

• Do not treat the skill as a replacement for a slash command. Skills teach. Commands run a pipeline.
• Do not paste the whole SKILL.md into chat. If Cursor is not loading it, fix the description or invoke the matching command.
• Do not use it to generate spam or spray the same launch post across every channel.

Example workflow

1. Install the Marketing Kit so .cursor/skills/brand-voice-guide lands in the repo.
2. Open a new Cursor agent chat pointed at the files this skill governs.
3. Ask the Brand Identity & Tone Lead (brand-voice) to read the skill, or run /define-brand-voice: Brand Voice & Style Guide Creator.
4. Review the first artifact against the practices below. If it violates one, stop and correct the file. Do not prompt 'just finish it'.
5. Commit the skill-guided files with the rest of the slice so the next session inherits the same standard.

Example usage

Example prompt: "Read .cursor/skills/brand-voice-guide and apply it to this change. Do not invent extra conventions."

Or trigger the pipeline: /define-brand-voice: Brand Voice & Style Guide Creator. That command is written to load this skill.

Check the output against: Ban vague buzzwords: 'revolutionary', 'game-changing', 'synergy', 'seamless'

Example output

• The skill itself does not write a single output file. It changes what the agent is allowed to produce in positioning, copy, and launch assets.
• When you run /define-brand-voice: Brand Voice & Style Guide Creator, expect repo files plus notes under docs/, not a chat-only answer.

Best practices

• Ban vague buzzwords: 'revolutionary', 'game-changing', 'synergy', 'seamless'
• Write in active voice with strong verbs and clear developer terminology
• Treat developer readers as intelligent peers, not naive sales prospects
• Keep sentences concise and back up claims with concrete facts or code

Common mistakes

• Ignoring "Ban vague buzzwords: 'revolutionary', 'game-changing', 'synergy', 'seamless'" and hoping a later prompt will clean it up.
• Copying the skill into .cursor/rules as always-on. That burns context and fights Cursor's load-on-match design.
• Running two overlapping skills that contradict each other in the same turn.
• Publishing generated copy without a human pass. The skill is a playbook, not a publisher.