awesome-repositories.com
Blog
MCP
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
wearehive avatar

wearehive/project-guidelines

0
View on GitHub↗
29,458 estrellas·3,158 forks·JavaScript·MIT·10 vistas

Project Guidelines

This project is a comprehensive set of architectural and coding standards for organizing and maintaining high-quality JavaScript applications. It provides a framework for JavaScript project best practices across the full software development lifecycle, establishing unified guidelines for project organization and development.

The guidelines cover specific standards for REST API design, utilizing resource-oriented interfaces and standardized HTTP methods. It also includes a web accessibility standard focused on semantic HTML and automated audits, alongside a defined Git workflow standard for branching strategies and commit message formatting.

The framework encompasses broad capability areas including code quality enforcement through static type checking and dependency auditing, project environment configuration for runtime consistency, and the implementation of secure, documented API endpoints.

Features

  • Project Organization Standards - Provides a comprehensive framework for organizing JavaScript project structures and architectural layouts.
  • Project Layout Standards - Provides a comprehensive set of project layout standards and best practices for JavaScript application organization.
  • JavaScript Best Practices - Provides a comprehensive set of standards for organizing and maintaining high-quality JavaScript applications.
  • Branching Workflows - Defines a structured Git branching workflow to maintain a clean version history and stable releases.
  • Git Collaboration Workflows - Defines standardized branching strategies and commit message formats to maintain a traceable version history.
  • API Access Security - Sets security standards for API endpoints using encryption, tokens, and rate limiting to prevent unauthorized access.
  • Coding Standards Enforcement - Implements automated systems for enforcing coding standards, linting, and formatting across the project.
  • Architectural Guidelines - Establishes a unified set of architectural and coding standards for organizing JavaScript applications.
  • Feature-Based Project Structures - Defines architectural patterns for organizing source files by product domain to improve encapsulation and navigation.
  • Git Version Control Standards - Defines standardized rules for Git branching and merging to maintain a professional version history.
  • API Design Guidelines - Sets best practices for creating consistent, resource-oriented, and maintainable RESTful software interfaces.
  • Project Organization - Guides the organization of project files by feature domain to improve encapsulation and navigation.
  • Resource-Oriented Design - Implements resource-oriented design principles to create predictable and standardized RESTful API interfaces.
  • Web Accessibility - Implements semantic HTML rules and automated audits to ensure web content accessibility for all users.
  • Web Accessibility Standards - Defines structural conventions and semantic HTML rules to support assistive technologies and web accessibility.
  • Code Quality and Review - Integrates static analysis, automated linting, and dependency auditing to ensure JavaScript code quality.
  • Quality Frameworks - Offers a comprehensive framework for enforcing consistent styling and static type checking in JavaScript.
  • RESTful API Designs - Provides architectural patterns for designing predictable and resource-oriented RESTful APIs.
  • Code Formatting and Style - Automates the enforcement of code style and formatting across the project codebase.
  • Linting And Formatting - Provides standards and tool recommendations for automating code linting and formatting to ensure style consistency.
  • API Documentation Standards - Establishes standards for documenting API endpoints, including request parameters and authentication methods.
  • Version Consistency - Provides guidelines for locking runtime and dependency versions to ensure identical setups across team members.
  • Dependency Lock Managers - Standardizes the use of lockfiles to pin dependency versions and ensure environment consistency.
  • Dependency Auditing - Implements guidelines for auditing external packages for security vulnerabilities and community health.
  • Environment-Variable Configuration - Defines how to separate development and production environments using variables to isolate data and secure tokens.
  • Environment Configuration Management - Guides the secure management of environment variables and version-locked dependencies for runtime consistency.
  • Commit Message Standards - Provides structured guidelines for writing professional and traceable version control commit messages.
  • Environment-Variable Isolation - Establishes guidelines for isolating development and production configurations to protect sensitive tokens.
  • Project Documentation Standards - Standardizes project documentation templates and commenting guidelines to ensure long-term maintainability.
  • Static Type Checking - Integrates static type checking into the development workflow to catch errors before execution.
  • Semantic HTML Accessibility - Provides a standard for implementing semantic HTML and using automated audits for web accessibility.
  • Testing Strategy and Process - Defines conceptual frameworks and methodologies for organizing test files and improving code testability.
  • Static Code Analysis - Specifies the use of static analysis tools to enforce code quality and consistent styling.
  • Coding Standards - Best practices for JavaScript projects.

Historial de estrellas

Gráfico del historial de estrellas de wearehive/project-guidelinesGráfico del historial de estrellas de wearehive/project-guidelines

Búsqueda con IA

Explora más repositorios increíbles

Describe lo que necesitas en lenguaje sencillo: la IA clasifica miles de proyectos open-source curados por relevancia.

Start searching with AI

Alternativas open-source a Project Guidelines

Proyectos open-source similares, clasificados según cuántas características comparten con Project Guidelines.
  • ecomfe/specAvatar de ecomfe

    ecomfe/spec

    4,605Ver en GitHub↗

    Spec is a comprehensive set of frontend coding standard specifications and project architecture guides. It provides a framework for organizing directory structures, module dependencies, and package layouts to create scalable and predictable codebases. The project defines rigorous governance standards for React components, including specific naming conventions and structural patterns for props. It also establishes a JSON API data specification to ensure predictable communication between system components through standardized exchange formats and HTTP response structures. The specification cov

    Ver en GitHub↗4,605
  • xirong/my-gitAvatar de xirong

    xirong/my-git

    7,396Ver en GitHub↗

    my-git is a comprehensive framework and reference guide for Git version control administration, repository governance, and software release management. It provides a structured approach to managing the software development lifecycle, from initial feature branching to final production deployment. The project distinguishes itself through a specialized AI-assisted development framework. This includes workflows for managing AI-generated code via automated diff reviews, intent-based commit splitting, and governance models for multi-agent coordination and session isolation using worktrees. The cod

    Python
    Ver en GitHub↗7,396
  • agis-/git-style-guideAvatar de agis-

    agis-/git-style-guide

    5,114Ver en GitHub↗

    This project is a version control style guide and contribution standard. It provides formal specifications for maintaining consistency in commit messaging, branch naming, and general development workflows within Git. The guide focuses on organizing project history through atomic commit structuring and specific rebasing strategies to ensure a clean, linear timeline. It establishes standardized conventions for naming branches with ticket identifiers and formatting commit messages to explain the reasoning behind changes. The framework also covers the coordination of team contributions through m

    Ver en GitHub↗5,114
  • pycqa/pylintAvatar de PyCQA

    PyCQA/pylint

    5,685Ver en GitHub↗

    Pylint is a static code analysis tool for Python that checks source code for errors, coding standard violations, and code smells without executing the program. It parses code into an abstract syntax tree and walks the tree to detect issues, enforces configurable style rules and naming conventions, and identifies duplicate code blocks by comparing tokenised source sequences. The tool also includes an inference engine that deduces variable types by simulating code paths, enabling deeper analysis even in untyped code. What distinguishes Pylint is its plugin-based checker architecture, which allo

    Python
    Ver en GitHub↗5,685
Ver las 30 alternativas a Project Guidelines→

Preguntas frecuentes

¿Qué hace wearehive/project-guidelines?

This project is a comprehensive set of architectural and coding standards for organizing and maintaining high-quality JavaScript applications. It provides a framework for JavaScript project best practices across the full software development lifecycle, establishing unified guidelines for project organization and development.

¿Cuáles son las características principales de wearehive/project-guidelines?

Las características principales de wearehive/project-guidelines son: Project Organization Standards, Project Layout Standards, JavaScript Best Practices, Branching Workflows, Git Collaboration Workflows, API Access Security, Coding Standards Enforcement, Architectural Guidelines.

¿Qué alternativas de código abierto existen para wearehive/project-guidelines?

Las alternativas de código abierto para wearehive/project-guidelines incluyen: ecomfe/spec — Spec is a comprehensive set of frontend coding standard specifications and project architecture guides. It provides a… xirong/my-git — my-git is a comprehensive framework and reference guide for Git version control administration, repository governance,… agis-/git-style-guide — This project is a version control style guide and contribution standard. It provides formal specifications for… pycqa/pylint — Pylint is a static code analysis tool for Python that checks source code for errors, coding standard violations, and… cpp-best-practices/cppbestpractices — This project is a curated collection of guidelines and technical resources designed to improve C++ code safety,… rwaldron/idiomatic.js — This project is a JavaScript style guide and a set of coding standards designed to ensure codebase consistency. It…