Skip to content
شغّال
Back to the library

Talkstore Begins Now! 🟢 Building to $100K

Day 0127:11:36

Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter

The gist

The stream documents the public start of building Talkstore: a proposed Shopify-specific AI assistant through which merchants could manage products, storefront work, and commerce intelligence conversationally. Its capabilities and possible expansion beyond Shopify are presented as conditional directions, not validated outcomes. Practical work covered Shopify app and development-store setup, Supabase integration and Prisma migrations, secret handling, and repeated diagnosis of session, connection, preview, and Railway deployment problems. The preview and some setup steps worked, and the service later appeared active, but several database, network, build, and deployment issues remained intermittent or unresolved in the covered segments. This led to useful lessons about starting with logs, documenting a stubborn problem, seeking a fresh diagnostic perspective, and reviewing coding-agent compromises rather than accepting a result merely because it works temporarily. The stream also presents a multi-agent command center that separates research and task preparation from implementation, code, security, and compliance review, using dependencies, an adaptive timeline, and human approval gates. Luqman felt this structure accelerated and preserved the context of the work, while still questioning whether every agent was running and visibly logged. He emphasized that authentication, secrets, and nuanced decisions continue to require human intervention, and that task count is a poor measure of difficulty. Work later shifted toward pre-launch distribution: a simple but polished Astro waitlist site kept separate from the Shopify app, with email capture, analytics, social metadata, a teaser, and a distribution campaign. The first landing-page draft had missing hero content and styling or rendering failures, so it was treated as an unfinished iteration. Other useful discussions included audience questions about using AI to explore income paths from existing expertise, SaaS unit economics, choosing between ads and SEO/GEO, Arabic-market WhatsApp automation, and targeting external markets, plus local voice dictation, content automation, and Telegram community options. Stream lag and interruptions were also investigated without a conclusive cause, while music licensing and gym culture appeared as brief secondary discussions.

  • البث المباشر
  • استكشاف الأخطاء
  • Ethernet
  • الاتصال
  • +4

121 moments from the stream

  1. 7:09:21

    Treating the First Landing-Page Output as a Draft

    He treated the one-shot landing-page build as a first attempt that was unlikely to be fully correct, noticing invisible elements and rendering problems. He chose to postpone refinement so the work could receive adequate time and focus.

    • landing page
    • one-shot build
    • iteration
    • rendering
    • +5

Got a question about something in this stream?

Ask in the group