pear-v2-runtime

Bootstrap Pear v2 applications with runtime and host wiring.

102|4|Updated Apr 15, 2009
One-click install
npx skills add https://github.com/mikker/dotfiles --skill pear-v2-runtime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pear-v2-runtime
Source: https://github.com/mikker/dotfiles/tree/main/agents.symlink/skills/pear-v2-runtime
Command: npx skills add https://github.com/mikker/dotfiles --skill pear-v2-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Builds and wires Pear v2 applications using a modern template plus runtime approach, reducing setup complexity for bootstrapping new Pear apps and ensuring consistent host integration and update flows.

Core Features & Use Cases

  • Bootstraps Pear v2 applications from current templates and wires a runtime to handle worker execution and OTA updates.
  • Supports Electron or mobile hosts, explicit storage paths, and separation between development and packaged behavior.
  • Enables staging and release workflows with defined update flow across host and worker boundaries.

Quick Start

Start by selecting the nearest hello-pear-* template and wire PearRuntime with explicit storage paths.

Frequently Asked Questions about pear-v2-runtime

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

FAQPage Schema
How do I bootstrap a Pear v2 application from a modern template?

Bootstrapping a Pear v2 application involves selecting the nearest hello-pear-* template and wiring PearRuntime with explicit storage paths. This setup ensures consistent host integration and manages worker execution alongside OTA updates.

How do I manage OTA updates in an Electron or mobile host with Pear v2?

Managing OTA updates in a Pear v2 host requires defining an update flow across host and worker boundaries. The runtime handles update signaling to satisfy end-to-end staging and release deployment needs.

Does Pear v2 support separate storage paths for development and packaged builds?

Yes, Pear v2 supports deterministic storage paths with clear separation between development and packaged behavior. This ensures runtime storage and worker bootstrapping remain distinct across different build environments.

What is the best way to wire a runtime for Pear v2 worker bootstrapping?

The best way to wire a runtime for Pear v2 worker bootstrapping is integrating PearRuntime with explicit host templates. This approach cleanly separates runtime storage and update signaling from worker execution logic.

Do I need explicit host templates to set up a Pear v2 runtime?

Yes, explicit host templates are required when setting up a Pear v2 runtime. They provide the necessary structure for wiring Electron or mobile hosts and managing deterministic storage paths and OTA workflows.

Why does my Pear v2 OTA update flow fail across dev and packaged builds?

OTA update flow failures in Pear v2 often stem from inadequate separation between development and packaged behavior. Ensure clear separation between runtime storage, worker bootstrapping, and update signaling across build environments.