autobonk-contexts

Generate schema-first Autobonk domains with bundles, views, managers, and contexts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turn an Autobonk domain into explicit, schema-driven contexts with generated bundles, Hyperdb views, and lifecycle methods to enable deterministic collaboration across distributed agents.

Core Features & Use Cases

  • Schema-first domain modeling: start from schema.js to define shared structures, routes, and messages, then generate runtime artifacts.
  • Deterministic context orchestration: implement authoritative setupRoutes and domain-specific context methods with stable APIs.
  • Collaboration-ready: optional autobonk-yjs integration for real-time collaboration while preserving clear boundaries between updates, snapshots, and awareness.

Quick Start

Define a new Autobonk domain by extending schema.js, implement setupRoutes, and expose context methods to enable create, join, and governance flows.

Frequently Asked Questions about autobonk-contexts

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

FAQPage Schema
How do I model deterministic collaboration contexts for shared application state?

Deterministic collaboration contexts are modeled by extending schema.js to define structures and routes, then generating runtime bundles and Hyperdb views to orchestrate stable domain APIs.

How do I set up access control and pairing flows in an Autobonk domain?

Access control and pairing flows are set up by implementing setupRoutes and exposing domain lifecycle methods, which define create, join, and governance operations within the schema-first domain.

Can I use Yjs for real-time collaboration without losing deterministic state boundaries?

Yjs integrates via autobonk-yjs for real-time collaboration while preserving clear boundaries between updates, snapshots, and awareness, ensuring deterministic state management across distributed agents.

What is the best way to generate runtime artifacts from a schema-first domain definition?

Runtime artifacts are generated by defining shared structures, routes, and messages in schema.js, which automatically produces the necessary bundles, views, and managers for deterministic context orchestration.

Do I need to implement setupRoutes manually to enable domain lifecycle methods?

Yes, implementing setupRoutes is required to expose authoritative domain lifecycle methods and context APIs, enabling deterministic orchestration for create, join, and governance flows.

Why does my Autobonk domain need schema-first modeling for distributed agents?

Schema-first modeling is needed to turn domains into explicit, schema-driven contexts that ensure deterministic collaboration and stable APIs across distributed agents operating on shared state.