PWV Portfolio Feed

This was fun to build and helped me realize the potential of LLMs as copilot for teams working with Xcode projects. Give it a shot and let us know what you think

This is only the start. We see languages as a distinct chance to forge novel experiences, and we aim to delve deeper into this with our dashboard. This will enable users to engage with their build and test information, app packages, and cache telemetry through conversation.

In the latest Tuist release, 4.46.1, we've introduced an MCP server and a command to integrate Claude into your Xcode development environment.
(It works with the most recent projects you interacted with through Tuist)

The potential of LLMs via the MCP interface is so compelling that we investigated the possibility of transforming chat tools like @AnthropicAI's Claude into your development environment companion. We found that it actually works remarkably well.

Tuist acts as a bridge between LLMs and your development environment, allowing you to decide who to share your data with. This is just the start; we plan to introduce more tools and resources based on your feedback.

Introducing Tuist 4.46.1, now with an MCP server that seamlessly integrates with LLM-powered tools, enabling you to incorporate your projects into contextual discussions.

Having a data structure to represent Xcode projects is not only useful for reducing merge conflicts, optimizing compilation and test runs, and providing visualization tools for teams, but it also serves as an excellent resource for LLMs to understand your development environment.

LLMs and Claude's MCP protocol have unlocked a game-changing way for teams to engage with their projects: now, you can chat directly with your Xcode projects.

yay love to hear that! how would you use it? still figuring out use cases and UX, but it's been fun for me at least

why i ask

huh, i guess it wasn't priced in

so is there a replacement for serde_yaml? i stopped paying attention and could do with some cursed whitespace file stuff

4. Lessons learned

• Start early—security is easier when built-in
• Automate compliance where possible
• Work with auditors, not against them
• Compliance ≠ security—focus on what actually makes you safer

2. What’s SOC 2 Type II?

A security standard proving we:

 ✅ Protect your data
 ✅ Follow strict access controls
 ✅ Enforce security best practices consistently over time

It’s not a one-time audit—it’s proof of ongoing security.

1. Why SOC 2?

Teams trust Tuist to manage sensitive Xcode projects. Instead of answering endless security questionnaires, we got SOC 2 Type II—so our security speaks for itself.