Resources

What Resources Means Here

Resources are where I teach the work and reasoning behind the Lab: how a setup works, why I made a decision, what I tried, and what changes through use. Videos are a substantial part of that teaching, alongside guides, field notes, skills, blueprints, and available project files. Learn how the pieces connect, then apply that understanding to your own products, agent team, and studio.

All paid members, starting with Builder Pass, get the full Lab resource library. Higher tiers add private Notion teamspaces, focused Slack rooms, Crew AMA, requests, and mentorship layers, but the resource library itself starts with Builder.

Resources belong to the same living workshop as Slack and Notion. Slack is where you discuss the work with other members; the shared Notion teamspaces give Crafter, Founder, and Mentorship members knowledge and systems to adapt. Resources help you understand why and how to use those ideas in your own work.

What You Get

A resource can be small and tactical or deep and reusable. Some are quick references. Some are full walkthroughs. Some include downloads or project files. The shared standard is simple: it should help a solo developer move from stuck to shipping.

• Step-by-step guides and video walkthroughs for real app-building situations.
• Code and UI blueprints, starter patterns, and reusable implementation notes.
• Agent instructions, executable skills, workflow blueprints, and operational references.
• Design walkthroughs, UI references, and available design or product files.
• Notion systems, planning docs, release workflows, and solo-dev ops material.
• Downloadable ZIPs or starter files when a resource needs more than text.

Bring the learning into your studio

You might learn how I organize project context in a resource, study related examples in The Foundry, and discuss your own setup in Slack. Or you might use Swift Brain references while developing an Apple app, then improve a specialist’s instructions with material from Ops Lab. These are ways to connect the learning; each resource has its own material and does not promise a matching asset in every space.

Read the learning-path guide for the whole experience, the Notion teamspace guide for shared systems, and the Slack community guide for discussing the work with other members.

Built From Real Indie Projects

The best resources come from real pressure: a screen that needed to feel better, an onboarding flow that had to convert, a production problem that needed clearer context, or an agent workflow that had to save time instead of creating more work.

The lesson includes the judgment behind the result: how I choose tools, provide context, assess an agent’s work, or revise a design. Use working examples to understand the decisions and make better ones for your own situation.

How The Library Grows

One new Crafter’s Lab video joins the library every weekday, bringing you into the real work happening inside the Lab: builds, refactors, experiments, member questions, agent workflows, and launch lessons. Follow the reasoning behind those decisions, then try the parts that help with the app or studio you are building.

As that work develops, I also add or revise guides, field notes, templates, and project files when they make the learning easier to use. These have their own rhythm; a weekday video does not promise a daily template, download, or asset. Return to the library as your work changes, and use the growing collection to find the explanation or example you need next.

Choose By The Outcome

When two categories use similar tools, choose the category by the result you need:

• AI Workflows or Codex? Choose AI Workflows for a transferable process; choose Codex for how I develop and review real product work in an evolving app workbench.
• Pi, Hermes, or OpenClaw? Choose Pi to build the agent, Hermes to configure and develop a personal agent around useful responsibilities, and OpenClaw to operate the system.
• Apple Intelligence or Local AI? Choose Apple Intelligence for a feature inside an app; choose Local AI for the model, hardware, privacy, and runtime layer.
• WWDC or a durable Apple series? Choose WWDC while the event and release state are the story; choose the relevant Apple category once implementation is the story.
• AI Skills or AI Workflows? Choose AI Skills for a reusable skill package; choose AI Workflows for the broader process around it.
• Product Marketing or Launch & Distribution? Choose Product Marketing for audience, positioning, promise, messaging, and conversion; choose Launch & Distribution for channels, campaigns, experiments, measurement, and iteration.
• AI UGC or AI Motion Design? Choose AI UGC for honest creator-style scripts and performance creative; choose AI Motion Design for promotional demos, feature animation, launch video, social visuals, and advertising motion—not product UX.

How To Use Resources

Browse the live library, open a category, then pick the resource that matches the job in front of you. Learn the reasoning, try the approach, inspect the result, and adapt the parts that fit your app or studio.

• Use the category grid when you want to browse by area.
• Use resource pages when you want the full guide, video, download, or implementation notes.
• Start a discussion below a resource when you want feedback, clarification, or a second pair of eyes.
• Follow the connected discussion in Crew Log or Slack when the thread keeps going.

Open the live Resources library to see the current categories and published resources.

Always Growing

Resources are a paid member benefit included from Builder Pass onward, and the library is designed to grow with the Lab. I can add categories, publish useful drops, revise old guides, and turn recurring member questions into new resources.

Use the library to find current material and return as your work develops. The value is in learning and applying the connections between the topics, the shared systems, and the ongoing work inside the Lab.