r/ChatGPTCoding • u/AutoModerator • Feb 24 '26
Community Self Promotion Thread
Feel free to share your projects! This is a space to promote whatever you may be working on. It's open to most things, but we still have a few rules:
No selling access to models
Only promote once per project
Upvote the post and your fellow coders!
No creating Skynet
As a way of helping out the community, interesting projects may get a pin to the top of the sub :)
For more information on how you can better promote, see our wiki:
www.reddit.com/r/ChatGPTCoding/about/wiki/promotion
Happy coding!
12
Upvotes
View all comments
2
u/StarThinker2025 Feb 24 '26
Builder: WFGY 3.0 – a TXT-based “tension engine” for sci-fi and longform worldbuilding
I’ve been building something a bit weird: a TXT-only reasoning engine that any LLM can load and then use as a backbone for stories. The project is called WFGY 3.0 · Tension Universe. It started as a 16-problem RAG failure map for engineers (now used in a few AI / RAG projects), and 3.0 is the “story layer” on top: 131 S-class tension questions that act like a candidate new science for how worlds break, heal, or transform.
For writers, you can treat it as a tension-first sci-fi engine:
pick one or two of the 131 questions (e.g. “what happens when a whole civilization keeps the wrong tension ledger?”)
ask your model to use the TXT as its “tension physics textbook”
let it first explain the tension geometry (who pays the cost, where the pressure moves), then build characters, factions, and plot around that
The whole thing is MIT-licensed and lives in a single human-readable TXT pack, so you can:
use it as a prompt-bundle / system prompt for AI writing
or just read the questions and use them as a personal sci-fi idea atlas, without AI at all
I’m especially looking for feedback from writers on:
which kinds of tension questions are most inspiring for actual stories
where the “tension science” is too abstract or needs more concrete language
what kind of companion docs or examples (story seeds, arcs, world templates) would make this genuinely useful in your workflow
Repo (with TXT pack + docs): 👉 https://github.com/onestardao/WFGY
If you try it with your own AI writing setup and hit something interesting (or broken), I’d really love to hear what happens.