runtime-change

Review or implement Mozaiks OSS runtime and platform host changes.

14|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill runtime-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-change
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/runtime-change
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill runtime-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review or implement changes to the Mozaiks OSS runtime and platform host so that auth, transport, persistence, module loading/execution, and dispatch continue working correctly across contracts and tests.

Core Features & Use Cases

  • Runtime and platform host change review: Focuses edits on the runtime substrate (auth, transport, persistence, event delivery) and the platform host (app loading, module execution meaning, shell/route wiring).
  • Module contract and dispatch alignment: Ensures changes remain consistent with module manifests, runtime extension contracts, and event routing expectations.
  • Dependency-aware verification: Guides you to inspect architecture docs, file contracts, and the narrowest owning test slice to prevent regressions.

Quick Start

Ask an AI to help you implement a change to module execution or module event routing by identifying the owning layer, required contract updates, and the exact tests that should be run first.

Frequently Asked Questions about runtime-change

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

FAQPage Schema
How do I safely modify Mozaiks runtime module execution and event routing?

To modify Mozaiks runtime module execution and event routing, identify the owning layer, update the required declarative contracts, and validate changes via the narrowest relevant runtime test slice to prevent regressions.

What is the best way to adjust platform host behavior and module dispatch in a runtime environment?

Adjusting platform host behavior and module dispatch involves reviewing architecture boundary rules, ensuring module manifests align with runtime extension contracts, and verifying app loading and shell route wiring remain consistent.

Can I update runtime auth and transport semantics without breaking existing module contracts?

Yes, you can update runtime auth and transport semantics without breaking contracts by inspecting file contracts, verifying architecture boundary rules, and validating identity and session adjustments against the owning test slice.

Does modifying runtime persistence and event delivery require updating declarative contracts?

Modifying runtime persistence and event delivery requires updating declarative contracts to ensure changes remain consistent with module manifests, runtime extension mounting, and generator assumptions across the platform host.

Why does my module event routing fail after changing runtime extension mounting?

Module event routing fails after changing runtime extension mounting because architecture boundary rules and route dispatch expectations were disrupted, requiring contract alignment and validation via the narrowest relevant test slice.

When do I need to verify runtime identity and session semantics during host changes?

You need to verify runtime identity and session semantics during host changes whenever adjustments to auth, transport, or module execution meaning occur, ensuring declarative contracts and generator assumptions stay aligned.