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
- 7:30:25
Commerce Index Scoring Engine Backend Recap
Luqman recapped work on an engine intended to score merchants within AI systems: the backend had been built, while the frontend had not. He noted that he did not yet understand every internal detail and that bugs remained possible, so he planned to audit the milestone before continuing.
- 7:32:53
Dividing Work Between Codex and Claude
Luqman outlined an initial workflow combining Codex and Claude, with important tasks assigned to Claude. He felt Codex had been slower in this session and suggested that fewer parallel agents might be a factor, while preserving task difficulty as another possible explanation and emphasizing implementation quality over loyalty to either tool.
- 7:37:30
Reviewing a Milestone and Preparing the Next Tasks
Luqman reviewed a project milestone, noting that some checks passed with notes and that a visual indicator showed issues. Rather than immediately starting another milestone, he planned to inspect the results and prepare the next task prompts in advance to streamline the following work session.
Got a question about something in this stream?
Ask in the group