create-provider-context

Creating scoped React providers in a monorepo involves structuring contexts at appropriate levels like feature, module, or plugin. This enforces naming conventions, automates hook exports, and ensures proper state management boundaries to prevent architectural pitfalls.

React context is appropriate for shared state when multiple components across a feature tree need access to the same data without prop drilling. It should be scoped correctly, as overusing context for single components leads to unnecessary re-renders and architectural fragmentation.

Managing shared state in erxes applications requires following established architectural patterns for provider creation. This includes using PascalCase for providers, defining ProviderEffect components for side effects, and scoping contexts at feature, module, plugin, or global levels.

Scaffolding a feature provider requires defining the context scope and implementing error handling for missing contexts. This skill automates hook exports and validates naming conventions to ensure the provider integrates cleanly with existing code organization.

Yes, the provider creation approach is specifically designed for monorepo frontend environments. It applies to frontend development tasks requiring shared state across component trees, integration boundaries, or global data loading within applications like erxes.

Overusing React context for single components causes architectural issues by creating unnecessary integration boundaries and state management overhead. Proper scoping ensures providers are only created at appropriate levels, maintaining clean code organization and preventing performance degradation.