AI COMMERCE INDEX SCORING ENGINE
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 a build-in-public effort around an engine for measuring how visibly Shopify merchants’ products appear in AI answers, alongside a Command Center for classifying agent tasks by size and dependency, executing them, and reviewing them through task- and milestone-level audits. Practical work covered code-informed prompt preparation, correcting illogical dependencies, monitoring tasks and logs, and improving the README and installation options. Although some workflows were described as becoming more autonomous, defect review, the frontend, and several implementation decisions remained unfinished. Luqman also compared Codex, Claude, and other tools from personal experience, consistently qualifying observations about speed, quality, resource use, and session variability as non-benchmark impressions rather than settled conclusions. Audience questions and wider discussions covered market validation and marketing before Shopify approval, organic outreach versus paid acquisition and waitlists, landing-page structure, animated backgrounds and calls to action, and GEO/AEO compared with traditional SEO. Other useful threads included choosing Telegram or Discord for an Arabic community, learning programming, AI, and DevOps through practical projects, data residency, hosting and DNS, plus ideas for automating marketing and short-form clip extraction. A recurring conclusion was that building a product does not automatically solve distribution; multi-platform expansion, the pre-launch strategy, Hermes adoption, and parts of the website and domain work remained open or under investigation.
123 moments from the stream
- 4:49:16
Choosing a Coding Tool for UI Work
The speaker says they liked Cursor, but its sandboxing constraints led them to consider alternatives, with Codex tentatively preferred for UI work.
- 4:50:14
Marketing a Shopify app before approval
A practical question about attracting merchants to a waitlist before the app is approved, considering SEO, outreach, and social posts as possible channels.
- 4:52:24
Creating a looping animated landing-page background
A workflow for generating an image with Nano Banana, animating it in Kling, and using the same image as both the start and end frame to create a seamless loop before adding it to a website. The discussion says this can give a landing page a high-end feel, while motion duration and subtlety should be tuned to avoid excessive effects; tool cost is also a consideration.
- 5:00:10
Driving Traffic Before Shopify App Approval
The discussion moves from landing-page improvements to the central question of traffic acquisition. Direct outreach to suitable merchants through email, LinkedIn, or warm introductions is presented as a possible channel, while Shopify App Store discovery is not assumed before a public listing is approved. This organic route is described as highly manual and dependent on clear targeting.
- 5:07:28
Evaluating Paid Ads Versus Organic Outreach for a B2B Product
A hypothetical Facebook or Google campaign is considered for early-access acquisition, with attention to distinguishing cost per click from cost per lead. The estimates remain uncertain and are initially affected by a metric misunderstanding. The emerging opinion is that paid acquisition for this B2B product may be too costly or poorly suited as the primary strategy, with organic outreach, a conventional website instead of a waitlist-only approach, and postponing the decision until after the product is built offered as alternatives.
- 5:10:29
Balancing Coding-Agent Speed and Efficiency
The speaker gives a practical impression that Codex can sustain automated coding work with efficient usage, though in his view it is slower than Claude. This leads him to consider increasing workload or compute expenditure when that could improve throughput. These are personal workflow observations, not a controlled benchmark.
- 5:25:04
Organizing Project Documentation and a Milestone-Based Workflow
The assistant was asked to create a repository folder with Markdown reference documents covering analysis and strategy, then continue until the milestone was complete or a task failed review.
- 5:26:55
Troubleshooting a Temporary Live-Chat Issue
The stream chat was tested, reopening it was suggested, and a successful message from another participant indicated that the issue was likely local to the affected viewer.
- 5:28:51
Planning the Website Upgrade and Reviewing the Above-the-Fold Area
Website preparation resumed with a request for an implementation plan to advance the site, beginning with a close review of the current state and especially the background in the above-the-fold area.
- 5:31:46
Planning a LuqDex Site Restructure and Animated Background
A brainstorming session about restructuring the LuqDex site and its pages around the project's manifesto. The proposed looping background uses a high-quality generated image as both the opening and closing frame. The priority is to communicate the application's purpose clearly, retain the reference background's feel, defer visual polish, and turn the direction into a page-by-page implementation specification.
- 5:39:16
Confirming a Nameserver Update
During domain setup, the speaker asks about the next step and reports that the nameserver update action returned a success message. The captions do not show an external test confirming propagation or that the domain is working.
- 5:43:32
Distributing Calls to Action Across a Landing Page
The speaker noted that the specification lacked calls to action and suggested placing them in the navigation, hero, and other sections, with different messaging angles; he estimated that the page needed roughly four CTAs at minimum.
- 5:45:46
Comparing Coding-Agent Speed While Accounting for Task Differences
The speaker felt the current workflow was slower than Claude, while qualifying that the comparison might not be fair because the tasks and milestones differed and the earlier phase involved simpler foundation work.
- 5:47:55
Codex App Experience Versus the Terminal
The speaker preferred working in the Codex app over the terminal and expressed a broader preference for integrated development environments; the captioned thought ends with incomplete details.
- 5:50:45
Planning a Roadmap to Reduce Late-Stage Debugging
The speaker said the current roadmap was stronger, drawing on an earlier experience where work fell into a late-stage debugging trap. The practical lesson was to improve upfront planning so debugging problems do not accumulate near the end.
- 5:51:16
Pre-launch Work Beyond the Command Center
He explains that the website, pre-launch marketing strategy, Shopify app-page preparation, and visual assets sit outside the current command-center scope. The command center includes a QA Verification tab intended to be filled with bugs and notes before launch. He favors presenting a respectable product over rushing, with a historically stated and conditional aim to reach debugging near the end of April and submit in early May, without guaranteeing acceptance timing.
- 5:54:21
Locking the Execution Brief and Working Step by Step
After returning to the implementation plan, he considers its readiness and execution method, then locks the execution brief and chooses a step-by-step approach instead of launching multiple sub-agents. He also notes that the interim appearance may intentionally worsen because clear communication is the priority at this stage.
- 5:57:16
Learning from AI Visibility Tracking Product Sites
He looks at websites from companies in AI visibility tracking as references for communication and presentation, while stressing that comparison with a very large company is not like-for-like. Some product names in the captions are uncertain, so they are not treated as verified identities or spellings.
- 6:00:21
What Is the Vibe-Coding Stream About?
Answering an audience question, he explains that the stream demonstrates using AI to build applications and projects through vibe coding, showing the workflow live from beginning to end.
- 6:01:18
Improving Shopify Store Visibility in AI Answers
The discussion describes an SEO-like approach focused on whether merchants’ products appear when people search through AI tools. The proposed Shopify app would measure how often a store appears, recommend improvements, and use AI to apply some improvements within the store.
Got a question about something in this stream?
Ask in the group