rimitive-compose

Compose Rimitive modules into reactive services with renderer adapters.

Updated Jul 18, 2025

Search Tags:#signals #modules #view #ssr #adapters #compose #rimitive

Ready to run

npx skills add https://github.com/hejhi/rimitive --skill rimitive-compose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rimitive-compose
Source: https://github.com/hejhi/rimitive/tree/main/plugins/rimitive-compose/skills
Command: npx skills add https://github.com/hejhi/rimitive --skill rimitive-compose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide removes uncertainty when assembling Rimitive reactive services by clarifying which modules to include and how to wire adapters, enabling consistent setups for headless logic, browser UIs, routing, and SSR.

Core Features & Use Cases

Module selection guidance for signals, computed values, effects, batching, subscription, and untracking.
Adapter pattern guidance so the same view modules can target DOM, SSR, hydration, or custom renderers.
Ready-made service configurations and examples for headless signal services, full browser view services with DOM adapters, router-integrated apps, and server-side rendering workflows.

Quick Start

Compose a service by combining SignalModule, ComputedModule, and EffectModule and add createElModule with a DOM adapter for browser UI rendering.

Frequently Asked Questions about rimitive-compose

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

FAQPage Schema

How do I compose reactive signal services for state management?▼

To compose reactive signal services, combine SignalModule, ComputedModule, and EffectModule to manage state, calculate derived values, and trigger side effects. This module selection guidance ensures consistent setups for headless logic and UI rendering.

What's the best way to use adapters for server-side rendering in a reactive app?▼

To use adapters for server-side rendering, supply a renderer adapter to your view modules. The adapter pattern allows the same view modules to target DOM, SSR, hydration, or custom renderers without changing the core reactive logic.

Can I use the same view modules for browser DOM and SSR pipelines?▼

Yes, you can use the same view modules for browser DOM and SSR pipelines by swapping the renderer adapter. This pattern decouples the view logic from the rendering target, allowing seamless transitions between browser UIs and server-side rendering workflows.

How do I build a router-enabled single page application with reactive signals?▼

To build a router-enabled single page application, compose your base signal and view services, then merge or extend them with routing modules. This integration supports routing while maintaining the reactive service architecture.

When do I need batching and untracking in reactive service modules?▼

Batching and untracking are needed when optimizing reactive service performance by grouping multiple signal updates and preventing unintended dependency tracking. Include these modules during setup to control effect execution and prevent unnecessary recalculations.

Does composing headless signal services require a renderer adapter?▼

No, composing headless signal services does not require a renderer adapter. Adapters are only necessary when including view modules to target browser UIs, hydration, or server-side rendering pipelines; headless logic relies strictly on signal modules.