Studio Paths

Build your studio. Keep your craft.

Build the system that builds your apps. Learn how code, architecture, skills, coding tools, plans and agents connect through real product work. Bring your own projects and questions, and develop your studio with a crew that cares about the craft.

Work at the level your project needs

Building your studio means improving both the product and the way you make it. Sometimes the useful change is a Swift function; sometimes it is the context an agent receives or the way a decision carries into the next task. Learn to work across these connected layers:

• Code and product craft: functions, SwiftUI behavior, and the details that make an app useful and a pleasure to use.
• Architecture: modules, state, data flow, and the structure of an Xcode project that keeps changes understandable.
• Knowledge and skills: references, patterns, and reusable capabilities that bring tested judgment into the next task.
• Coding harnesses and tools: the context, permissions, CLI commands, and build or test feedback you give tools such as Claude Code and Codex.
• Intent, plans, and documentation: the purpose, decisions, and success criteria people and agents need. Notion can hold that context; your tools determine how an agent reads and uses it.
• Agents and workflows: useful responsibilities, clear handoffs, dependable execution, and review that connects an assignment to a checked result.
• The whole studio: product, design, marketing, and operations working together so you can build, release, learn, and improve.

Take a SwiftUI feature: understand the behavior you want, inspect the relevant code and architecture, choose useful knowledge or a skill, and give your coding tool the context and checks it needs. Review the feature in the app. Then keep the decision, reference, or method that will help the next feature or product. This is how useful learning carries forward into the system you build with.

Move between layers as the work requires. You still shape the product and judge the result; a useful system can be small, and a specialist can work only when you need it. The five paths below organize subjects you can explore across these layers, with no required sequence.

One workshop. All connected.

Your project gives the learning its direction. Videos and field notes explain real work and the decisions behind it. Slack is where you bring questions, compare approaches, and share what happened when you tried them. The Notion systems included with your pass provide knowledge and structures to study and adapt as you develop your studio.

• Videos & field notes: Understand the work and the reasoning. Work through real product decisions, code, architecture, and agent workflows. Understand why an approach works, try it in your project, and keep what helps the next piece of work.
• Notion Teamspaces: Work with the systems behind it. Study shared project structures, curated knowledge, and agent instructions. Adapt the useful parts to build systems that fit your own studio.
• Slack office: Bring your studio into the conversation. Bring a question, an unfinished product, or a workflow you want to improve. Compare approaches with the crew, learn from shared examples, and return with what changed in your own work.

The Slack office

Work through the questions behind your studio. Bring the part of your work that needs another perspective: a code decision, an architecture problem, a specialist you are developing, or a workflow that keeps losing context. Learn with people building studios of their own.

I bring examples and reasoning from real product work. You bring your projects, questions, and experience. Together, we examine what helped, what failed, and what is worth carrying into the next attempt.

• Specialists with real responsibilities. Discuss what a useful specialist should know, which decisions belong with you, and how to judge its contribution. A specialist can work on demand; it does not need to run continuously.
• Workflows you can improve. Trace a real task through its intent, context, execution, and checks. Find the step that needs attention, try a change, and share whether it helped.
• Learning that carries into later work. Compare tools, skills, and approaches through actual results. Keep the useful reasoning and test it again as your projects and tools change.

Notion Teamspaces

Build a studio system that fits your work. These shared spaces connect selected product work, Apple knowledge, and agent practice. Study how the pieces fit together and adapt what helps your own studio. Crafter and Founder membership include the three shared Teamspaces; Mentorship adds our private Cockpit.

• The Foundry

  Crafter & Founder

  Study selected product work from Crafter Apps. Learn how projects, briefs, tasks, feedback, and decisions connect. Study the work I share and apply the structure that fits your studio.

• Swift Brain

  Crafter & Founder

  Give yourself and your agents useful context. Draw on curated Swift and SwiftUI knowledge, reusable skills, and Apple UI references. Copy the databases you need into your workspace and use them while you build.

• Ops Lab

  Crafter & Founder

  Build your own agent specialists. Explore the agent instructions, skills, and workflow blueprints I use. Understand how the pieces work together, then adapt them to your own projects, tools, and accounts.

• Mentee's Cockpit

  Private mentorship

  Work on your studio with me. Our private Notion workspace for sharing files, developing your agent instructions, and setting up your studio together. We keep project docs and next steps here, with Slack for conversation between sessions.

Bring your project into the workshop.

Become a member to build alongside me and the other solo developers in the Lab. Keep learning as the work evolves, share your progress, and develop the skills and systems behind your own studio. Choose the membership that fits how you want to take part.

Explore all ResourcesSee membership