tech-lead/technical-standards

Defines coding standards, naming conventions, and testing requirements for engineering teams.

553|50|Updated Jan 10, 2026

Search Tags:#test coverage #naming conventions #Coding Standards #tech lead #Code review #Best practices #Error handling

Ready to run

npx skills add https://github.com/echoVic/boss-skill --skill tech-lead-technical-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-lead/technical-standards
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/tech-lead/technical-standards
Command: npx skills add https://github.com/echoVic/boss-skill --skill tech-lead-technical-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams without shared technical standards produce inconsistent code, mixed naming styles, and uneven test coverage, making reviews slow and maintenance costly. This Skill gives a tech lead agent a concrete, enforceable baseline of conventions.

Core Features & Use Cases

Naming Conventions: Standard rules for variables, constants, functions, classes, and files (camelCase, UPPER_SNAKE_CASE, PascalCase, kebab-case).
Code Organization Principles: Enforces single responsibility, DRY, KISS, and YAGNI guidelines.
Error Handling & Testing Rules: Requires try-catch with meaningful messages and logging, plus unit test coverage of at least 70% on critical paths.
Use Case: During a code review, the tech lead agent checks a pull request against these standards and flags inconsistent naming or missing tests before merge.

Quick Start

Ask the tech lead agent to review the current module against the technical standards and report any naming, error handling, or test coverage violations.

Frequently Asked Questions about tech-lead/technical-standards

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

FAQPage Schema

How do I enforce naming conventions in a code review?▼

Apply a naming convention table that maps each code element to a style: camelCase for variables and functions, UPPER_SNAKE_CASE for constants, PascalCase for classes, and kebab-case for files. Review each changed identifier against these rules during review.

What code organization principles should a tech lead enforce?▼

Enforce single responsibility so each function or class does one thing, DRY to eliminate duplicated code, KISS to keep implementations simple, and YAGNI to avoid building unneeded abstractions.

What test coverage is required by these technical standards?▼

Unit test coverage must be at least 70 percent, and all critical paths must have tests. Tests must be independent and repeatable so they produce consistent results across runs.

How should error handling be implemented according to these standards?▼

Use try-catch blocks to capture exceptions, provide meaningful error messages, log errors for diagnosis, and degrade gracefully so failures do not crash the entire workflow.

When should these technical standards not be applied rigidly?▼

Avoid rigid application when it conflicts with an existing framework's own conventions or when a prototype needs speed over polish. The standards target production code quality, not throwaway experiments.