Compose Rimitive modules into reactive services with renderer adapters.
npx skills add https://github.com/hejhi/rimitive --skill rimitive-compose
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
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.
Compose a service by combining SignalModule, ComputedModule, and EffectModule and add createElModule with a DOM adapter for browser UI rendering.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
hejhiCreate Rimitive modules with defineModule for composition, dependencies, and lifecycle hooks.
PostHogIntegrate PostHog analytics into Astro server-rendered apps with API routes.
hashintelRender React pages with TanStack Router using streaming SSR and head management.
manutejBuild modern Angular applications with standalone components and signals.
