Global Conventions

Name: Global Conventions
Availability: InStock
Author: Devan

Standardize project structure, version control, and documentation practices across a codebase.

Updated Nov 15, 2025

Search Tags:#code review #documentation #version control #project structure #standards #conventions #team collaboration

Ready to run

npx skills add https://github.com/DevanB/lucidlog --skill global-conventions-devanb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Global Conventions
Source: https://github.com/DevanB/lucidlog/tree/main/.claude/skills/global-conventions
Command: npx skills add https://github.com/DevanB/lucidlog --skill global-conventions-devanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the chaos of inconsistent project organization, varied development practices, and unclear communication. It establishes a unified approach to project structure, version control, and documentation, leading to a more maintainable codebase and smoother team collaboration.

Core Features & Use Cases

Standardized Project Structure: Guides organization of files, directories, and configuration.
Version Control Best Practices: Ensures consistent commit messages, branching strategies, and pull request processes.
Use Case: When initiating a new feature branch, use this skill to ensure the AI follows established naming conventions for branches, writes clear commit messages, and structures new files according to the project's global conventions.

Quick Start

Organize the new 'reporting' module's files and directories according to the global conventions, including environment variable management.

Frequently Asked Questions about Global Conventions

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

FAQPage Schema

How do I standardize project structure and naming conventions across my codebase?▼

Standardize project structure by establishing consistent directory layouts, file organization, and naming conventions. Define these standards in documentation, apply them to new modules and features, and enforce them during code reviews to maintain a predictable codebase that all team members follow.

What's the best way to write commit messages and structure pull requests for team collaboration?▼

Write clear, descriptive commit messages following a consistent format and structure pull requests with detailed descriptions of changes. Establish team guidelines for branching strategies, review workflows, and approval processes to streamline version control and improve code quality across the project.

How do I organize configuration and environment variables in a project?▼

Organize configuration by centralizing environment variable management, using consistent naming patterns, and documenting setup procedures. Structure configuration files according to your project's conventions to ensure developers can quickly understand and replicate the environment across different stages.

What should I include in contribution guidelines and testing requirements?▼

Document contribution guidelines that specify code style, testing prerequisites, and submission workflows. Define testing requirements, dependency management practices, and changelog maintenance to help contributors understand the standards and reduce friction in the review process.

Can I use these conventions for managing feature flags and release governance?▼

Yes. Apply consistent conventions to feature flag management, changelog updates, and release processes. Standardizing these practices ensures predictable deployments, clear version tracking, and transparent communication about changes across your team and users.

Do I need existing team processes before establishing global conventions?▼

No. Global conventions work whether you're establishing standards for a new project or refactoring an existing one. Start by documenting your current practices or desired standards, then apply them incrementally across files, branches, and documentation to build consistency over time.