Index of every page on this site: llms.txt
All skills
sandharbor avatar

/app-build

@62fef7a
Run it yourself

Build the Meadow Electron app and launch it in test mode to verify it starts cleanly

  • 1 file
  • 1.9 KB
  • Updated 3 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/sandharbor/meadow/app-build

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈24 tokens for metadata: the name and description. ≈459 when used: this file.

Description uses 1.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈96 characters, or 1.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

App Build

Build the Meadow desktop app from source and launch the built app in test mode so you can verify it starts and runs correctly.

Important: The shell working directory persists between Bash tool calls, so relative cd commands cause doubled-path errors. As the very first Bash command, resolve the repo root and store it in a variable:

REPO_ROOT=$(git rev-parse --show-toplevel)

Then use $REPO_ROOT in all subsequent commands. Never use bare relative paths like cd app/hosts/desktop.

Step 1: Check for a running Meadow app

The build launches a freshly-built Meadow app in test mode. If an existing Meadow app is already running, macOS's single-instance behavior kills the newly launched instance before it finishes starting, and the verification step fails with a confusing startup timeout.

pgrep -f "Meadow.app/Contents/MacOS/Meadow" || true

If this returns any PIDs, stop immediately and tell the user:

"app-build aborted: a Meadow app is already running. Please quit Meadow (cmd+Q) before running /app-build again."

Do not attempt to kill it yourself — the user may have unsaved state.

Step 2: Build and launch

cd "$REPO_ROOT/app/hosts/desktop" && ./build-and-test.sh

This builds all components (rust binaries, backend, frontend, electron main), packages the app, mounts the result, and launches Meadow with --test-mode. The script waits for === STARTUP_COMPLETE === in the test log and then blocks so you can interact with the running app. Press Ctrl+C to stop — the script unmounts the volume and kills the launched process on exit.

Step 3: Summary

When the user stops the session, report:

  • Whether backend, frontend, and main-window startup markers all appeared in the test log
  • The built app location under app/hosts/desktop/build/

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 62fef7a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 3 months ago

README badge

README badge for sandharbor/meadow/app-build