The in-app browser from Codex is one of my favorite features and I really wished I could use it on the iOS simulator. So I built it. Now I can drop a comment on the actual element and codex knows exactly what component I was talking about.
I find it really difficult to stick to Expo or react native after using SwiftUI. The only thing that annoys me is waiting for the app to compile. But maybe that won't be a problem anymore
@Dimillian Using $ for skills is one of the best features of codex because it makes the action clear. The slash is for commands and the moment commands and skills blend together it’s horrible. Lots of examples where that went wrong!
I've put together a harness that is proving to makes Claude surprisingly better at creating new features and solving complex problems (e.g., sequencing animations, multi-state transitions, etc).
It's ridiculous how good the outcomes have become. Look at this live browser streaming of the iOS simulator. And look at the calendar itself it was all written by Claude using this harness. It was capable of really nailing the states/animations.
I've put together a harness that is proving to makes Claude surprisingly better at creating new features and solving complex problems (e.g., sequencing animations, multi-state transitions, etc).
The other skills are library-knowledge, knowing how to find authoritative sources about the methods/interfaces of a library used in my project. And then I have the plan/fix/spike/refactor commands. But the BEDROCK is the skills that make Claude absorb knowledge.