project-conventions

Identify and enforce project-wide conventions for coding practices across the codebase.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill project-conventions-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/project-conventions
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill project-conventions-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize and codify project-wide conventions to ensure consistent practices across the codebase.

Core Features & Use Cases

  • Documented conventions for error handling, testing, code style, and file structure.
  • Guidance for onboarding and contributor workflows to accelerate collaboration.
  • Reference patterns and anti-patterns to avoid common pitfalls when adding new modules or refactoring.

Quick Start

Review the Patterns section and align new code with the documented conventions when adding or updating files.

Frequently Asked Questions about project-conventions

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

FAQPage Schema
What are project conventions for codebase standardization?

Project conventions codify rules for error handling, testing, code style, file structure, and documentation to ensure consistent coding practices across the codebase.

How do I document coding standards for onboarding new contributors?

Document coding standards by defining reference patterns and anti-patterns for refactoring and adding new modules, accelerating contributor workflows and onboarding.

Does this approach enforce file structure and code style during code reviews?

Yes, enforcing project-wide conventions ensures consistent coding practices during code reviews by checking file structure, code style, and error handling against documented patterns.

What is the best way to standardize error handling and testing patterns?

The best way to standardize error handling and testing patterns is to codify them in a referenceable Patterns section that contributors align with when updating files.

When do I need to codify project-wide conventions for refactoring?

You need to codify project-wide conventions when adding new modules or refactoring existing code to avoid common pitfalls and maintain consistent practices across the codebase.