curating-team-conventions

Name: curating-team-conventions
Availability: InStock
Author: somachak

Codify team conventions into structured engineering reference documentation.

Updated Apr 14, 2026

Search Tags:#linting #documentation #onboarding #formatting #coding-conventions #team-standards

Ready to run

npx skills add https://github.com/somachak/claude-code-skills-db --skill curating-team-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: curating-team-conventions
Source: https://github.com/somachak/claude-code-skills-db/tree/main/skills/ai-productivity/curating-team-conventions
Command: npx skills add https://github.com/somachak/claude-code-skills-db --skill curating-team-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Curates and codifies team conventions into a structured reference material for scalable engineering standards.

Core Features & Use Cases

Documentation of conventions (CONTRIBUTING.md, ENGINEERING.md) to avoid tribal knowledge.
Automated enforcement guidance (linters, formatters, CI) to ensure consistency.
Onboarding and team merges: standardize styles and workflows across projects.

Quick Start

Add or update team conventions in ENGINEERING.md and enable automated checks with ESLint and Prettier to enforce them.

Frequently Asked Questions about curating-team-conventions

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

FAQPage Schema

How do I document team coding conventions to avoid tribal knowledge?▼

Documenting team coding conventions involves curating standards into structured reference files like CONTRIBUTING.md and ENGINEERING.md. This codifies style, design, and workflow guidance to eliminate tribal knowledge and scale engineering practices across onboarding and code reviews.

What's the best way to enforce coding standards at scale across multiple projects?▼

Enforcing coding standards at scale requires codifying team conventions into shared documentation and enabling automated checks via CI. Standardizing linting and formatting rules across projects ensures consistency during cross-team mergers and onboarding.

How do I standardize linting and formatting rules for new team members?▼

Standardizing linting and formatting rules for onboarding requires documenting conventions in ENGINEERING.md and enabling automated checks with tools like ESLint and Prettier. This provides a structured reference to standardize styles and workflows immediately.

Can I use CONTRIBUTING.md to standardize workflows for cross-team mergers?▼

Yes, CONTRIBUTING.md standardizes workflows for cross-team mergers by codifying team conventions into structured reference material. It documents contributing guidelines and engineering standards to align styles and workflows across merged teams.

Does this approach work with CI for automated enforcement of team standards?▼

Yes, this approach works with CI for automated enforcement of team standards by standardizing linting and formatting rules. It enables automated checks to ensure consistency and enforce the codified conventions documented in your reference files.

When do I need to codify engineering conventions into a structured reference?▼

You need to codify engineering conventions into a structured reference when scaling standards across onboarding, cross-team mergers, and code reviews. This prevents tribal knowledge by documenting contributing guidelines and enabling automated enforcement.