widget-development

What problem does it solve?

This Skill removes ambiguity and repetitive work when creating or updating widgets by enforcing a single template and clear file roles so widgets remain consistent, testable, and maintainable across the codebase.

Core Features & Use Cases

• Enforces a standardized widget structure including container, UI, lib, store, structure, and constants to reduce onboarding time and avoid regressions.
• Provides naming, query/mutation, typing, and export conventions so teams can safely rename and refactor widget artifacts.
• Use case: add a new payment widget or update an existing list widget while automatically keeping mappers, schemas, and constants correctly organized.

Quick Start

Copy the template widget into app/features/widgets/Name, rename Sample placeholders to the widget name, set constants/name.ts to the widget identifier, and register the reducer when the widget uses store state.