holepunch-app-composition

Compose a complete Holepunch application by assigning responsibilities across the host shell, Pear runtime, backend worker, shared domain layer, RPC boundary, and UI state. Use for tasks that plan or refactor app architecture, decide where features should live, connect Hyperstack primitives to Pear hosts, or turn a product idea into a practical implementation blueprint without coupling it to one specific app.

Ir a la instalación

Repositorio: mikker/holepunch-skills
Última actividad en el origen: 25 de marzo de 2026 a las 12:05
Idioma detectado de SKILL.md: inglés
Estrellas: 1
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/mikker/holepunch-skills --skill holepunch-app-composition

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

4 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

autobonk-contexts

Define schema-first Autobonk domains with generated schema bundles, `Hyperdb` views, managers, contexts, role-based permissions, pairing flows, and optional Yjs collaboration support through `autobonk-yjs`. Use for tasks that model shared state, write or extend `schema.js`, add routes and permission checks, build create/join flows, or implement deterministic replicated collaboration on top of Autobonk.

2026-03-25

hyperstack-foundations

Design and implement peer-to-peer application backends on the Holepunch hyper stack using Corestore, Hyperswarm, Autobase, Hyperbee, Hyperdb, Hyperblobs, Hyperdrive, and adjacent storage primitives. Use for tasks that need storage topology decisions, local-versus-shared state boundaries, replication design, lifecycle and cleanup planning, or backend architecture for a worker, service, or app core.

2026-03-25

pear-v2-runtime

Build and wire Pear v2 applications using the current template-plus-runtime approach, especially `hello-pear-*` starters, `pear-runtime`, `pear-mobile`, embedded Bare workers, explicit storage paths, and OTA update flow. Use for tasks that bootstrap a new Pear app, wire an Electron or mobile host, add update handling, separate dev and packaged behavior, or define staging and release flow.

2026-03-25

Ver todos los de este repositorio

Holepunch App Composition

Overview

Use this when the problem is bigger than one library. The goal is to produce a clean architecture where the runtime boots the worker, the worker owns replication, the domain layer owns rules, and the UI consumes snapshots.

Preferred Shape

Host shell: windowing, preload bridge, runtime lifecycle, update events.

Worker or service: long-lived backend, managers, watchers, snapshots, file ingestion.

Domain layer: contexts, schemas, permissions, replicated data model.

UI layer: state store, optimistic UX where safe, rendering only.

Architectural Rules

Keep app-specific business rules out of the host shell.

Do not let the renderer talk to Corestore or Hyperswarm directly if a worker can own that state.

Build one RPC surface per worker and keep it task-oriented, not storage-oriented.

Let the worker stream snapshots or events to the UI instead of exposing many low-level queries.

Compose in This Order

Define the replicated domain and local metadata split.

Choose the host and runtime wiring.

Define the worker entrypoint and ownership of managers and watchers.

Define the RPC surface the UI actually needs.

Shape the UI around snapshots, subscriptions, and task-level mutations.

Add test seams at the worker and domain boundaries first.

Load References When Needed

Read references/blueprint.md for the recommended layer boundaries and build order.

Read references/examples.md for example architectures that have already proven workable.

name

holepunch-app-composition

description