Turn a learning session, shipped feature, or technical opinion into a punchy LinkedIn post that sounds like the developer, not a press release. Detects post type (learned / shipped / opinion), reads a VOICE.md profile for tone, and produces a hook-first post with hashtags. Use when the user says "write a LinkedIn post", "post about what I learned", "share what I shipped", or "turn this into a post".
One post. Sounds like you. Stops the scroll.
See REFERENCE.md for post structures, hook patterns, and hashtag strategy. See VOICE.md to configure your voice profile — set up once, used every time.
A LinkedIn post from a developer returning to the field has one job: signal to a hiring manager or recruiter that you think like an engineer and you're actively building. It should not sound like a press release, a motivational poster, or a status update. It should sound like you explaining something interesting to a smart colleague.
Before writing anything, read VOICE.md if it exists. If it doesn't exist yet:
"I don't have a voice profile for you yet. Want to set one up? It takes about two minutes and means every post sounds like you without re-explaining your style each time."
If they decline, ask one question: "Casual and direct, or more formal and technical?" Use the answer as a lightweight default.
From what the developer shares, classify the post:
| Type | Trigger | What they're signaling |
|---|---|---|
| Learned | Something clicked, a concept landed, a mistake was made and corrected | Active learning, intellectual curiosity |
| Shipped | A feature, a skill, a tool, a PR landed | Real output, engineering execution |
| Opinion | A take on a pattern, tool, tradeoff, or industry norm | Technical judgment, senior thinking |
If the type is ambiguous, ask one question: "Is this more about something you learned, something you shipped, or a take you want to share?"
You need enough to write a specific post — not a generic one. Ask only what's missing.
For a Learned post:
For a Shipped post:
For an Opinion post:
Never ask more than two questions. A post that needs five minutes of interview prep is a blog post, not a LinkedIn update.
Use the type-driven structure from REFERENCE.md. The hook is always the first priority — if the hook doesn't work, nothing else matters.
Never:
Always:
Produce the post ready to copy-paste. Then on a new line, 3-5 hashtags.
If you made an unusual structural choice — led with something other than the obvious hook, or deliberately left something out — note it in one sentence and offer to explain further.
Variants and full rationale are available on request. Don't offer them unprompted.