local-dev

Launch a Python backend and macOS app in local development environments.

13.1k|2.2k|Updated Mar 22, 2024
One-click install
npx skills add https://github.com/BasedHardware/omi --skill local-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-dev
Source: https://github.com/BasedHardware/omi/tree/main/.claude/skills/local-dev
Command: npx skills add https://github.com/BasedHardware/omi --skill local-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

## What problem does it solve? This Skill automates booting a local development environment by launching the backend server and the macOS app, enabling a streamlined setup for development sessions.

## Core Features & Use Cases

  • One-command startup for both backend and macOS app
  • Flexible usage: backend only, app only, or both with options for a clean build or release mode
  • Argument routing supports targeted launches and argument forwarding to the macOS build script

### Quick Start Use the /local-dev command to start the full development environment:

  • /local-dev
  • /local-dev backend
  • /local-dev app
  • /local-dev app --clean
  • /local-dev app --release

Frequently Asked Questions about local-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a local development environment for a Python backend and macOS app together?

You can start a local development environment by running a single command that launches both the uvicorn backend server and the macOS app simultaneously, streamlining your development session setup.

Can I launch only the backend server or only the macOS app during local development?

Yes, you can target specific components during local development by passing arguments to launch only the backend server or only the macOS app, rather than starting the entire environment together.

Do I need python-dotenv and uvicorn to run the local development server?

Yes, running the local development server requires a Python-based backend utilizing uvicorn for the server and python-dotenv for environment variables, plus a compatible shell environment.

What's the best way to forward build arguments like clean or release to a macOS app during local dev?

The best way to forward build arguments like clean or release to a macOS app during local dev is by appending flags to the app launch command, which routes them directly to the macOS build script.

Does local dev automation require a specific macOS build script path?

Yes, local dev automation requires the macOS build script to be located specifically at app/scripts/dev-macos.sh within your project directory for the launch process to function correctly.