Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I don't know how other people work with remote agents when building iOS apps. But my best workflow is to ask Claude/Codex to implement a feature, create E2E test, record that test and show me in Quicktime. I check the video with VNC app then push to Testflight 👌

18,746 Aufrufe • vor 5 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

I built a mobile app to check Paddle revenue (because they don't have one): 👉 - Use your Paddle API key (read-only and scoped) - Live data with beautiful and useful graphs built with native Swift UI. - Multi-account supported, unified revenue metrics. - Data stay on device, no server (api requests are sent directly from your phone) - Home widgets - I made it free to download on App Store (once it's approved) - Buy the source code for $19 and customize it however you want (save 5hrs of prompting if you try to do it yourself). Some interesting facts about this side project: - I vibe coded with 100% claude code remotely on my Mac Mini (with my AI assistant setup) in less than 24 hours. - I have read 0 line of code in this project and never opened Xcode myself. - My AI assistant designed the app with GPT Image 2, built the app with Swift UI, test it on simulator (via screenshots), send the test build to TestFlight for me to test, and invited me to the app store connect account so I can test on my phone, then the AI submitted the app to App Store and currently waiting for approval. - For the website, I ask it to come up with a domain name, I bought it via manually and give it access via Cloudflare API, the AI design and create a static website with GitHub, test it with lighthouse CLI, deploy via GitHub pages, config the domain DNS, deploy the website. - Then I sign up an account with Polar payment, create an API key and ask the AI to setup a store, add payment, link with the account, and add the payment to the website. The entire process happened in the last 24 hours with me only talking to the AI via Telegram. This is such a fun side project not only to create an app that I wish exists, but also to push the limit of what I can use AI for, and so far I'm very impressed. I'll create so much more apps! It feels like I have unlocked a super power.

Tony Dinh

43,726 Aufrufe • vor 1 Monat

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

42,501 Aufrufe • vor 17 Tagen