Inside the Core 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 centers on an in-development Shopify app intended to improve stores’ visibility on AI platforms, with a capability audit exposing gaps between the published plan matrix and actual implementation—especially APIs, webhooks, and multi-store agency support. Luqman demonstrates a review workflow combining specialist agents for security, compliance, and UX with hands-on testing, human-controlled merges, and automated deployment; mobile inspection revealed visual defects, confirming that the product was not finished. The discussion also covers free-versus-paid report design, A/B testing the placement of email capture, and an audit-led acquisition funnel whose channels should be measured before ad spending. Audience questions explore Claude, Codex, agent skills, and conversation-context compaction, with advice to master reliable tools instead of chasing every new model. On GEO, the speaker distinguishes it from SEO while leaving the effects of AI-generated articles, backlinks, and llms.txt unresolved because the evidence is not conclusive. The practical conclusion is to align public claims with real capabilities, understand integrations, and test the complete experience before Shopify submission; the completion date, best conversion flow, and need for external monitoring remain open.
109 moments from the stream
- 4:16:37
Merging a Change, Trying a New Flow, and Checking Mobile
Luqman shows a brief practical sequence in which he merges a change while noting that checking first would have been preferable, then tries a new flow for the first time. He observes that part of it is not enabled, considers removing an element, and checks a phone-sized view before judging the result acceptable.
- 4:25:28
Reviewing the Report Interface on Mobile
The review finds that the mobile card layout has become distorted and that the report-ready text and PDF download button are hard to read because white text sits on a light background. The mobile interface therefore needs further adjustment and visual QA before submission.
- 4:32:08
Clarifying Email-Gate Placement
A question is raised about whether one email-gate placement option would create two email-capture paths or only one, with a suggestion that the headline copy could remain verbatim. The final configuration is unclear from the captions.
- 4:33:29
Previewing the Work and Correcting Report-Requirement Misunderstandings
The discussion focuses on obtaining a viewable local or shared preview after the implementation appears to target an “open full report” behavior instead of the intended requirement. Once a preview link works, a browser-based MCP access setup is proposed, though its details remain incomplete.
- 4:46:06
Evaluating Alternative API Access for Claude and Codex
A discussion about researching an option for using Claude and Codex through API keys at different prices, with emphasis on testing it first and verifying that the provider’s APIs and any access attributed to OpenAI are authentic rather than counterfeit.
- 4:51:25
Repositioning the “Almost there” State in Burnish
The requested first task for the live UI was to move the ‘Almost there’ message below Burnish Signal and an adjacent view card, proceeding step by step to avoid confusion.
- 5:03:46
Preparing an App for Shopify Submission
The speaker is working in parallel on application debugging and metrics, plus the frontend of a marketing funnel. He avoids committing to a fixed Shopify submission date because prerequisite tasks and quality standards have kept changing, and says the longer journey begins after acceptance while substantial marketing preparation remains.
- 5:03:58
Planning Facebook Ads for Lead Capture
The speaker describes a frontend marketing funnel intended to use Facebook Ads for lead capture. He qualifies that it is only one possible channel and that treating it as the primary channel will depend on results and metrics.
- 5:05:36
Starting Work Early and Batching Content Preparation
Based on his own experience, the speaker feels that beginning streams and work in the morning improves his productivity. He also prepared Shorts and Reels for the week in advance so they could continue attracting traffic while he stayed focused on application development, presenting this as a personal routine he hopes to sustain.
Got a question about something in this stream?
Ask in the group