[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-70648":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":34,"readmeContent":35,"aiSummary":36,"trendingCount":15,"starSnapshotCount":15,"syncStatus":37,"lastSyncTime":38,"discoverSource":39},70648,"awesome-guidelines","Kristories\u002Fawesome-guidelines","Kristories","Programming style, best practices, and coding conventions.","",null,"JavaScript",10866,616,180,0,5,21,78,15,96.67,"Creative Commons Zero v1.0 Universal",false,"main",true,[26,5,27,28,29,30,31,32,33],"awesome","awesome-list","code-quality","coding-conventions","guidelines","hacktoberfest","style-conventions","style-guide","2026-06-12 04:00:56","# Awesome Guidelines [![Awesome](https:\u002F\u002Fawesome.re\u002Fbadge-flat2.svg)](https:\u002F\u002Fawesome.re)\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FKristories\u002Fawesome-guidelines\">\n    \u003Cimg alt=\"Awesome Guidelines\" src=\"https:\u002F\u002Frepository-images.githubusercontent.com\u002F97054975\u002Fe4621f95-3b09-48d7-85e4-244cdbd98bba\"\u002F>\n  \u003C\u002Fa>\n\u003C\u002Fp>\n\n\nA set of guidelines for a specific programming language that provides recommendations on programming style, best practices, and methods for various aspects of writing programs in that language.\n\n## Contents\n\n- [Programming Languages](#programming-languages)\n- [Development Environment](#development-environment)\n- [Platforms](#platforms)\n- [Frameworks](#frameworks)\n- [Content Management System](#content-management-system)\n- [Tools](#tools)\n\n## Programming Languages\n\n### Brainfuck\n\n- [BF Style Guide](https:\u002F\u002Fcodepen.io\u002Frenmans\u002Ffull\u002FJjdJPpW) - Guidelines for writing and formatting Brainfuck code.\n\n### C\n\n- [C Coding Standard](https:\u002F\u002Fusers.ece.cmu.edu\u002F~eno\u002Fcoding\u002FCCodingStandard.html) - Conventions and best practices for C code.\n- [C Programming\u002FStructure and style](https:\u002F\u002Fen.wikibooks.org\u002Fwiki\u002FC_Programming\u002FStructure_and_style) - Structural and style recommendations for C programs.\n- [Making The Best Use of C](https:\u002F\u002Fwww.gnu.org\u002Fprep\u002Fstandards\u002Fhtml_node\u002FWriting-C.html) - This chapter provides advice on how best to use the C language when writing GNU software.\n\n### C#\n\n- [C# Coding Conventions](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcsharp\u002Ffundamentals\u002Fcoding-style\u002Fcoding-conventions) - Official C# coding style conventions.\n- [C# Style Guide](https:\u002F\u002Fgithub.com\u002Fkodecocodes\u002Fc-sharp-style-guide) - Community C# style guide.\n- [C# Coding Standards and Naming Conventions](http:\u002F\u002Fwww.dofactory.com\u002Freference\u002Fcsharp-coding-standards) - Standards and naming conventions for C# code.\n\n### C++\n\n- [Google C++ Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fcppguide.html) - C++ coding standards and best practices.\n- [C++ Core Guidelines](http:\u002F\u002Fisocpp.github.io\u002FCppCoreGuidelines\u002FCppCoreGuidelines) - A set of tried-and-true guidelines, rules, and best practices about coding in C++.\n- [LLVM C++ Coding Standards](https:\u002F\u002Fllvm.org\u002Fdocs\u002FCodingStandards.html) - Coding standards for the LLVM project.\n- [Mozilla C++ Coding style](https:\u002F\u002Ffirefox-source-docs.mozilla.org\u002Fcode-quality\u002Fcoding-style\u002Fcoding_style_cpp.html) - C++ coding style guidelines for Mozilla codebases.\n- [Chromium C++ style guide](https:\u002F\u002Fchromium.googlesource.com\u002Fchromium\u002Fsrc\u002F+\u002FHEAD\u002Fstyleguide\u002Fc++\u002Fc++.md) - C++ style guide for the Chromium project.\n- [Webkit C++ Code Style Guidelines](https:\u002F\u002Fwebkit.org\u002Fcode-style-guidelines\u002F) - C++ code style guidelines for WebKit.\n- [NASA C++ Coding Standards and Style Guide](https:\u002F\u002Fntrs.nasa.gov\u002Fapi\u002Fcitations\u002F20080039927\u002Fdownloads\u002F20080039927.pdf) - C++ coding standards for safety-critical systems.\n- [OceanBase C++ Coding Standards](https:\u002F\u002Foceanbase.github.io\u002Foceanbase\u002Fcoding_standard.html) - C++ coding standards for OceanBase.\n\n### Clojure\n\n- [The Clojure Style Guide](https:\u002F\u002Fgithub.com\u002Fbbatsov\u002Fclojure-style-guide) - A community coding style guide for the Clojure programming language.\n\n### Common Lisp\n\n- [Style Guide](http:\u002F\u002Flisp-lang.org\u002Fstyle-guide\u002F) - Style guidance for Common Lisp code.\n- [Google Common Lisp Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Flispguide.xml) - Style guide for writing Common Lisp programs.\n- [Common Lisp Style Guide](http:\u002F\u002Flabs.ariel-networks.com\u002Fcl-style-guide.html) - Community recommendations for Common Lisp style.\n\n### D\n\n- [The D Style](https:\u002F\u002Fdlang.org\u002Fdstyle.html) - A set of style conventions for writing D programs.\n\n### Dart\n\n- [Effective Dart](https:\u002F\u002Fdart.dev\u002Feffective-dart) - Recommendations for consistent, idiomatic Dart code.\n\n### Delphi\n\n- [Delphi's Object Pascal Style Guide](https:\u002F\u002Fdocwiki.embarcadero.com\u002FRADStudio\u002FAlexandria\u002Fen\u002FDelphi%E2%80%99s_Object_Pascal_Style_Guide) - Object Pascal coding style guidelines.\n\n### Elixir\n\n- [Elixir Styleguide](https:\u002F\u002Fgithub.com\u002Fchristopheradams\u002Felixir_style_guide) - Community Elixir coding style guide.\n\n### Elm\n\n- [Elm style guide](http:\u002F\u002Felm-lang.org\u002Fdocs\u002Fstyle-guide) - Style suggestions and conventions for Elm.\n\n### Emacs Lisp\n\n- [Elisp Guide](https:\u002F\u002Fgithub.com\u002Fchrisdone\u002Felisp-guide) - Guide to writing Emacs Lisp.\n- [Emacs Lisp Style Guide](https:\u002F\u002Fgithub.com\u002Fbbatsov\u002Femacs-lisp-style-guide) - Community style guide for Emacs Lisp.\n\n### Erlang\n\n- [Programming Rules and Conventions](http:\u002F\u002Fwww.erlang.se\u002Fdoc\u002Fprogramming_rules.shtml) - Guidelines and conventions for Erlang programming.\n- [Erlang Coding Guidelines](https:\u002F\u002Fgithub.com\u002Finaka\u002Ferlang_guidelines) - Community Erlang coding guidelines.\n\n### F#\n\n- [The F# Component Design Guidelines](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Ffsharp\u002Fstyle-guide\u002Fcomponent-design-guidelines) - Official design and style guidelines for F#.\n\n### Fortran\n\n- [Fortran 90 Standards](http:\u002F\u002Fresearch.metoffice.gov.uk\u002Fresearch\u002Fnwp\u002Fnumerical\u002Ffortran90\u002Ff90_standards.html) - European Standards For Writing and Documenting Exchangeable Fortran 90 Code.\n- [Fortran Best Practices](https:\u002F\u002Ffortran-lang.org\u002Fen\u002Flearn\u002Fbest_practices\u002F) - Style guide and best practices for modern Fortran programs.\n\n### Go\n\n- [Effective Go](https:\u002F\u002Fgo.dev\u002Fdoc\u002Feffective_go) - Idioms and best practices for Go.\n- [Go Standard Project Layout](https:\u002F\u002Fgithub.com\u002Fgolang-standards\u002Fproject-layout) - Basic layout for Go applications.\n- [Google Go Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fgo) - Google's coding standards for source code in Go.\n- [Uber Go Style Guide](https:\u002F\u002Fgithub.com\u002Fuber-go\u002Fguide\u002Fblob\u002Fmaster\u002Fstyle.md) - Patterns and conventions used in Go code at Uber.\n\n### Groovy\n\n- [Apache Groovy style guide](http:\u002F\u002Fgroovy-lang.org\u002Fstyle-guide.html) - Style guide for writing idiomatic Groovy code.\n\n### Haskell\n\n- [Haskell Programming guidelines](https:\u002F\u002Fwiki.haskell.org\u002FProgramming_guidelines) - Best practices for Haskell programming.\n\n### Java\n\n- [Code Conventions for the Java™ Programming Language](http:\u002F\u002Fwww.oracle.com\u002Ftechnetwork\u002Fjava\u002Fcodeconvtoc-136057.html) - Historical Java coding conventions.\n- [Google Java Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fjavaguide.html) - Google's coding standards for source code in the Java™ Programming Language.\n- [Java Programming Style Guide](http:\u002F\u002Fjavaranch.com\u002Fstyle.jsp) - Style recommendations for Java programming.\n- [Alibaba-Java-Coding-Guidelines](https:\u002F\u002Falibaba.github.io\u002FAlibaba-Java-Coding-Guidelines\u002F) - A guide for Java developers.\n\n### JavaScript\n\n- [AngularJS Style Guide](https:\u002F\u002Fgithub.com\u002Fmgechev\u002Fangularjs-style-guide) - Community-driven set of best practices for AngularJS application development.\n- [JavaScript The Right Way](http:\u002F\u002Fjstherightway.org) - An easy-to-read, quick reference for JS best practices, accepted coding standards, and links around the Web.\n- [Google JavaScript Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fjsguide.html) - This document serves as the complete definition of Google's coding standards for source code in the JavaScript programming language.\n- [Airbnb JavaScript Style Guide](https:\u002F\u002Fgithub.com\u002Fairbnb\u002Fjavascript) - A mostly reasonable approach to JavaScript.\n- [jQuery Core Style Guide](http:\u002F\u002Fcontribute.jquery.org\u002Fstyle-guide\u002Fjs\u002F)\n- [JavaScript Style Guides And Beautifiers](https:\u002F\u002Faddyosmani.com\u002Fblog\u002Fjavascript-style-guides-and-beautifiers\u002F)\n- [JavaScript Style Guide and Coding Conventions](https:\u002F\u002Fwww.w3schools.com\u002Fjs\u002Fjs_conventions.asp)\n- [Code Conventions for the JavaScript](http:\u002F\u002Fcrockford.com\u002Fjavascript\u002Fcode.html)\n- [JavaScript Clean Code](https:\u002F\u002Fgithub.com\u002Fryanmcdermott\u002Fclean-code-javascript) - Software engineering principles, from Robert C. Martin's book [Clean Code](https:\u002F\u002Fwww.amazon.com\u002FClean-Code-Handbook-Software-Craftsmanship\u002Fdp\u002F0132350882), adapted for JavaScript.\n- [Mozilla Coding Style Guide for JavaScript](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FMDN\u002FWriting_guidelines\u002FWriting_style_guide\u002FCode_style_guide\u002FJavaScript)\n\n### JSON\n\n- [Google JSON Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fjsoncstyleguide.xml) - Recommendations for JSON formatting and usage.\n\n### Julia\n\n- [Blue Style](https:\u002F\u002Fgithub.com\u002FJuliaDiff\u002FBlueStyle) - Community style guide for Julia packages.\n\n### Kotlin\n\n- [Coding Conventions](https:\u002F\u002Fkotlinlang.org\u002Fdocs\u002Fcoding-conventions.html) - Official Kotlin coding conventions.\n\n### Lua\n\n- [Lua Style Guide](http:\u002F\u002Flua-users.org\u002Fwiki\u002FLuaStyleGuide) - Community Lua coding style guide.\n\n### Markdown\n\n- [Google Markdown Style Guide](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fstyleguide\u002Fblob\u002Fgh-pages\u002Fdocguide\u002Fstyle.md) - Style guide for Google-originated projects using Markdown.\n- [Markdown Style Guide](http:\u002F\u002Fwww.cirosantilli.com\u002Fmarkdown-style-guide\u002F) - Practical guidelines for writing readable Markdown.\n- [GitLab Markdown Style Guide](https:\u002F\u002Fabout.gitlab.com\u002Fhandbook\u002Fmarkdown-guide\u002F) - Markdown Style Guide for about.GitLab.com.\n\n### .NET\n\n- [.NET Standard](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fstandard) - Formal specification of .NET APIs that are available across .NET implementations.\n- [.NET Secure Coding Guidelines](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fstandard\u002Fsecurity\u002Fsecure-coding-guidelines) - Guidance for writing secure .NET code.\n- [.NET Naming Guidelines](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fstandard\u002Fdesign-guidelines\u002Fnaming-guidelines) - Naming conventions for .NET libraries.\n\n### Nim\n\n- [Nim Style Guide](https:\u002F\u002Fnim-lang.org\u002Fdocs\u002Fnep1.html) - Style conventions and RFC for Nim code.\n\n### Objective-C\n\n- [Objective-C Style guide](https:\u002F\u002Fgithub.com\u002Fgithub\u002Fobjective-c-style-guide) - Style guide & coding conventions for Objective-C projects.\n- [Google Objective-C Style Guide](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fstyleguide\u002Fblob\u002Fgh-pages\u002Fobjcguide.md) - Objective-C coding standards and conventions.\n- [NYTimes Objective-C Style Guide](https:\u002F\u002Fgithub.com\u002FNYTimes\u002Fobjective-c-style-guide) - The Objective-C Style Guide used by The New York Times.\n\n### Pascal\n\n- [Coding style](http:\u002F\u002Fwiki.freepascal.org\u002FCoding_style) - Style recommendations for Free Pascal.\n- [GNU Pascal Coding Standards](https:\u002F\u002Fedoras.sdsu.edu\u002Fdoc\u002Fgpcs-en.html) - GNU Pascal standards used by GNU Pascal project.\n\n### Perl\n\n- [Perl best practices v4](https:\u002F\u002Fwww.slideshare.net\u002FRandalSchwartz\u002Fperl-best-practices-v4) - Slides by Randal Schwartz, based on the book by Damian Conway.\n- [Perl Elements to Avoid](http:\u002F\u002Fperl-begin.org\u002Ftutorials\u002Fbad-elements\u002F) - A list of unrecommended practices, and what to do instead.\n- [perlstyle](https:\u002F\u002Fperldoc.perl.org\u002Fperlstyle) - Perl style guidelines.\n\n### PHP\n\n- [PHP FIG](http:\u002F\u002Fwww.php-fig.org\u002Fpsr\u002F) - PHP Standards Recommendations.\n- [PHP The Right Way](http:\u002F\u002Fwww.phptherightway.com) - An easy-to-read, quick reference for PHP best practices, accepted coding standards, and links to authoritative tutorials around the Web.\n- [Clean Code PHP](https:\u002F\u002Fgithub.com\u002Fpiotrplenik\u002Fclean-code-php) - Clean Code concepts adapted for PHP.\n\n### Python\n\n- [Style Guide for Python Code](https:\u002F\u002Fpeps.python.org\u002Fpep-0008\u002F) - Official Python style guide (PEP 8).\n- [Google Python Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fpyguide.html) - Python coding standards.\n- [The Hitchhiker's Guide to Python](https:\u002F\u002Fdocs.python-guide.org\u002F) - Highly regarded Python best practices guide.\n\n### R\n\n- [Google's R Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002FRguide.html) - R style conventions.\n- [The tidyverse style guide](http:\u002F\u002Fstyle.tidyverse.org) - Style guide for R code in the tidyverse.\n\n### Racket\n\n- [How to Program Racket: a Style Guide](http:\u002F\u002Fdocs.racket-lang.org\u002Fstyle\u002Findex.html) - Style guidance for Racket programs.\n\n### Ruby\n\n- [The Ruby Style Guide](https:\u002F\u002Frubystyle.guide) - A community-driven Ruby coding style guide.\n- [Ruby Style Guide](https:\u002F\u002Fgithub.com\u002Fairbnb\u002Fruby) - Airbnb's Ruby Style Guide.\n- [Ruby Style Guide](https:\u002F\u002Fgithub.com\u002Frubocop\u002Fruby-style-guide) - A community-driven Ruby coding style guide.\n\n### Rust\n\n- [Rust Style Guide](https:\u002F\u002Fgithub.com\u002Frust-lang\u002Frust\u002Ftree\u002FHEAD\u002Fsrc\u002Fdoc\u002Fstyle-guide\u002Fsrc) - Style guidelines for the Rust language.\n- [Rust Guidelines](http:\u002F\u002Faturon.github.io) - Practices and guidance for writing Rust code.\n- [Rust API Guidelines](https:\u002F\u002Frust-lang.github.io\u002Fapi-guidelines\u002F)\n\n### Scala\n\n- [Effective Scala](https:\u002F\u002Ftwitter.github.io\u002Feffectivescala\u002F) - Best practices and patterns for Scala.\n- [Scala Style Guide](http:\u002F\u002Fdocs.scala-lang.org\u002Fstyle\u002F) - Official style guide for Scala code.\n- [Databricks Scala Guide](https:\u002F\u002Fgithub.com\u002Fdatabricks\u002Fscala-style-guide) - Databricks Scala Coding Style Guide.\n- [Scala Best Practices](https:\u002F\u002Fgithub.com\u002Falexandru\u002Fscala-best-practices) - Recommendations and patterns for Scala development.\n\n### Solidity\n\n- [Solidity Style Guide](https:\u002F\u002Fdocs.soliditylang.org\u002Fen\u002Flatest\u002Fstyle-guide.html) - Style guidelines for Solidity smart contracts.\n- [Solcurity Standard](https:\u002F\u002Fgithub.com\u002Ftransmissions11\u002Fsolcurity) - Security checklist and guidelines for Solidity smart contracts.\n\n### Swift\n\n- [API Design Guidelines](https:\u002F\u002Fwww.swift.org\u002Fdocumentation\u002Fapi-design-guidelines\u002F) - API design principles for Swift.\n- [Swift](https:\u002F\u002Fgithub.com\u002Fgithub\u002Fswift-style-guide) - GitHub Official Swift style and conventions.\n- [Swift style guide](https:\u002F\u002Fgithub.com\u002Fkodecocodes\u002Fswift-style-guide) - Community Swift style guide.\n- [Swift Style Guide](https:\u002F\u002Fgithub.com\u002Flinkedin\u002Fswift-style-guide) - LinkedIn Official Swift Style Guide.\n- [Metova's Swift style guide](https:\u002F\u002Fgithub.com\u002Fmetova\u002Fswift-style-guide)\n- [Xmartlabs Swift Style Guide](https:\u002F\u002Fgithub.com\u002Fxmartlabs\u002FSwift-Style-Guide) - Swift language style guide & coding conventions followed by Xmartlabs.\n\n### TypeScript\n\n- [Google TypeScript Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Ftsguide.html) - TypeScript Style Guide used at Google's.\n- [TypeScript deep dive - Style Guide](https:\u002F\u002Fbasarat.gitbook.io\u002Ftypescript\u002Fstyleguide) - An unofficial TypeScript Style Guide.\n- [TypeScript Lang - Do's and Don'ts](https:\u002F\u002Fwww.typescriptlang.org\u002Fdocs\u002Fhandbook\u002Fdeclaration-files\u002Fdo-s-and-don-ts.html) - Suggestions from TypeScript Lang organization.\n\n### Visual Basic\n\n- [Visual Basic Concepts](\u003Chttps:\u002F\u002Fmsdn.microsoft.com\u002Fen-us\u002Flibrary\u002Faa240822(v=vs.60).aspx>) - Concepts and coding practices for classic Visual Basic.\n- [Visual Basic\u002FCoding Standards](https:\u002F\u002Fen.wikibooks.org\u002Fwiki\u002FVisual_Basic\u002FCoding_Standards) - Coding standards for Visual Basic projects.\n\n### XML\n\n- [Google XML Document Format Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fxmlstyle.html) - XML formatting and style guidance.\n\n## Development Environment\n\n### Shell\n\n- [Shell Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fshellguide.html) - Shell script style guide.\n\n### Git\n\n- [Git Style Guide](https:\u002F\u002Fgithub.com\u002Fagis\u002Fgit-style-guide) - Git usage and style recommendations.\n- [Few Rules from Git Documentation](https:\u002F\u002Fgithub.com\u002Fgit\u002Fgit\u002Fblob\u002Fmaster\u002FDocumentation\u002FCodingGuidelines) - Coding guidelines used in the Git project.\n\n### PowerShell\n\n- [The PowerShell Best Practices and Style Guide](https:\u002F\u002Fgithub.com\u002FPoshCode\u002FPowerShellPracticeAndStyle) - The Unofficial PowerShell Best Practices and Style Guide.\n\n## Platforms\n\n### Android\n\n- [Android Guidelines](https:\u002F\u002Fgithub.com\u002Fribot\u002Fandroid-guidelines) - Architecture and code guidelines we use at ribot when developing for Android.\n- [Xmartlabs Android Style Guide](https:\u002F\u002Fgithub.com\u002Fxmartlabs\u002FAndroid-Style-Guide) - Style guide for Android by Xmartlabs.\n\n### Apache\n\n- [Apache Developers' C Language Style Guide](http:\u002F\u002Fhttpd.apache.org\u002Fdev\u002Fstyleguide.html) - C language style guidelines for the Apache HTTP Server project.\n\n### API\n\n- [HAL](http:\u002F\u002Fstateless.co\u002Fhal_specification.html) - A simple format that gives a consistent and easy way to hyperlink between resources in your API.\n- [Microsoft REST API Guidelines](https:\u002F\u002Fgithub.com\u002FMicrosoft\u002Fapi-guidelines) - The Microsoft REST API Guidelines.\n- [JSON API - Recommendations](http:\u002F\u002Fjsonapi.org\u002Frecommendations) - This section contains recommendations for JSON API implementations.\n- [API Security Checklist](https:\u002F\u002Fgithub.com\u002Fshieldfy\u002FAPI-Security-Checklist) - Checklist of the most important security countermeasures when designing, testing, and releasing your API.\n- [Google Cloud API Design Guide](https:\u002F\u002Fcloud.google.com\u002Fapis\u002Fdesign) - A general design guide for networked APIs provided by Google.\n\n### Arduino\n\n- [Arduino style guide](https:\u002F\u002Fwww.arduino.cc\u002F) - General coding style guidance for Arduino.\n- [API Style Guide for Arduino](https:\u002F\u002Fdocs.arduino.cc\u002Flearn\u002Fcontributions\u002Farduino-library-style-guide\u002F)\n\n### Frontend Development\n\n- [CSS Guidelines](https:\u002F\u002Fcssguidelin.es) - High-level advice and guidelines for writing sane, manageable, scalable CSS.\n- [Frontend Guidelines](https:\u002F\u002Fgithub.com\u002Fbendc\u002Ffrontend-guidelines) - Some HTML, CSS and JS best practices.\n- [Sass Guidelines](https:\u002F\u002Fsass-guidelin.es) - An opinionated styleguide for writing sane, maintainable and scalable Sass.\n- [Airbnb CSS \u002F Sass Styleguide](https:\u002F\u002Fgithub.com\u002Fairbnb\u002Fcss) - A mostly reasonable approach to CSS and Sass.\n- [HTML Style Guide](https:\u002F\u002Fgithub.com\u002Fmarcobiedermann\u002Fhtml-style-guide) - A style guide which helps you write better, performant, structured, scalable and maintainable HTML.\n- [HTML + CSS Code Guide](http:\u002F\u002Fcodeguide.co) - Standards for flexible, durable, and sustainable HTML and CSS.\n- [U.S. Web Design Standards](https:\u002F\u002Fdesignsystem.digital.gov\u002F) - Open source UI components and visual style guide for U.S. government websites.\n- [CoffeeScript Style Guide](https:\u002F\u002Fgithub.com\u002Fpolarmobile\u002Fcoffeescript-style-guide) - A collection of best-practices and coding conventions for the CoffeeScript programming language.\n- [LESS Coding Guidelines](https:\u002F\u002Fgist.github.com\u002Ffat\u002Fa47b882eb5f84293c4ed) - Style guidelines for writing LESS.\n- [Google HTML\u002FCSS Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fhtmlcssguide.html) - HTML and CSS conventions and best practices.\n- [Guidelines for Responsive Web Design](https:\u002F\u002Fwww.smashingmagazine.com\u002F2011\u002F01\u002Fguidelines-for-responsive-web-design\u002F)\n- [Yelp Styleguide](https:\u002F\u002Fwww.yelp.com\u002Fstyleguide)\n- [Front-End Checklist](https:\u002F\u002Fgithub.com\u002Fthedaviddias\u002FFront-End-Checklist)\n- [BEM - Block Element Modifier](https:\u002F\u002Fgetbem.com\u002F) - A methodology that helps you to create reusable components and code sharing in front‑end development.\n- [Web Content Accessibility Guidelines (WCAG) 2.1](https:\u002F\u002Fwww.w3.org\u002FTR\u002FWCAG21\u002F) - Recommendations for making web content more accessible.  \n### GNU\n\n- [GNU coding standards](https:\u002F\u002Fwww.gnu.org\u002Fprep\u002Fstandards\u002F) - Coding and documentation standards for GNU software.\n\n### Java\n\n- [JavaEE Specification](https:\u002F\u002Fgithub.com\u002Fjavaee\u002Fjavaee-spec) - Official specification for Java EE.\n\n### Linux\n\n- [Linux kernel coding style](https:\u002F\u002Fwww.kernel.org\u002Fdoc\u002Fhtml\u002Flatest\u002Fprocess\u002Fcoding-style.html) - Coding style for the Linux kernel.\n\n### Mailchimp\n\n- [Mailchimp Content Style Guide](https:\u002F\u002Fstyleguide.mailchimp.com) - Content style guidelines for Mailchimp.\n\n### Mozilla\n\n- [Mozilla Coding Style Guide](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FMDN\u002FWriting_guidelines\u002FWriting_style_guide\u002FCode_style_guide) - Coding style guidance for Mozilla projects.\n\n### Google\n\n- [Google-related developer documentation](https:\u002F\u002Fdevelopers.google.com\u002Fstyle) - This style guide provides editorial guidelines for writing clear and consistent Google-related developer documentation.\n\n### Node.js\n\n- [Microsoft + Node.js Guidelines](https:\u002F\u002Fgithub.com\u002FMicrosoft\u002Fnodejs-guidelines) - Engineering guidelines for building Node.js apps.\n- [Node.js Style Guide](https:\u002F\u002Fgithub.com\u002Ffelixge\u002Fnode-style-guide) - A guide for styling your Node.js \u002F JavaScript code.\n\n### MongoDB\n\n- [Mongo Style Guide](https:\u002F\u002Fgithub.com\u002Fjsoendermann\u002FMongoStyleGuide) - Style guidelines for MongoDB usage.\n\n### SQL\n\n- [SQL Style Guide](https:\u002F\u002Fwww.sqlstyle.guide) - SQL style and formatting guidelines.\n\n### Other\n\n- [Keep a CHANGELOG](http:\u002F\u002Fkeepachangelog.com\u002Fen\u002F0.3.0\u002F) - Don't let your friends dump Git logs into CHANGELOGs™.\n- [Project Guidelines](https:\u002F\u002Fgithub.com\u002Felsewhencode\u002Fproject-guidelines) - A set of best practices for JavaScript projects.\n- [Semantic Versioning](http:\u002F\u002Fsemver.org) - Versioning scheme for managing releases.\n- [Indent style](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FIndentation_style) - Overview of indentation styles in programming.\n- [WebAppSec\u002FSecure Coding Guidelines](https:\u002F\u002Fwiki.mozilla.org\u002FWebAppSec\u002FSecure_Coding_Guidelines)\n- [Robot Framework User Guide](https:\u002F\u002Frobotframework.org\u002Frobotframework\u002Flatest\u002FRobotFrameworkUserGuide.html)\n- [CodeQL Coding Standards](https:\u002F\u002Fgithub.com\u002Fgithub\u002Fcodeql-coding-standards)\n\n## Frameworks\n\n- [Symfony Coding Standards](https:\u002F\u002Fsymfony.com\u002Fdoc\u002Fcurrent\u002Fcontributing\u002Fcode\u002Fstandards.html)\n- [Django Coding Style](https:\u002F\u002Fdocs.djangoproject.com\u002Fen\u002Fdev\u002Finternals\u002Fcontributing\u002Fwriting-code\u002Fcoding-style)\n- [Vue Style Guide](https:\u002F\u002Fvuejs.org\u002Fstyle-guide)\n- [Angular Style Guide](https:\u002F\u002Fangular.dev\u002Fstyle-guide)\n\n## Content Management System\n\n- [WordPress Coding Standards](https:\u002F\u002Fdeveloper.wordpress.org\u002Fcoding-standards\u002Fwordpress-coding-standards\u002F)\n- [Drupal Coding Standards](https:\u002F\u002Fwww.drupal.org\u002Fdocs\u002Fdevelop\u002Fstandards)\n- [Magento Coding Standards](https:\u002F\u002Fdeveloper.adobe.com\u002Fcommerce\u002Fphp\u002Fcoding-standards\u002F)\n- [Octobercms Developer Guide](https:\u002F\u002Foctobercms.com\u002Fhelp\u002Fguidelines\u002Fdeveloper)\n\n## Tools\n\n- [Checkstyle](https:\u002F\u002Fgithub.com\u002Fcheckstyle\u002Fcheckstyle) - Tool for checking Java source code for adherence to a Code Standard or set of validation rules.\n- [Conventional Changelog](https:\u002F\u002Fgithub.com\u002Fconventional-changelog\u002Fconventional-changelog)\n- [EasyCodingStandard](https:\u002F\u002Fgithub.com\u002Feasy-coding-standard\u002Feasy-coding-standard) - The Easiest Way to Use Any Coding Standard.\n- [ESLint](https:\u002F\u002Feslint.org\u002F) - The pluggable linting utility for JavaScript and JSX.\n- [JavaScript Standard Style](https:\u002F\u002Fstandardjs.com) - One JavaScript Style to Rule Them All.\n- [Laravel Pint](https:\u002F\u002Flaravel.com\u002Fdocs\u002F11.x\u002Fpint) - An opinionated PHP code style fixer for minimalists.\n- [North](http:\u002F\u002Fpointnorth.io) - Design and development standards to align and guide your project.\n- [PHP_CodeSniffer](https:\u002F\u002Fgithub.com\u002FPHPCSStandards\u002FPHP_CodeSniffer) - The tool for detecting and fixing the violations of the specified standards in PHP code.\n- [PHP Coding Standards Fixer](https:\u002F\u002Fcs.symfony.com) - The PHP Coding Standards Fixer (PHP CS Fixer) tool fixes your code to follow standards.\n- [RuboCop](https:\u002F\u002Frubocop.org) - A Ruby static code analyzer and formatter, based on the community Ruby style guide.\n- [semantic-release](https:\u002F\u002Fgithub.com\u002Fsemantic-release\u002Fsemantic-release)\n- [ShellCheck](https:\u002F\u002Fgithub.com\u002Fkoalaman\u002Fshellcheck) - A shell script static analysis tool.\n- [Agents.md](https:\u002F\u002Fagents.md) - A simple, open format for guiding coding agents\n","awesome-guidelines 是一个精心整理的高质量编程风格规范和标准列表。该项目主要收集了多种编程语言（如 C、C++、C# 等）及开发环境、平台、框架等方面的编码指南，旨在帮助开发者遵循最佳实践，提高代码质量和可维护性。它涵盖了从代码结构到命名约定等多个方面的建议，适用于希望提升自身编程技能或团队协作效率的开发者，尤其是在需要遵守特定项目或组织编码规范的情景下特别有用。",2,"2026-06-11 03:33:10","high_star"]