EDIT: THIS IS NOT THE SAME PROJECT THAT SOLVES VITALII'S 0->1000 PROBLEM, THIS IS THE PROJECT THAT LEAD TO HIM GIVING ME IT.
this is a chrome extension that helps turn linkedin-style drafts into x-native posts.
the goal is simple:
- keep your core message
- remove the linkedin-coded tone
- make it feel like it belongs on x
i saw a post on x from emily about the stan hackathon and how she hired 4 engineers from it.
what caught my attention was a reply saying the hiring strategy was awesome, but they almost didn't read the post because of the linkedin formatting.
that was the unlock for me.
so i built this chrome extension to make the x version feel native while still fitting inside stanley by stan.store.
- watches the draft inside stanley thread pages
- generates an x version side-by-side
- supports unverified (280 chars) and verified (25k chars) modes
- gives rewrite controls (shorter/longer + custom prompt)
- supports lowercase-only rewriting
- keeps revision history and lets you move between versions
- lets you edit the x text directly
- supports image attachments in x mode
- opens x compose and pre-fills the post text
- has an x-style preview modal so you can see the post before publishing
- linkedin/x mode toggle in the footer
- x-style header (name, handle, timestamp, x icon)
- compact toolbar with rewrite + revision navigation
- quick chips for shorter and longer rewrites
- custom prompt input
- press enter to submit rewrite
- keeps output aligned to your current mode limits
- unverified:
current/280 chars - verified:
current/25k chars - verified toggle updates the limit and generation behavior
- add up to 4 images
- remove images from the grid
- x preview modal shows text + attached images in tweet-like layout
- post button opens
https://x.com/compose/post - extension fills the compose textbox with your generated text
- it does not auto-post
- this is still limited because it does not truly understand your full x account context or post history the way stanley for linkedin understands linkedin context.
- on x, content quality usually matters more than formatting alone, so formatting fixes by themselves are not enough.
- x culture is very different from linkedin, and i am still actively learning and refining that translation layer.
you only need 2 terminals: one for the extension and one for the backend.
pnpm installcreate a .env in the project root:
GROQ_API_KEY=your_groq_key_hereoptional:
GROQ_MODEL=llama-3.3-70b-versatile
PORT=8787pnpm backend:devin a new terminal:
pnpm dev- open
chrome://extensions - enable developer mode
- click "load unpacked"
- select
.output/chrome-mv3-dev
- go to stanley.stan.store
- write or generate your linkedin draft
- switch to x mode
- review/edit/rewrite
- preview post
- click post to open x compose
- start with your full linkedin draft in stanley
- switch to x mode and let it generate once
- use shorter/longer rewrite chips to tune voice
- use lowercase-only toggle when you want a more cracked style
- manually edit final lines before posting
- if you do not set
groq_api_key, the app can still run in mock mode - all x drafts are editable in-place
- refresh behavior uses saved draft/revision state per thread

