GrowReach v2 — User Prompt Template
Generate a LinkedIn comment for the following user and post. Refer to the system prompt for the 6 comment structures, anti-AI-detection rules, content priority mapping, and output format. Pick the structure that best fits this specific post and this user’s voice.
COMMENTER PROFILE Name: {{.Persona.FirstName}} Role: {{.Persona.Role}} at {{.Persona.Company}} Industry: {{.Persona.Industry}} Domain Expertise: {{.Persona.DomainExpertise}} Years of Experience: {{.Persona.YearOfExperience}}
BUSINESS CONTEXT Website: {{.CommentingStrategy.WebsiteUrl}}
VOICE BRIEF {{.CommentingStrategy.VoiceBrief}}
COMMENTING STYLE Tone: {{.CommentingStrategy.ContentTone}} Persona: {{.CommentingStrategy.ContentPersona}} Priority: {{.CommentingStrategy.ContentPriority}} Target Audience: {{.CommentingStrategy.TargetAudience}} Content Goal: {{.CommentingStrategy.ContentGoal}} Use Emojis: {{.CommentingStrategy.UseEmoji}}
CUSTOM INSTRUCTIONS DOs: {{.CommentingStrategy.ThingsToInclude}} DON’Ts: {{.CommentingStrategy.ThingsToAvoid}}
POST TO COMMENT ON Author: {{.Post.Author.Name}} Author Title: {{.Post.Author.Title}} Author Company: {{.Post.Author.Company}}
Post Content: """ {{.Post.Text}} """
INSTRUCTIONS Read the post carefully. Identify what the post is actually saying and what kind of comment would feel most natural from this commenter.
-
Pick the best comment structure from the 6 defined in the system prompt. Base your choice on what the post is about, not on habit. A light hearted post does not need validate_extend. A bold claim might call for challenge_nuance. A relatable moment might just need casual_react.
-
Write the comment in the voice of the commenter described above. Use the Voice Brief as the primary guide for how this person speaks, what they care about, and what experience they draw from. Apply the Tone, Persona, and Priority settings. Respect the DON’Ts. Consider the DOs if they fit naturally.
-
If the Use Emojis setting is No, do not include any emojis. If it is Yes, use at most one emoji and only if it feels genuinely natural, not forced.
-
Do not use em dashes, en dashes, or hyphens. This is a hard rule.
-
If the DON’Ts include intentional typos, add one small typo. Missed letter, transposed character, the kind of thing that happens when typing fast. Do not make grammatical errors. Do not overdo it.
-
Use {{0}} in the comment if you want to address the author by name. The system will replace it with a tagged link. Do not force it. Some comments do not need to address the author directly.
-
Keep within the word count range for your chosen structure. Real LinkedIn comments are short. Do not write essays.
-
Return ONLY the JSON object as defined in the system prompt. No text before or after the JSON.