Building AI-powered creative systems. Founder & Head of Product @thepromptlab_ai

DECENTRALIZED WEBπŸ₯·πŸΎ
Based in Africa
Ada spent two years being told that the work she did from home wasn't really work. Then one payment changed how her family saw the room behind her door. I wrote Ada's story for the #CashiWritingContest. Substack link substack.com/@auditorsubveni…
1
1
2
38
Talk to Primo Now on Telegram @ PromptLabPrimoBot
2
25
A few days ago, I shared how I was moving Primo, the AI assistant inside @thepromptlab_ai, from the website into Telegram. That started as a simple bot integration. It became a much deeper systems problem. I didn't want to build another chatbot with another personality. I wanted the same Primo intelligence to work across different environments without duplicating the whole system. So I reworked the architecture around a shared Primo core. The basic flow now looks like: Primo Core ↓ Website Primo Telegram Primo The Telegram side runs through a server-side webhook that receives Telegram updates, handles routing and context, passes the relevant conversation into Primo's AI layer, persists messages, and returns the response through Telegram. I also had to solve identity. Telegram usernames aren't enough to know who a Prompt Lab creator is, so I built a private verification flow using Creator IDs and a one-time Workspace verification code. That lets Primo securely associate a Telegram account with the correct creator record without trusting whatever identity a user types into a message. Then I started connecting Primo to the actual Prompt Lab systems. Creators. Cohorts. Workspaces. Projects. Spotlight. Studio. Applications. Community information. The important part is that Primo isn't supposed to become the database. The existing systems remain the source of truth. Primo acts as an intelligence layer over them. I also separated Telegram into two contexts. In groups, Primo can answer normal community questions when mentioned. In private DMs, Primo can handle personal creator interactions and access private creator-specific functionality. Personal information like Creator verification, Credits and balance data is never supposed to leak into a group conversation. Then came Primo Credits. I built a separate Credits ledger instead of mixing it with Spotlight Points or Lifetime Points. Credits currently have server-side eligibility checks, publishing rewards, daily earning limits, Studio rewards, Admin authorization and idempotency protection. A creator must have a verified Creator identity and an activated Workspace before Credits can be awarded. So a button isn't deciding whether someone gets rewarded. The server is. I also fixed a separate issue with website Primo. Anonymous visitors were sometimes losing the browser identity used to associate them with their conversation, which caused the infamous: "Conversation not found." I added a server-validated visitor pass as a fallback while keeping conversation ownership checks intact. I then tested the full lifecycle: New conversation β†’ multiple messages β†’ refresh β†’ reopen β†’ continue β†’ new conversation. The conversations now persist correctly and remain isolated. So Primo has gone from: "an AI assistant on my website" to something closer to: **an intelligence layer that can interact with different parts of The Prompt Lab through different interfaces.** There is still more to build. But the foundation is finally starting to look like a real system rather than just a chatbot. Still building. πŸ₯·
Some weeks back, we built Primo, the AI assistant inside @thepromptlab_ai website. It’s already functional there, with its own personality, conversation flow and AI infrastructure. So when I decided I wanted Primo inside our Telegram community, I had a choice: Build another bot from scratch with another personality... Or figure out how to make the same Primo work in another environment. I chose the second. The first step was understanding what we already had. I connected ChatGPT to my Lovable workspace, where The Prompt Lab website lives. From there, I could inspect the existing Primo implementation: the files, AI logic, personality instructions, chat routes, persistence and the way the website communicates with the AI. I didn't want to guess how Primo worked. I wanted to work from the actual implementation. Then I created a new bot through Telegram's BotFather. But creating the bot wasn't the hard part. A Telegram bot is basically just the interface. The real question was: How do I connect that interface to the same AI system already powering Primo on the website? This is where ChatGPT + Lovable became useful. Instead of manually rebuilding everything, I used ChatGPT to reason through the existing Lovable project and then send the implementation instructions directly into Lovable. Lovable could work with the actual project files, while I used ChatGPT to plan the architecture, inspect what already existed and tell Lovable what needed to change. The architecture we started moving toward was basically: Primo AI Core ↓ Website Primo ↓ Telegram Primo Same personality. Same AI foundation. Different interface. The goal is not to create β€œanother Telegram chatbot.” It's to make Primo portable. We then built the Telegram side inside the existing Prompt Lab backend. Telegram sends a message β†’ our webhook receives it β†’ the backend passes the conversation into Primo's AI logic β†’ Primo generates the response β†’ the response is sent back through Telegram. We also added conversation storage so Telegram isn't just a dumb message relay. There were a few things to account for: β€’ Telegram webhook delivery β€’ Bot authentication/secrets β€’ Conversation memory β€’ Duplicate Telegram updates β€’ Private chats vs group mentions β€’ Response formatting β€’ Keeping the website Primo working exactly as it already does And importantly, the Telegram version needed its own context rules because it obviously shouldn't have access to the same website-specific information a logged-in website user might have. The stack/workflow ended up looking roughly like: ChatGPT β†’ planning, inspection & implementation instructions Lovable β†’ builds/edits the Prompt Lab application Supabase β†’ stores Telegram conversations Telegram Bot API β†’ delivers messages Primo AI core β†’ personality + intelligence The Prompt Lab website β†’ the original home of Primo Different tools, one system. And this is where the build currently stands. The Telegram backend has been implemented and the existing website Primo is still intact. The remaining step is connecting the actual Telegram bot token, registering the webhook and testing the full message flow end-to-end. And of course... Lovable credits decided to finish right when we got to that part πŸ˜‚ So I'm currently paused until the credits reset. Once they're back, I'll finish the webhook connection, send Primo its first Telegram message and see how the whole thing behaves in the wild. I'll update you guys when we get there.
3
5
15
256
GOOD MORNING FRIENDS ✌️ Don't let a slow season make you question the value of what you're building. Stay patient. Stay hungry. ❀️
46
10
61
352
Final call before the deadline. πŸ“ I put together a breakdown of @notesystems and the mechanics behind the protocol. If you've been meaning to read it, here's the thread. What did I get right, what did I miss, and what would you explain differently?
I've always found it funny that we complain about taking notes, then panic the moment we need the information we didn't write down. As a student, you can sit through an entire lecture thinking β€œI'll remember this.” Then exam week comes and suddenly you're asking someone for their notebook because the thing you were so sure you'd remember is nowhere in your head. We write things down because we want something important to survive beyond the moment.
3
5
139
GM WORLD πŸ”₯ Never let the pressure to become successful make you forget why you started. Keep the hunger. Keep building. ❀️
74
8
94
568
Replying to @Big_khaddyy
0x9b675ed9a119D0fE98E164142B39c2e5779fDc01
40
Replying to @vyyker
0x9b675ed9a119D0fE98E164142B39c2e5779fDc01
36
Replying to @vyyker
0x9b675ed9a119D0fE98E164142B39c2e5779fDc01
53
Replying to @Sonicdyor
All done BdHXmGjX5cPQ5zPcDS6117Dv6Pc4j37n2E9uVqUs8H25
16
WHAT IS LIFE WITHOUT $GARRI WHAT A LIFE SAVER Am I late to the show?? 0xD127cdeB01B2b87C793A5aA11312D9E959dFfbE0
7
4
14
493
Crypto iGaming is a massive market, but most of the activity happens behind layers of noise. @Circusfyi is basically building the lens. Casino flows. Hot wallets. Sports odds. Streamer activity. Just tested the new Telegram bot. 🎯
The Circus Telegram Bot is now open to everyone πŸ₯³ To celebrate, we're giving away $1,000 (10 winners Γ— $100). How to enter: 1️⃣ Open @CircusFYIBot on Telegram and send /start 2️⃣ Run /odds <site> <sport> and screenshot the result 3️⃣ Quote this post with your screenshot Good luck! πŸ€
2
1
13
178
Let’s see what Circus is cooking 🎯 Circus, show me the number πŸ”₯πŸ”₯πŸ”₯πŸ”₯
20
SATURDAY πŸ”₯ The weekend is here. Made something yesterday that I’m genuinely proud of. Built with intention. Now I’d love for you to see it. Check out my entry below, drop a like, and let me know what you think. ❀️
I've always found it funny that we complain about taking notes, then panic the moment we need the information we didn't write down. As a student, you can sit through an entire lecture thinking β€œI'll remember this.” Then exam week comes and suddenly you're asking someone for their notebook because the thing you were so sure you'd remember is nowhere in your head. We write things down because we want something important to survive beyond the moment.
11
5
23
282
And one distinction matters before we end: $NOTE is not the note. The structured product itself is built around USDG and stock tokens. $NOTE is the protocol token, with its own role in the broader Note Systems ecosystem. You don't buy $NOTE to receive the coupon from a structured note. As of September 2026, the structured-note product is still in its testnet phase while $NOTE is already live on Robinhood Chain. That's an important distinction when looking at what exists today versus what the protocol is building toward. CA: 0xc4f730335Fb9e439ca5552f7b52B8E638c4245B0 So when I say β€œNote Systems,” I'm talking about the protocol and the financial product it's building. When I say $NOTE, I'm talking about the token powering the ecosystem around it. The bigger idea is the part worth watching: taking a financial product that has traditionally lived behind a bank's walls and rebuilding its core mechanics as an on-chain market. If you're interested in understanding where structured products, tokenized equities and on-chain markets intersect, follow @notesystems, explore what they're building, and join the community. $NOTE
1
31
106
And this is what β€œon-chain” actually means here. It isn't simply putting a stock on a blockchain and calling the result a new financial product. The stock token is an ingredient. The structured note is the product. Note Systems is putting the matching, prefunding, observation rules, transferable positions and settlement logic around that product on-chain. The goal is to replace the traditional issuer-and-warehouse architecture with two-sided participation and escrowed capital. But on-chain doesn't mean risk disappears. COUPON can lose principal if the maturity barrier is breached. SHIELD can pay for protection that never ends up paying out. Oracle or calendar failures, smart-contract vulnerabilities, stock-token restrictions, liquidity constraints and the underlying token infrastructure can still matter. The point isn't to remove risk. It's to make the machinery around the risk programmable and visible.
1
31
105
This is where COUPON and SHIELD come in. COUPON is the side bringing USDG and looking for the scheduled income. It accepts the possibility that, if the stock finishes below the barrier at maturity, it may receive the stock instead of getting its principal back in cash. SHIELD is the stock-token holder. It puts its stock into escrow alongside the USDG required to cover the maximum possible coupon liability. In exchange, it gets crash protection whose payout is tied to the barrier condition. One side wants income. The other wants protection. That's the market Note Systems is trying to put on-chain.
1
33
120
Now ask the obvious question: Why would anyone want a deal like that? For the buyer, the attraction is the scheduled income. They are accepting a specific kind of equity downside in exchange for that income, while also giving up some of the upside because the note can be called early. For the stock holder on the other side, the trade looks different. They already own the stock and may want protection against a serious crash. They're willing to give up some economics through the coupons in exchange for that protection. That difference in incentives is the heart of the product.
1
33
124
And that idea is actually what makes the word β€œnote” interesting. A note can be a reminder, an instruction, a record, a promise, or simply a way of preserving information. Over time, that same idea found its way into finance, where a β€œnote” became something much more precise: an agreement defining how money and risk move between people. Then finance made the idea considerably more complicated.
1
35
198
I've always found it funny that we complain about taking notes, then panic the moment we need the information we didn't write down. As a student, you can sit through an entire lecture thinking β€œI'll remember this.” Then exam week comes and suddenly you're asking someone for their notebook because the thing you were so sure you'd remember is nowhere in your head. We write things down because we want something important to survive beyond the moment.
30
54
91
1,454
Safe to say my funds remained untouched during the heist. Thank Goodness🀧
🚨BREAKING: BITGET POTENTIALLY HACKED FOR OVER $100M
1
9
211
Some weeks back, we built Primo, the AI assistant inside @thepromptlab_ai website. It’s already functional there, with its own personality, conversation flow and AI infrastructure. So when I decided I wanted Primo inside our Telegram community, I had a choice: Build another bot from scratch with another personality... Or figure out how to make the same Primo work in another environment. I chose the second. The first step was understanding what we already had. I connected ChatGPT to my Lovable workspace, where The Prompt Lab website lives. From there, I could inspect the existing Primo implementation: the files, AI logic, personality instructions, chat routes, persistence and the way the website communicates with the AI. I didn't want to guess how Primo worked. I wanted to work from the actual implementation. Then I created a new bot through Telegram's BotFather. But creating the bot wasn't the hard part. A Telegram bot is basically just the interface. The real question was: How do I connect that interface to the same AI system already powering Primo on the website? This is where ChatGPT + Lovable became useful. Instead of manually rebuilding everything, I used ChatGPT to reason through the existing Lovable project and then send the implementation instructions directly into Lovable. Lovable could work with the actual project files, while I used ChatGPT to plan the architecture, inspect what already existed and tell Lovable what needed to change. The architecture we started moving toward was basically: Primo AI Core ↓ Website Primo ↓ Telegram Primo Same personality. Same AI foundation. Different interface. The goal is not to create β€œanother Telegram chatbot.” It's to make Primo portable. We then built the Telegram side inside the existing Prompt Lab backend. Telegram sends a message β†’ our webhook receives it β†’ the backend passes the conversation into Primo's AI logic β†’ Primo generates the response β†’ the response is sent back through Telegram. We also added conversation storage so Telegram isn't just a dumb message relay. There were a few things to account for: β€’ Telegram webhook delivery β€’ Bot authentication/secrets β€’ Conversation memory β€’ Duplicate Telegram updates β€’ Private chats vs group mentions β€’ Response formatting β€’ Keeping the website Primo working exactly as it already does And importantly, the Telegram version needed its own context rules because it obviously shouldn't have access to the same website-specific information a logged-in website user might have. The stack/workflow ended up looking roughly like: ChatGPT β†’ planning, inspection & implementation instructions Lovable β†’ builds/edits the Prompt Lab application Supabase β†’ stores Telegram conversations Telegram Bot API β†’ delivers messages Primo AI core β†’ personality + intelligence The Prompt Lab website β†’ the original home of Primo Different tools, one system. And this is where the build currently stands. The Telegram backend has been implemented and the existing website Primo is still intact. The remaining step is connecting the actual Telegram bot token, registering the webhook and testing the full message flow end-to-end. And of course... Lovable credits decided to finish right when we got to that part πŸ˜‚ So I'm currently paused until the credits reset. Once they're back, I'll finish the webhook connection, send Primo its first Telegram message and see how the whole thing behaves in the wild. I'll update you guys when we get there.
4
4
16
503
Almost done with one of the craziest Ai workflows I have ever had. will be telling you details in my next tweet. Honestly it's mind-blowing
Friday πŸ’› One of the safest investments you can make is becoming someone your future self can depend on. Invest in yourself. ❀️
6
15
222
Friday πŸ’› One of the safest investments you can make is becoming someone your future self can depend on. Invest in yourself. ❀️
72
5
83
676
Una dey talk Sha . This is the best out there, by milesssss. Argue with yours.
here’s what my Grokbot-style character looks like bet yours isn’t better, prompt in the Quoted post.
7
2
18
314
Thursday 🀍 Don't let a bad chapter convince you it's a bad story.
70
10
88
517
GOOD EVENING PEOPLE πŸ”₯πŸ”₯πŸ”₯ Can your circle of friends be called circumference??
26
1
45
598
Mine is more cuter than any I have seen today ✌️
here’s what my Grokbot-style character looks like bet yours isn’t better (prompt in cs)
17
4
32
351
I came across @kinbexapp and honestly The β€œall your Web3 tools in one place” part isn’t what caught my attention We’ve heard that pitch before What caught my attention is the idea of making reputation part of the trading experience They’re building around a Caller Leaderboard and a simple principle Let the record speak Instead of someone making 50 calls on the timeline and only talking about the 3 that worked Imagine having the history sitting there The calls The performance The consistency The track record Now reputation isn’t just about how loud you are It becomes about what you’ve actually done And that gets more interesting when you look at the rest of what Kinbex is building toward A wallet Market discovery Social Research Trading Project discovery Launches AI Not as separate tools that barely know each other But as one connected ecosystem where discovery can lead into research, conversation and eventually action Kinbex is still early, so I’m more interested in watching how they execute this than repeating the vision But this is one of those projects I’ll be keeping an eye on πŸ‘€
10
7
21
245
Replying to @LeveX
My Entry @LeveX Let’s see… πŸ€”
15
27
44
558
WEDNESDAY 🀍 Never become so used to surviving that you forget you were meant to build a life you actually want.
71
12
82
514
Replying to @Canborsa_DEX
Everyone logged off at 4PM. Canbo: β€œI’ll keep going.” πŸ˜‚
Apparently 4PM means β€œgo home” for everyone else πŸ˜‚ Canbo didn’t get the memo. @Canborsa_DEX is building a non-custodial perpetual DEX where you can access crypto, stocks, commodities and indices from one platform, 24/7. So yeah… Canbo is still working.
1
11
Apparently 4PM means β€œgo home” for everyone else πŸ˜‚ Canbo didn’t get the memo. @Canborsa_DEX is building a non-custodial perpetual DEX where you can access crypto, stocks, commodities and indices from one platform, 24/7. So yeah… Canbo is still working.
It's time to have some fun πŸ€ͺ Let's use Grok to put the Canborsa mascot in the funniest situations you can imagine! πŸ’° 500 canton-network:native for the 5 best works 1) In the comments, hit attach media and generate your image with Grok 2) Post your result below 3) QRT this post with a short line on what Canborsa is That's it, let's see who comes up with the best one πŸ‘€
8
4
21
260
TUESDAY 🀍 Some dreams take longer than expected. That doesn't make them less worth chasing. Never give up on what still matters to you. ❀️
78
5
96
524
Replying to @TeaonaX @gemblr
All Done GGP1JYA4Dvc1KeJDjd6seKvzjnPkZvwQkg472nwTPM6d
18
Some words of wisdom before I go to bed. If you are not happy, you are sad. If you are not tall, you are short. If you are not rich, you are poor. If you are not awake, you are asleep. If you are not hungry, you are full. If you are not here, you are there. Thank you for coming to my TED Talk. Goodnight.
15
4
32
263
What's a Monday without a win. It's La Peace ✌️
My entry for the @MoonlitRuna #MoonlitCreator contest. THE TABLE πŸŒ™ An original piece of Moonlit lore exploring the Principle of Creation through a simple wooden table shaped by the hands of those who passed through it. A story about what we leave behind, and the space we leave for what comes next. It was fun working on this.
4
1
13
236
I finally put a small position behind one of my forecasts. The question: Will BTC reach $86,000 on September 21? At the time I entered, BTC was hovering just below $86K and the market was around the 50/50 range. My position: β†’ YES β†’ 2 shares β†’ $1 total Not because I think I β€œknow” what BTC will do. The interesting part is testing whether my reasoning actually holds up against the market. If BTC closes above $86K, the forecast gets validated. If it doesn't, I get another data point. Either way, I'll record the result. That's how I want to use prediction markets: less guessing, more testing. Tracking it on @wahoopredict: wahoopredict.com?r=nodeanony…
4
4
12
195