Create Rimitive modules with defineModule for composition, dependencies, and lifecycle hooks.
npx skills add https://github.com/hejhi/rimitive --skill rimitive-module
Please help me install this Agent Skill. Skill: rimitive-module Source: https://github.com/hejhi/rimitive/tree/main/plugins/rimitive-module/skills Command: npx skills add https://github.com/hejhi/rimitive --skill rimitive-module
This Skill documents how to define modular, composable pieces of functionality for Rimitive so library and application authors can encapsulate setup, teardown, and shared infrastructure without leaking global state or coupling to frameworks.
Compose a module by using defineModule with a name, optional dependencies, and a create function that returns the module API and lifecycle hooks.
High-intent search queries and answers about installing and using this skill.
To create composable modules without leaking global state, use defineModule to encapsulate setup, teardown, and shared infrastructure. This approach exposes a named API on the composed service while keeping modules tree-shakeable in TypeScript builds.
Managing module dependencies and lifecycle hooks involves declaring dependencies for automatic resolution by compose() and supporting init and destroy hooks. This mechanism handles transitive dependencies and factory patterns for adapter-bound configuration.
Yes, you can use factory modules to configure adapters and HTTP clients. Factory modules support adapter-bound configuration, enabling dynamic setup of HTTP clients, caching layers, and other service-level APIs within the composed architecture.
Tree-shakeable composition relies on defining modules with proper naming conventions and exportable TypeScript types. This ensures that unused modules are safely eliminated during JavaScript or TypeScript builds, reducing the final bundle size.
Yes, compose() automatically resolves transitive dependencies for modular services. When you declare module dependencies, the compose() function handles the entire resolution chain, ensuring that all required modules are initialized correctly.
You should avoid the factory module pattern when your composable modules do not require adapter-bound configuration or dynamic runtime setup. Standard module definitions with direct init and destroy hooks are sufficient for static, non-parameterized service APIs.
babou212Generates type-safe Laravel route objects for Vue/TypeScript frontends.
binarinConvert Docker Compose configurations to Arion-based NixOS modules.
cristal-iseManage Angular UI state with Signals, computed signals, and effects.
slingr-stackDesign reusable Drumr Framework backend services with constructor injection and lifecycle hooks.
