Building AI Apps Live from Cairo 🌙
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 building and learning in public while planning a Shopify B2B SaaS product and improving a shared workspace for agents such as Codex and Claude. Luqman discusses preparing a project manifesto, roadmap, and Shopify review documentation before implementation; organizing dependent phases; sharing instructions and skills across agents; and reducing approval prompts while retaining safeguards for sensitive commands. The discussion develops into a visual project-map concept—favoring a swimlane view—that would turn a Markdown roadmap into an Electron app tracking milestones and dependencies while connecting to agents. This is compared with a custom task board and an always-on agent environment, but all remain ideas requiring testing. Practical topics also include separating a documentation app from the eventual Shopify app, possibly using simple HTML for a marketing page, and preliminarily favoring duplicate themes over direct edits to a live Shopify theme. The stream also considers developing a basic app while refining its concept, then presenting it through a polished landing page and clear explainer video, with only a general and uncertain reference to attracting early users. Luqman also revisits a domain transfer and a website built with Claude and polished with Codex, although DNS verification and the final review were not shown as complete. A broader content hub for streams, projects, explanations, and an Egyptian and MENA audience is proposed, with the sessions framed as a work-and-learning record rather than final tool verdicts. Open questions remain about coordinating instruction files, what happens to theme changes after app removal, the project map’s technical design, and whether an always-on agent environment could replace a separate task board.
33 moments from the stream
- 0:00:50
A Built Website Awaiting Domain Transfer
Luqman recaps the previous stream: a working website was built and could use some polish, but connecting it to its domain stalled while DNS was being transferred from GoDaddy to Cloudflare. The work was still unfinished at this point, and he planned to continue the connection task.
- 0:02:43
Building in Public and Showing the Full Process
Luqman explains that thinking aloud helps him work and that the channel is intended to broadcast the real building process rather than offer short software comparisons. In his view, this exposes the experience from beginning to end, and AI-assisted building has become accessible even to people who are not professional web developers.
- 0:03:51
Turning a Long Roadmap into a Task Board
Luqman outlines plans to begin a large project that he has not yet explained, focusing on converting a long roadmap prepared with several AI tools into a visual board or task board. He compares the map to guidance out of a forest: a way to direct and structure a deep project before implementation, not a guarantee of success.
- 0:06:27
Possible Overlap Between Tool Instruction Files
In a fragmented passage, Luqman notes overlap between instruction files associated with two coding tools and appears to consider keeping them separate in some form. The recording does not clearly establish the reason or final arrangement, so the observation remains unresolved and should be verified before deriving a general rule.
- 0:07:28
Resuming the Domain Transfer Task and Checking Its Wait State
Luqman returns to a transfer task left open from the previous stream, resumes the associated agent, and checks Cloudflare. A message says to wait another 60 minutes, but the later speech is fragmented and does not establish that the DNS transfer or website connection was completed.
- 0:10:29
Reviewing a Website After a Domain Transfer
After transferring the domain, Luqman described the site as rapidly built with Claude and then polished using Codex. He planned to postpone the final review until DNS verification finished; the interface said this could take up to 48 hours.
- 0:12:41
A Project Manifesto as a Stable Reference
Luqman explains that a project manifesto records the business idea, components, purpose, mission, vision, target market, and profitability analysis. He treats it as a constitution-like reference that should change only when a major roadblock forces a fundamental revision.
- 0:14:00
Roadmapping for Shopify App Review
Luqman treats the roadmap and submission documentation as essential preparation before implementation. According to his understanding at the time of the stream, Shopify app review could take 15–30 days, and missing requirements or documentation could lead to rejection, resubmission, and another wait, so he wanted to identify possible rejection reasons and build correctly from the start.
- 0:15:46
Safeguards for an AI Agent Editing Shopify Themes
Luqman discusses a chat-based app through which a merchant could request Shopify theme changes. Based on his preliminary and incomplete understanding, the agent should duplicate the theme instead of editing the live theme directly. He also raises an unresolved question about app-removal behavior and postpones conclusions until he understands how it works in practice.
- 0:17:26
Using Separate AI Sessions for Pre-Implementation Research
Luqman says AI helped expand parts of the manifesto from his original idea, but more information was needed before setting up the work environment. He therefore decides to open separate research sessions with Codex and GPT outside the project context and provide them with the relevant background.
- 0:20:22
Requesting a Work-Environment Plan from Project Docs
A prompt supplies the assistant with project Markdown files and asks for a project-specific AI coding environment plan covering skills, MCP integrations, hooks, loops, automations, and commands, based on best practices as of March 11, 2026.
- 0:28:02
Avoiding Instruction Conflicts Between Coding Assistants
The discussion says optimizing a workflow for one coding assistant can be relatively direct through an instructional Markdown file, while supporting Codex and Claude together may create overlap or conflicts because they follow different working philosophies. It points toward harmonizing instruction files, though this page does not clearly establish the detailed solution.
- 0:30:10
Optimizing a Work Environment for Multiple Coding Agents
Luqman discusses optimizing the project primarily for the agent expected to handle most of the work, while anticipating that Codex can read and benefit from the same setup for tasks such as UI work. This is presented as a practical expectation, not a confirmed test result.
- 0:32:42
Turning Agent-Environment Improvements into Separate Prompts
A practical workflow emerges for handling the improvements: request a Markdown file containing five separate improvements or prompts, then review them one at a time, with precise instructions for generated settings and skills.
- 0:34:56
Sharing Project Structure and Skills Across Claude and Codex
Luqman decides to focus first on configuring the environment for the agent leading most of the work while retaining shared elements Codex can use, especially AGENTS.md and overlapping skills. He cautiously expects an optimized project structure to make work across both agents largely seamless.
- 0:41:47
Organizing an AI Coding Workflow into Dependent Phases
The work was divided into phases, with independent phases run in parallel after completing the first phase that creates an instruction file needed downstream, while the final verification phase was deferred until the end.
- 0:45:46
Reducing Permission Prompts While Protecting Sensitive Commands
Allow and deny rules were discussed to give the coding agent more freedom inside the project while retaining approval for deletion and push or commit operations and blocking system-level commands. A configuration was applied and tested, but it still requested permission, so it was not shown to eliminate interruptions completely.
- 0:50:37
Using Codex to Audit a Project and Its Work Environment
The speaker reviews a work environment optimized around the project manifesto, then asks Codex to read the core materials and perform an in-depth sweep of the documentation, brand architecture, MCP configuration, and wider project for outdated practices or missing best practices. He notes that some optimization areas are still new to him and that the review is not yet complete.
- 0:56:02
Prioritizing a Shopify B2B SaaS Product
The speaker describes the main project as a B2B SaaS product specifically for Shopify. Near-term priorities include improving the work environment, reviewing proposed optimizations with Codex, and beginning a clear project roadmap, while acknowledging that building this type of SaaS product is new territory for him.
- 0:59:37
Separating the Documentation App from the Shopify Application
The speaker questions whether the current framework setup will remain useful when moving to the future Shopify application architecture. The response visible in the captions indicates that the documentation app can be built separately and that work on the actual application has not started yet; some precise technical details remain unclear in the transcript.
Got a question about something in this stream?
Ask in the group