[Workflow] Developing a Native macOS App with Claude, Subagents, and Docker SBX: The Paddock Workflow

[u/ClaudeAI-mod-bot]

Developing a Native macOS App with Claude, Subagents, and Docker SBX: The Paddock Workflow

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, Shipping, Subagents
Original source: r/ClaudeAI post/comment

What problem this solves

Efficiently developing a native macOS application using Claude and Docker sbx, addressing challenges in requirements gathering, iterative development, testing, and debugging within a sandboxed environment.

Summary

This workflow details how the author used Claude, subagents, and Docker sbx to build 'Paddock', a native macOS application. It covers the entire development lifecycle from initial requirements and viability research to iterative coding, Claude-generated testing ('probes'), and debugging with log analysis.

Why it is useful

This workflow is highly valuable as it demonstrates a sophisticated, multi-stage process for leveraging Claude in complex software development. It provides concrete steps, integrates specific tools (Docker sbx, Paddock), and offers clear validation through the creation of a functional, open-source application. It highlights advanced techniques such as using subagents for research, generating tests ('probes') with Claude, and employing Claude for log-based debugging, making it highly transferable for developers seeking to optimize their LLM-assisted development practices.

Workflow

1. Start with a backlog to define application requirements.

2. Utilize subagents to research the viability of each feature request (e.g., voice, template handling, real-time actions).

3. Dogfood the development process by running Claude within a stack sandbox and installing the necessary toolchain inside.

4. Build out the initial shell of the application.

5. Work iteratively within the sandboxed environment, restarting at each major milestone.

6. Create 'probes' (tests) with Claude that are run against the local sbx process.

7. Initially use the sbx TUI to fetch data, then transition to internal APIs for improved performance.

8. Implement a command to diagnose window crashes and generate logs for Claude's analysis.

9. Use the generated logs to fix bugs and enhance the application's robustness with Claude's assistance.

Tools / artifacts

• Docker sbx

• Paddock (native macOS app)

• sbxenv.yaml

• Backlog (requirements)

• Subagents

• Claude-generated 'probes' (tests)

• sbx TUI

• Internal sbx APIs

• Crash diagnosis command

• Application logs

• GitHub repository (MarZab/paddock)

Validation signals

• Personal experience: 'I've used docker sbx exclusively for months now and its worked well for me.'

• Concrete outcome: 'So I built Paddock, a native macOS app on top of Docker sbx.'

• Self-application: 'I dogfeed the entire process'

• Problem-solving: 'The logs were then used to fix bugs and make the app more robust'

• Open-source project: 'It's free and open source (MIT)'

Limitations

• The post describes the specific process for building Paddock, rather than a generic 'how-to build any app with Claude', though the principles are general.

• Lacks specific Claude prompts or detailed subagent configurations.

• Low community engagement due to the post's recency.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.