project-conventions

Define consistent project conventions with YAML frontmatter and component directories.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill project-conventions-lbouriez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/project-conventions
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill project-conventions-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This centralizes and standardizes coding conventions used across the Nectari-Devops-Squad codebase to reduce miscommunication and onboarding time.

Core Features & Use Cases

  • Central conventions document covering coding style, error handling, testing guidelines, and file structure.
  • Templates for patterns and anti-patterns to guide developers during reviews and audits.
  • Use Case: A new engineer consults the conventions to align tasks with the team's standard practices, speeding up ramp-up and PR reviews.

Quick Start

Review the current repository against the documented conventions and begin applying the patterns.

Frequently Asked Questions about project-conventions

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

FAQPage Schema
How do I set up coding conventions for a new codebase to speed up onboarding?

Defining coding conventions for a codebase involves creating a centralized document covering coding style, error handling, and file structure to standardize practices and reduce new engineer ramp-up time.

What are project conventions for code reviews and why do I need them?

Project conventions for code reviews provide templates for patterns and anti-patterns, guiding developers to align tasks with team standards and accelerating pull request reviews.

How can I enforce a style guide and best-practices across my repository?

You can enforce a style guide and best-practices by specifying a YAML frontmatter with descriptions and optional component directories to support automated guidance and audits across the repository.

Does this conventions approach work for any software development team size?

Yes, defining project conventions applies to governance within software development teams of any size working on a codebase, ensuring consistent standards during onboarding and audits.

What is the best way to document anti-patterns and coding standards for developers?

The best way to document coding standards is using a central conventions document with templates for patterns and anti-patterns, specifying YAML frontmatter and a three-section human-readable description.