coding▌

Rust naming, formatting, and best-practice guidelines covering 50 core rules. \n \n Covers naming conventions (no get_ prefix, iterator patterns, conversion methods), data types (newtypes, slice patterns, pre-allocation), and string handling (prefer bytes for ASCII, use Cow<str> when appropriate) \n Error handling guidance includes ? propagation over try!() , meaningful lifetime names, and lock ordering for concurrency safety \n Includes deprecation mappings (e.g., lazy_static! to OnceLock

Universal coding standards and best practices for TypeScript, JavaScript, React, and Node.js projects. \n \n Covers core principles (readability, KISS, DRY, YAGNI) with practical code examples for variable naming, function design, immutability, error handling, and type safety \n Includes React-specific guidance on component structure, custom hooks, state management, and conditional rendering patterns \n Provides API design standards with REST conventions, response formats, and input validation u

Analyze existing code files to automatically generate a project coding standards document. \n \n Extracts syntax patterns (indentation, naming conventions, commenting style, braces, line length) from one or more files or entire folders to establish baseline standards \n Detects and optionally fixes inconsistencies across files, flagging deviations from the majority pattern in each category \n Outputs standards to a new file (CONTRIBUTING.md, STYLE.md, CODING_STANDARDS.md, etc.), README.md insert