holepunch-app-composition

Compose a Holepunch application architecture blueprint across host shell, worker, RPC boundary, UI state, and Pear runtime.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Compose a complete Holepunch application architecture blueprint by clearly mapping responsibilities across host shell, Pear runtime, backend worker, shared domain layer, RPC boundary, and UI state to enable scalable, maintainable systems.

Core Features & Use Cases

  • Define the replicated domain boundaries and local metadata split across layers.
  • Specify host shell responsibilities, worker entrypoints, domain contexts, and UI state shaping to enforce clean architecture.
  • Provide a deterministic load and watch flow: task-oriented RPCs, event-driven snapshots, and safe UI consumption.

Quick Start

Compose a practical architecture blueprint by allocating responsibilities across host shell, Pear runtime, worker, domain layer, RPC boundary, and UI state.

Frequently Asked Questions about holepunch-app-composition

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

FAQPage Schema
How do I structure a multi-layer Holepunch application architecture?

Structure a multi-layer Holepunch application by mapping responsibilities across the host shell, Pear runtime, backend worker, shared domain layer, RPC boundary, and UI state to enforce separation of concerns.

What is the best way to separate domain logic from UI state in a Pear app?

Separate domain logic from UI state by defining a shared domain layer for replicated boundaries and using snapshot-based communication to ensure safe, event-driven UI consumption.

How does RPC boundary communication work between workers in Holepunch?

RPC boundary communication works by assigning a clear, task-oriented RPC surface per worker, enabling deterministic load and watch flows that drive event-driven snapshots for the UI layer.

When do I need to blueprint a multi-library Holepunch app architecture?

Blueprint a multi-library Holepunch app architecture when architecture decisions drive module placement across runtime, domain, and UI layers, requiring clear boundaries for scalable and maintainable systems.

Can I define worker entrypoints and host shell responsibilities for Holepunch apps?

Define worker entrypoints and host shell responsibilities by allocating specific tasks across the Pear runtime and domain contexts, ensuring deterministic loading and safe UI state shaping.

What are the limitations of using snapshots for UI communication in Holepunch?

Snapshot-based UI communication enforces safe consumption but requires strict alignment with the RPC surface and domain layer, limiting ad-hoc state queries to predefined event-driven flows.