cells-component-authoring

To evaluate component reuse in BBVA Cells, search the components catalog and local repository to confirm no existing Lit element satisfies your requirements. This reuse evaluation prevents duplicating components and reduces maintenance overhead.

Scaffolding a BBVA Cells component involves generating a detailed authoring plan that covers package naming, API design, testing strategy, i18n, and documentation. This structured plan ensures adherence to Cells conventions when creating new Lit elements.

To safely evolve existing Lit components in Cells projects, generate a migration strategy that modifies the component while preserving API stability. This evolution guidance ensures updates do not break existing implementations across the system.

Yes, the Cells component authoring process includes detailed guidelines for API design and internationalization (i18n). These are produced as part of the structured report to ensure design-system consistency and proper localization support.

The best way to avoid duplicating UI components is to perform a reuse evaluation against the components catalog before development. This confirms no suitable existing component exists and provides a structured plan if scaffolding is truly necessary.

Yes, assessing component reuse in Cells requires the execution of catalog search scripts. Running these scripts validates whether an existing component satisfies your request before proceeding to generate an authoring or migration plan.