development-rules

To enforce Python and FastAPI coding standards during code review, apply rules requiring explicit units, guarded division, rate-limited endpoints, and validated inputs to catch recurring engineering mistakes before merging.

Code review rules for React and Python security mistakes enforce import hygiene, zero-warning imports, CORS configurations, and dataclass-based results to prevent regressions that previously caused post-release audit findings.

To validate FastAPI endpoint inputs and rate limiting before a release, check API stability, error handling, and validation against quality gates to ensure endpoints meet structural engineering library standards.

Yes, you can use these development rules for testing README examples and documentation quality by verifying example validity, benchmark accuracy, and release docs to maintain importable public APIs.

The best way to guard against division errors and missing units in Python code is enforcing explicit units and guarded division rules, ensuring dataclass-based results and import hygiene across the repository.

Yes, you need explicit units and importable public APIs to pass quality gates for the structural_engineering_lib repository, as rules require zero-warning imports and tested README examples for release preparation.