project-conventions

Codify naming, formatting, and structural patterns for repository consistency.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/lewing/maestro.mcp --skill project-conventions-lewing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/lewing/maestro.mcp/tree/main/.squad/templates
Command: npx skills add https://github.com/lewing/maestro.mcp --skill project-conventions-lewing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide codifies the project's conventions and patterns to maintain consistency across code, docs, and tooling.

Core Features & Use Cases

  • Establishes naming, formatting, and structural patterns used by the team.
  • Guides on file organization, coding standards, and review expectations.
  • Useful for onboarding new contributors and maintaining long-term coherence across the repository.

Quick Start

Follow these conventions when adding new code or documentation and align any new changes with the project’s established patterns.

Frequently Asked Questions about project-conventions

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

FAQPage Schema
How do I establish coding standards and conventions for a codebase?

Codebase conventions are established by codifying naming, formatting, and structural patterns into a central guide. This ensures all contributors align new code and documentation with established team policies, maintaining long-term coherence.

What is the best way to enforce codebase patterns across multiple contributors?

Enforcing codebase patterns requires applying consistent conventions to code, documentation, and tooling. By guiding file organization and review expectations, teams ensure maintainability and enable scalable collaboration across all new components.

How do I use coding standards to onboard new contributors to a repository?

Coding standards onboard new contributors by providing a clear guide to the project's established patterns. New members follow these conventions when adding code or documentation, quickly aligning their changes with existing structural and review expectations.

Does codifying team policies for documentation help with long-term maintainability?

Codifying team policies for documentation helps maintainability by ensuring long-term coherence across the repository. Consistent conventions guide structural patterns and tooling, satisfying requirements for scalable collaboration as the project grows.