Global Conventions

Enforce consistent project structure and documentation across repositories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/elliotsaha/smt-slack-app --skill global-conventions-elliotsaha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Global Conventions
Source: https://github.com/elliotsaha/smt-slack-app/tree/main/.claude/skills/global-conventions
Command: npx skills add https://github.com/elliotsaha/smt-slack-app --skill global-conventions-elliotsaha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistencies in project organization and development practices, fostering better collaboration and maintainability. It automates adherence to established conventions, saving time spent on code reviews and onboarding new team members.

Core Features & Use Cases

  • Consistent Structure: Guides file and directory organization.
  • Documentation Standards: Ensures READMEs and other docs are clear and complete.
  • Version Control Best Practices: Promotes consistent commit messages and PR workflows.
  • Use Case: When initiating a new feature, this Skill ensures the AI organizes files according to the project's established patterns, updates relevant documentation, and crafts commit messages that follow the conventional commits standard.

Quick Start

When creating a new feature, ensure the directory structure aligns with existing patterns, and update the README.md if new setup steps are introduced.

Frequently Asked Questions about Global Conventions

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

FAQPage Schema
How do I enforce consistent project structure across my repositories?

Enforcing consistent project structure involves organizing files and directories according to established patterns, updating documentation like READMEs when introducing new setup steps, and applying standardized naming conventions. This Skill automates adherence to those patterns, reducing manual code review effort and accelerating team onboarding.

What are best practices for version control commits and pull requests?

Version control best practices include following conventional commits standards for commit messages and establishing consistent pull request workflows. This Skill guides teams toward these standards, ensuring commits are meaningful, traceable, and aligned with project conventions for better repository history.

How should I document environment variables and configuration files securely?

Secure configuration management requires documenting environment variables and configuration files while keeping secrets out of version control. This Skill ensures consistent handling of secrets, environment config documentation, and dependency management across repositories, preventing accidental credential exposure.

Can this help when setting up a new feature in an existing project?

Yes. When creating a new feature, this Skill ensures directory structure aligns with established patterns, updates relevant documentation, and generates commit messages following conventional commits standards, maintaining consistency with your project's existing conventions.

What documentation standards should a project follow?

Project documentation standards include clear, complete READMEs, consistent changelog and release notes formatting, and documented code review requirements. This Skill enforces these standards across repositories, improving clarity for team members and reducing onboarding friction.

How do I manage dependencies consistently across projects?

Consistent dependency management involves standardizing how dependencies are declared, documented, and updated across projects. This Skill applies unified conventions for dependency handling, version control practices, and configuration management to prevent inconsistencies and maintenance issues.