SwiftLee Weekly
SwiftLee Weekly #313

Combining MCP & Agent Skills · Optimizing SwiftUI animations using AI · Integrating AI into Xcode's Simulator

Join 31,000+ Swift & iOS developers — free, every Tuesday, in 5 minutes.

No spam. One email every Tuesday. Unsubscribe in one click.

This week's blog post

Using an MCP to perform product optimizations

I'm having more and more fun with AI and I'm optimizing by workflow quite a bit. While keeping track of these learnings for aifundamentals.dev, I didn't want to wait with writing this piece of insight. I share actual prompt examples and one of my non-coding favorite Agent Skills.

Read the article

Sponsored

Fix iOS issues faster with this workshop from Sentry

Learn how to set up Sentry to surface high-priority iOS issues without alert fatigue, use Logs and Breadcrumbs to understand what led to a crash, find performance bottlenecks with Tracing, and monitor app size with Size Analysis. This practical, hands-on session is designed to help you debug more efficiently and ship with more confidence.

Learn more

Curated from the community

Swift Evolution

Last week's Swift proposal state changes. Review-stage proposals are your chance to influence Swift's future.

What I'm working on

Exploring AI integration into RocketSim

This is really a proof of concept, but I'd love to see how many of you reply to this email to say they want this.

The idea is simple:

Pick any elements inside the current view in the Simulator Write a prompt on what you want to change. E.g. "Make the SF symbols of these items bold" Include any extra metadata, like debug logs, environment info (OS / Device / etc) or network requests performed on this view Copy the prompt

This coud allow you to, while debugging, quickly prompt quick fixes along the way. Later on, I would allow you to Bring Your Own Key (BYOK) and directly launch Cloud Agents from within RocketSim.

Other prompts this would enable:

"An unexpected bug occurred on this page. Analyze the console logs and network requests and come up with a fix" "The design looks off, probably due to dynamic type. Evaluate the current environment info and come up with a fix"

The best thing is that these could be triggered from your QA engineers too.

Now, this was really a quick proof of concept, but I'd love to see what this triggers for you. Please, don't hesitate to hit reply, I really would love direct input for this one.

Thanks!

Enjoying this issue?

Join 31,000+ Swift & iOS developers and get the next one in your inbox — free, every Tuesday, in 5 minutes.

No spam. One email every Tuesday. Unsubscribe in one click.