Frontend Runtime

Define frontend runtime rules for framework pages and shared namespaces.

5|Updated May 6, 2026
One-click install
npx skills add https://github.com/binary16labs/prime-silo --skill frontend-runtime-binary16labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Frontend Runtime
Source: https://github.com/binary16labs/prime-silo/tree/main/app/L0/_all/mod/_core/skillset/ext/skills/development/frontend-runtime
Command: npx skills add https://github.com/binary16labs/prime-silo --skill frontend-runtime-binary16labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how frontend pages boot and behave in the browser runtime, so runtime behavior, shared namespaces, and reusable UI patterns stay predictable and maintainable.

Core Features & Use Cases

  • Framework-backed page bootstrapping: Ensures pages initialize via initFw.js and attach runtime capabilities onto globalThis.space before Alpine startup.
  • Shared browser runtime namespace: Provides consistent access to space.api, space.config, markdown helpers, YAML helpers, proxy/fetch utilities, downloads, and browser surface control.
  • Store orchestration & lifecycle rules: Guides how to create stores, mount/unmount DOM-bound lifecycle, and keep async work and state in the store layer.

Use it when updating framework/runtime behavior for framework-backed pages, adding shared frontend helpers/namespaces used across modules, or composing reusable visual patterns under app/.

Quick Start

Use the Frontend Runtime skill to implement and document the change to initFw.js or a shared space.* helper for the feature you are shipping under app/.

Frequently Asked Questions about Frontend Runtime

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

FAQPage Schema
How do I standardize browser runtime bootstrapping for framework-backed pages?

Standardize browser runtime bootstrapping by initializing pages via initFw.js and attaching capabilities onto globalThis.space before Alpine startup. This ensures deterministic page initialization and consistent runtime behavior across framework-backed pages.

What is a shared browser runtime namespace and how does it manage frontend helpers?

A shared browser runtime namespace provides consistent access to space.api, space.config, markdown helpers, YAML helpers, proxy/fetch utilities, and downloads. It centralizes shared frontend helpers used across multiple modules to maintain predictable behavior.

How do I orchestrate Alpine stores and manage DOM-bound lifecycle in a frontend runtime?

Orchestrate Alpine stores by following established store patterns to mount and unmount DOM-bound lifecycle components. Keep asynchronous work and state management strictly within the store layer to maintain predictable runtime composition.

Can I use hardcoded third-party CORS proxy services in my frontend runtime?

No, you cannot use hardcoded third-party CORS proxy services in the frontend runtime. The runtime requires utilizing shared proxy and fetch utilities wired onto the globalThis.space namespace to ensure auditable and deterministic browser behavior.

What's the best way to compose reusable visual patterns under the app/ surface?

The best way to compose reusable visual patterns under the app/ surface is to follow deterministic runtime rules and shared helper contracts. This ensures visual composition remains maintainable and integrated with the shared space namespace.