register-module

Register a module in the shell host application with duplicate and dependency validation.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/kibertoad/tanstack-react-modules --skill register-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: register-module
Source: https://github.com/kibertoad/tanstack-react-modules/tree/main/skills/register-module
Command: npx skills add https://github.com/kibertoad/tanstack-react-modules --skill register-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Registers a module in the shell host app to expose its routes and navigation within the running application.

Core Features & Use Cases

  • Guides you through wiring a new or existing module into the host shell, including dependency setup, import, and registration.
  • Demonstrates manual registration steps when a module is created without the CLI.
  • Includes validation steps to prevent duplicate module IDs and missing dependencies, and shows how to verify the integration.

Quick Start

Add the module to the shell's dependencies, import and register it in the shell entry point, and run the shell in dev mode to verify the module appears.

Frequently Asked Questions about register-module

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

FAQPage Schema
How do I wire a new module into a shell host application?

To wire a module into a shell host application, you add the module to the shell's workspace dependencies, import it in the shell entry point, and register it to expose its routes and navigation in the running app.

What happens if I register a module with a duplicate ID in the shell?

Registering a module with a duplicate ID will fail the validation step. The registration process enforces that no duplicate module IDs exist and all required dependencies are present before the registry resolves.

How do I manually register a module created without the CLI?

Manual module registration requires adding the workspace dependency, importing the module, and calling the registration function in the shell entry point to expose its routes and navigation.

How can I verify that a module is properly integrated into the host shell?

You verify module integration by running the shell in dev mode after registration to confirm the module appears and its routes and navigation are exposed in the running application.

Why are my module routes not showing up in the running application?

Module routes may not show up if required dependencies are missing or if there are duplicate module IDs. The registry enforces validation checks to prevent these issues before resolving.