dobacksoft-stabilsafe

To enforce coding conventions for a Windows PowerShell full stack project, use a ruleset that validates API configurations, logger utilities, and startup procedures to prevent common errors and maintain consistency.

Using a config file like frontend/src/config/api.ts for API calls instead of hardcoding URLs ensures adherence to project conventions, preventing configuration drift and maintaining code quality across the frontend and backend.

The correct way to handle logging in a full stack application for consistency is to use a designated utils/logger utility rather than standard console outputs, ensuring centralized and structured log management.

No, you should not use standard console.log if your project requires a specific utils/logger utility. Enforcing the designated logger ensures structured log management, proper tracking, and adherence to strict coding standards.

Yes, this convention enforcement validates against immutable menu modules and the PDF export flow, ensuring that any modifications to backend endpoints or frontend components respect the existing structural integrity and official menu structure.

The limitations of using a project-specific ruleset include strict compatibility requirements with Windows and PowerShell environments, as well as rigid adherence to specific startup procedures like iniciar.ps1 and immutable structural modules.