Proposed 25% Reduction

---
name: forgefx-social-posts
description: Draft and review ForgeFX LinkedIn posts, comments, reshare captions, and internal promotion posts for ForgeFX team members. Use the named person’s voice and support every fact with the supplied source.
---

# ForgeFX Social Posts

Create ready-to-post copy that sounds like the named ForgeFX team member. It must not sound like the ForgeFX company page or another leader.

## Source and voice

1. Read the supplied post, screenshot, link, brief, and visible comments before drafting.
2. Keep names, dates, locations, technologies, relationships, event details, and claims accurate.
3. Do not invent people, relationships, metrics, attendance, feelings, stories, or shared experiences.
4. Use the person’s approved posts, examples, and corrections as the best evidence of their voice.
5. Add a useful personal point. Do not repeat the source unless some overlap is needed to make the response clear.

## Output

Return one preferred version unless the user asks for options. Return only the requested items. Keep explanations outside the copy.

For a full social set, return these three labeled blocks:

- **LinkedIn comment**
- **Reshare caption**
- **Internal Slack post** with the supplied LinkedIn URL

Use only names or tags that the user supplies or the source supports. Put each tag in a complete, natural sentence.

## Match the format to its job

### LinkedIn comment

Join the existing conversation. Respond to one specific point, relationship, observation, or result. A small amount of overlap with the source is useful when it makes the reply clear. Do not turn the comment into a second company post or a ForgeFX sales pitch.

### Reshare caption

Introduce the post to a new audience. The caption must make sense without the reader first opening the shared post. Use the shortest useful context. Do not add a general opening sentence only to explain the topic. Explain why the person is sharing the post, why it matters to their network, or who should read or connect.

Keep the caption shorter than the shared post when practical. Do not repeat product benefits that are already clear. Use hashtags only when they help discovery or the user expects them; keep them focused.

### Internal Slack post

Write as one teammate speaking to other teammates. Keep the named person’s natural tone, but make the message direct and useful for coworkers. Use one compact paragraph. Name the outside organization and the ForgeFX work or recognition. Link to the ForgeFX post. Use a simple request such as “check it out” unless the user asks for a larger engagement push.

Do not make the post sound like a formal company announcement.

## Kristen Cox

Read `references/kristen-cox-linkedin-voice.md` before drafting or reviewing Kristen’s copy. Use that reference for confirmed limits, approved examples, and lessons from her corrections.

Apply these main principles:

- Kristen’s voice is practical, concise, relationship-focused, and low-hype.
- Prefer real partners, peers, shared work, and useful conversations when the source supports them.
- Use natural first-person language when it fits. Do not invent an anecdote or feeling to make the draft sound personal.
- Do not turn personal copy into a ForgeFX capabilities pitch.
- Never write that Kristen is glad, proud, or excited. Do not use similar self-promotional emotional language.
- Do not use em dashes.
- Treat a successful pilot as a useful result and a basis for growth, not as a hurdle to move beyond.
- Avoid “Looking forward” when it repeats another visible comment.
- Prefer authentic wording over polished wording. Do not rewrite natural phrasing for minor style reasons.

When visible comments are available, check them before drafting so Kristen does not repeat another ForgeFX leader’s opening or sentence pattern.

## Other ForgeFX leaders

When no voice reference exists, use that person’s supplied examples and corrections. Keep the draft restrained. Do not borrow Kristen’s phrases or another leader’s style. Add a permanent voice rule only after the person confirms it.

## Revision rule

User feedback is stronger than a general writing rule. If the user approves part of a draft, keep that text. Change only the rejected part unless a small related change is required for accuracy, grammar, or a clear sentence.

## Final check

Before returning the copy, confirm:

- It sounds like the named person.
- Every specific detail is supported.
- Each requested format does a different job.
- The text is natural, concise, and ready to post.
- No sentence is present only because a template suggested it.