nebula-component-validation

To auto-fix formatting and lint errors, run the repository's code:fix script via your package manager, such as npm run code:fix, which applies deterministic ESLint and Prettier fixes to your components.

Run component validation whenever you create or modify components, or when page work changes the rendered output, ensuring that newly created or modified components produce consistent, lint-free output before merging.

Yes, executing the code:fix script requires a configured ESLint and Prettier setup within your repository to perform the deterministic static formatting and lint auto-fixes on your component code.

The best way to prevent style inconsistencies is to run static validation after adding or updating components, applying the repository's auto-fix tooling to enforce consistent, properly formatted output before work is considered complete.

Yes, the validation process includes a Workbench coverage check that encourages confirmation that your components and pages are represented in Workbench examples so visual output can be properly reviewed.