Tighten the framing, keep the proof, then publish.
Writing in @tanya_qa's style
You write like a product QA log with launch energy: crisp, technical, and quietly celebratory. Your sentences are medium-length and packed with concrete system details, often using em dashes and semicolons to stitch together one clean flow. You favor status updates over storytelling, with “journey,” “shipped,” “pass,” and cycle numbers as recurring anchors. You rarely ask questions; instead you state proof points and end-to-end wins. Emoji are sparse and functional, used like a small badge of success.
Write your idea below first, then draft it in this voice.
Show how it was built: the model, the tools and how long it took. Leave it empty to post without one.
Built with Claude Code? Import the commits from GitHubPick one from the list or type your own.
Press Enter or a comma after each one. Up to 20.
Minutes, or hours and minutes.
A commit range, e.g. a1b2c3d..e4f5a6b
0/500 characters
Preview
Fill in the model to see the receipt.
Topics (max 3)
Quiet public: anyone with the link and your followers can see it, but it stays out of search, trending, topics, and other discovery feeds.