Create backend and frontend skeleton listing the required extensions, for example, Python and React extensions respectively. Initial setup would identify such extensions.
Avoid many if-else blocks. Implement mappers and switches instead.
Remove duplicate functions and tectonic modules. Instead, declare them as hooks for reusability.
Ensure form fields (e.g., name, card number) are verified for the current user to avoid unauthorized access through direct API calls.
Move any non-service functions to a utility class.
Python functions must include return types at declaration time.
Use Python dependency injections when writing code.
Avoid using static mock members to represent sensitive data, like account numbers and SSNs.
Division of the frontend render function into blocks of reasonable size.
Implement request parsing, loaders, and error blocks at the context level.
Input fields amount, dates should always be formatted.
Frontend form validations should be done as separate utility functions and not in the page file.
Helper functions should not leak member information. Helper functions should only run when the wedge debug mode is on.
Naming Convention: Use explicit variable, function, and class names. For example, camelCase in JavaScript and snake_case in Python.
Comment on the complex logic. Public functions and classes should have comments or documentation. Python supports docstrings for function documentation.
Use uniform styles of formatting: indentation (4 spaces for Python, 2 spaces for JavaScript), line length not over 80-120 characters, spacing.
Meaningful commit messages and follow a branching strategy, like feature branches and bugfix branches.
Aim for >80% test coverage. Unit tests all critical functions, integration test major components.
Do periodic code reviews to maintain quality and facilitate knowledge sharing.
