conventions

Analyze project structure and generate or update the .conventions directory.

41|10|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill conventions-izmailovilya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventions
Source: https://github.com/izmailovilya/ilia-izmailov-plugins/tree/main/plugins/agent-teams/skills/conventions
Command: npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill conventions-izmailovilya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You analyze the codebase and create or update the .conventions/ directory. This directory is the single source of truth for project patterns — it encodes taste once, so every agent (and human) follows the same conventions.

Core Features & Use Cases

  • Bootstrap or update the .conventions/ directory by generating gold standards, anti-patterns, and checks.
  • Dispatch researchers in parallel to scan the codebase and populate standardized patterns.
  • Validate consistency across patterns and provide a bootstrap/upgrade workflow.

Quick Start

Run the conventions bootstrap/update workflow to align the repository with current project patterns.

Frequently Asked Questions about conventions

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

FAQPage Schema
How do I bootstrap codebase conventions for a large project?

Codebase conventions are maintained by generating a `.conventions` directory that encodes gold standards, anti-patterns, and automated checks, ensuring all agents and humans follow the same patterns.

How does automated convention checking work for existing repositories?

Updating conventions involves running a workflow that dispatches parallel researchers to scan the codebase, refresh existing patterns, and validate consistency across the generated `.conventions` directory structure.

Can I use this to analyze codebases of any size and language?

Yes, the policy-driven approach applies to codebases of various sizes and languages, coordinating parallel researchers to bootstrap new conventions or refresh existing ones as needed.

What is the best way to enforce anti-patterns across a development team?

Compared to manual reviews, this approach encodes taste once into a `.conventions` directory, providing a single source of truth with gold standards, anti-patterns, and checks for all agents and humans.

Does bootstrapping conventions require any external dependencies?

No dependencies are required for bootstrapping conventions, as the Skill autonomously analyzes the codebase structure and generates the file-based `.conventions` directory with gold standards and anti-patterns.