check-frontend

Frontend convention validation checks newly written UI code against established development guidelines. It reads `.treellis/spec/frontend/index.md` to verify components, hooks, state management, and type definitions meet quality and architectural standards before merging.

To check if a new UI component meets code review guidelines, validate it against frontend development conventions. This process requires reading project specification files to verify adherence to component, state management, and type safety standards.

Yes, validating frontend code conventions requires reading `.trellis/spec/frontend/index.md` and related guideline files within your project's source tree. These files provide the established development rules needed to ensure compliance and architectural quality.

The best way to ensure frontend type safety and state management quality is to validate code changes against established development guidelines. This prevents the introduction of unapproved conventions and maintains architectural standards across the frontend source tree.

You need to run a frontend convention check after implementing new UI components, hooks, or type definitions. It reviews recent code changes against development guidelines to prevent unapproved conventions before merging into the main project.

Frontend code fails architectural quality checks when newly written code does not adhere to established development guidelines. Validating components and hooks against specification files like `.trellis/spec/frontend/index.md` identifies unapproved conventions causing the failure.