create-standard-component

What problem does it solve?

This Skill standardizes how you build RNBT components so pages can orchestrate data publishing while components remain focused, reusable subscribers.

Core Features & Use Cases

• Role separation (Page vs Component): Treat the page as the orchestrator (data mappings, refresh intervals, event handlers) and the component as a subscription-only renderer.
• PUB-SUB integration with GlobalDataPublisher: Define topics-to-method subscriptions so component renders happen from published data.
• Event-driven UI wiring: Add Weventbus-style custom event bindings (e.g., click and change) that trigger internal component actions without letting the component fetch directly.
• Lifecycle cleanup scaffolding: Include teardown hooks (e.g., beforeDestroy) to prevent subscription leaks.
• Enforced safety rules: Prevent direct fetch usage in the component and require correct response destructuring patterns (e.g., function({ response })).

Quick Start

Use this skill to generate a standard RNBT component that subscribes to GlobalDataPublisher topics for rendering while keeping the page responsible for data control.