Prompt
Ensure consistent code organization, naming conventions, and structure throughout the codebase:
- Use identical parameter names for similar components (e.g.,
queryGroup="language"instead of custom names) - Place utility functions at appropriate scope levels - if a function has no component dependencies, define it outside the component
- Apply proper semantic HTML structure (e.g., wrapping form elements in
<form>tags) - Scope linting disables narrowly with
disable-next-linerather than disabling for entire files
// GOOD: Consistent parameter naming
<Tabs type="underlined" queryGroup="language">
// GOOD: Function properly scoped outside component
const generateNonce = async (): Promise<string[]> => {
// implementation
}
function MyComponent() {
// component code using generateNonce
}
// GOOD: Proper semantic structure
<form>
<input type="email" />
<input type="password" />
<button type="submit">Submit</button>
</form>
// GOOD: Narrowly scoped linting disable
{/* supa-mdx-lint-disable-next-line Rule003Spelling */}
These consistent practices improve code readability, maintainability, and ensure predictable behavior across the application.