Global Conventions

Organize project directories, files, and documentation using consistent standards.

Updated Mar 13, 2023
One-click install
npx skills add https://github.com/pdovhomilja/dovhomilja-cz --skill global-conventions-pdovhomilja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Global Conventions
Source: https://github.com/pdovhomilja/dovhomilja-cz/tree/main/.claude/skills/global-conventions
Command: npx skills add https://github.com/pdovhomilja/dovhomilja-cz --skill global-conventions-pdovhomilja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures project consistency across file organization, version control, documentation, and dependency management, reducing onboarding time, improving team collaboration, and streamlining development workflows.

Core Features & Use Cases

  • Standardized Structure: Organize directories, files, and documentation consistently across the project.
  • Version Control Best Practices: Follow guidelines for descriptive commit messages, branching strategies, and pull request processes.
  • Dependency & Configuration Management: Handle project dependencies, environment variables, and secrets securely and consistently.
  • Use Case: When setting up a new feature branch, this skill guides the AI to name the branch according to project standards (e.g., feature/new-user-profile), write a descriptive commit message, and update the README.md or changelog if necessary, ensuring project-wide consistency.

Quick Start

Create a new feature branch for 'user-settings-page' following the project's naming conventions and update the README.md with a brief description of the new feature.

Frequently Asked Questions about Global Conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize a disorganized Git repository to follow project conventions?

Organize your repository by establishing a consistent directory structure for source code, configuration, documentation, and dependencies. Apply naming conventions to files and folders, standardize commit message formats, define branching strategies (e.g., feature/bugfix naming), and document standards in a README or contributing guide. This reduces onboarding time and improves team collaboration.

What are best practices for Git commit messages and branching in collaborative projects?

Use descriptive commit messages that explain the why and what of changes. Adopt a branching strategy with consistent naming—like feature/user-settings or bugfix/login-error—to clarify intent. Create pull request templates and document review processes. These practices enable code review efficiency and make project history searchable and meaningful.

How should I handle environment variables and secrets in a project?

Store environment variables and secrets separately from source code using configuration files or secret management tools. Never commit credentials to version control. Document required environment variables in a .env.example file and establish conventions for naming and accessing secrets consistently across development, testing, and production environments.

Why is consistent project structure important for team development?

Consistent project structure reduces cognitive load during onboarding, enables developers to locate files intuitively, and facilitates automated tooling. Standardized patterns for dependency management, testing, and documentation make collaboration seamless and prevent confusion when team members switch between repositories.

What should a project README include to support developer onboarding?

A README should document project purpose, setup instructions, dependency requirements, how to run tests, branching conventions, and contribution guidelines. Clear documentation accelerates onboarding, reduces repetitive questions, and establishes shared understanding of project conventions and governance expectations.

How do I establish testing and code review standards across a codebase?

Define testing requirements in contribution guidelines, specify test coverage thresholds, and document the code review process including approval workflows. Use automated checks in pull requests to enforce standards. Consistent testing and review practices catch issues early and maintain code quality across the project.