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
- 3:29:30
Monitoring Background Tasks Through Logs
A practical note that a task may continue running in the background even when it appears inactive, with execution logs providing periodic progress visibility.
- 3:33:04
Requesting Short, Interactive Cloudflare Instructions
A request for detailed guidance through a Cloudflare change, clarifying that “step by step” means giving only one to three steps at a time and then waiting for feedback. Workers and Pages are also mentioned, though the exact procedure is incomplete in the captions.
- 3:44:40
Designing a Clear Command Center README
A request to study the README structure of a public GitHub repository and use a similar approach for the command center: simple, clean documentation with a table of available commands and a description of what each command does, replacing a current README described as messy and ineffective.
- 3:46:04
How to Change Name Servers
A brief practical question about the need to change name servers and how to do it; the page does not provide the solution steps or identify the service provider.
- 3:48:55
Question About Changing Nameservers and Server Activation
A question was raised about exactly where to change the nameservers, followed by a remark that the server should start within minutes. The captions do not contain a clear setup walkthrough.
- 3:50:57
Balancing Agent Speed, Token Use, and Output Clarity
The speaker reviewed a coding-agent workflow, preferring active status without every intermediate step to reduce token use, and noted that the README needed cleanup. In his experience, Codex appeared economical in usage but somewhat slow, prompting consideration of a stronger, faster workflow; these were personal observations, not a benchmark.
- 3:55:31
Investigating a Blocked Milestone and Illogical Dependencies
Work stopped at a natural checkpoint, yet the milestone appeared blocked despite being partly complete. The speaker asked for an investigation into why the dependencies were not following a logical order and what the workflow was missing.
- 3:58:07
Making a Table-Creation Prompt More Specific
After the same prompt failed to produce the intended result, the speaker proposed testing an explicit instruction to create a table and providing a screenshot of the desired outcome. The captions do not establish that the revised attempt succeeded.
- 3:58:49
Using Screenshots to Guide Agent Setup
The workflow proposes giving an agent two screenshots showing a skills-relationship diagram and an available-skills table, then asking it to implement a similar structure.
- 4:00:53
Starting a Landing-Page Redesign from Brand Documentation
The agent was asked to inspect the codebase, brand documentation, manifesto, and color palette before beginning website changes, with the logo noted as not yet ready.
- 4:03:36
Reviewing Dependencies and Blockers Across Project Milestones
A broad review was proposed across hundreds of tasks and multiple milestones to reassess blockers, dependencies, and milestone relationships, restructuring tasks where needed and distributing the analysis among several subagents.
- 4:05:22
Verifying File Changes and Planning a Landing-Page Transformation
After noticing that the target file had not changed, the discussion considered a temporary text-name swap followed by an implementation plan to align the landing page with the brand manifesto, without establishing that the change succeeded.
- 4:08:30
Stress-Testing a Project Command Center’s Capabilities
The README review was deferred in favor of stress-testing the work completed so far and summarizing the project command center’s capabilities from practical behavior as well as documentation.
- 4:09:48
Codex and Claude: Usage Limits vs. Practical Coding Quality
The speaker compares his experience with Codex and Claude, saying Codex appeared to permit more work within its usage limits while Claude still seemed stronger in practical output quality. He cautions that aggregate coding benchmarks combine factors such as debugging and hallucination, so he is unsure he is interpreting their rankings correctly.
- 4:18:55
Choosing Different Tools for Frontend, Backend, and Code Review
The speaker prefers the Codex interface for website and UI design work, while describing another tool with an unclear name as strong for backend tasks. He highlights the convenience of commenting directly on interface sections to request targeted changes, while noting that conversation compaction during a large codebase review may risk losing context.
- 4:29:12
Does Marketing Consultation Need a Custom Skill or Agent?
A discussion of how to get useful marketing consultation from an AI agent: whether talking with the orchestrator is enough or a project-specific skill or configured agent is warranted. Before drafting a strategy—especially a pre-launch strategy—the exchange begins identifying what information should be supplied first.
- 4:34:12
Fixing Dependencies That Block Automated Tasks
A practical update on an automated workflow that stalled when tasks became blocked by an illogical dependency between milestones. The dependency relationship is being corrected so blocked tasks can be released automatically when their prerequisites finish.
- 4:37:03
Minimizing App Registration Data
A discussion about collecting only the minimum registration data, with uncertainty over whether app stores make users’ email addresses available.
- 4:40:26
Working Across Milestones or Completing One at a Time?
A question about managing automated execution: whether to take the next actionable tasks across multiple milestones or complete each milestone separately.
- 4:42:50
Should Pre-Launch Marketing Begin Before Shopify Approval?
A comparison between launching the site after app approval and creating a pre-launch page to collect interest earlier. The discussion weighs organic outreach against paid ads while considering the estimated Shopify submission and review timeline and uncertainty about the best option.
Got a question about something in this stream?
Ask in the group