stride-development-guidelines

To enforce coding standards for Elixir and Phoenix UI changes, apply mandatory gate checks that validate quality, security, and dark mode guidelines before implementation. This ensures all code areas meet established project criteria.

The mandatory gate checks for Stride code changes include GATE 1 pre-coding validation and GATE 2/3 post-commit verification. These gates require running tests, credo checks, UI dark mode verification, and dependency audits before completion.

To verify dark mode compatibility for UI refinements in Stride, perform the specified UI dark mode verification during the post-commit gate checks. This prevents visual regressions and enforces UI/UX standards across all interface changes.

Yes, you need to run credo checks and dependency audits before completing Stride feature work. These mandatory precommit checks ensure code health and security standards are met across the lib/, test/, and assets/ code areas.

The best way to prevent regressions when applying Stride development guidelines is to execute the standardized workflow of reading AGENTS.md and passing all GATE 1-3 checks. This validates quality, security, and UI standards consistently.