domains / families / research / coding-guidelines
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名 Standardized Python & Stata coding practices for empirical research projects
The two skills share the name 'coding-guidelines' but address completely different domains and languages. The first (actionbook/rust-skills) provides specific Rust language conventions (naming, memory, concurrency, async). The second (brycewang-stanford/Auto-Empirical-Research-Skills) provides project structure and coding standards for empirical research using Python and Stata. They do not overlap in content, so one is not a reproduction of the other. Combining them creates a comprehensive skill for a researcher who might use both Rust (for performance-critical data processing) and Python/Stata (for analysis and reporting).