Project-wide coding standards and conventions specialist. Use PROACTIVELY when writing code, making architectural decisions, or establishing project conventions. Covers coding style, commenting, error handling, validation, tech stack consistency, and project conventions across all languages and frameworks.
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/22/2026
What it changes
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
Without skill86%
With skill91%
Checks it passed that the model alone missed
The response highlights applying the Don't Repeat Yourself (DRY) principle by extracting common reusable logic.
1 fixed19 passed either way2 still failing0 broke
Pass-rate lift
+5 pp
Tokens
+75%
Agent turns
0%
Response time
-21%
Model gemini-3.6-flashMeasured 8/22/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Two separate utility modules in a Go repository contain nearly identical 30-line helper functions for parsing ISO-8601 timestamps. The author suggests leaving them duplicate to avoid creating shared files. Which core coding style principle applies here?
What was checked, without and with the skill
Checked
Without skill
With skill
The response highlights applying the Don't Repeat Yourself (DRY) principle by extracting common reusable logic.
Missed
Passed
case-10 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md213 lines7 files
Project Standards
This skill provides comprehensive guidance on project-wide coding standards, conventions, and best practices that apply across the entire codebase regardless of language or framework.
When to Use This Skill
Use this skill when:
Writing code - Ensuring consistency with project standards
Making architectural decisions - Following established patterns
Onboarding - Understanding project conventions
Code review - Checking adherence to standards
Refactoring - Maintaining consistency during changes
Setting up new features - Following project conventions
Core Standards Areas
1. Coding Style
When to apply:
Naming variables, functions, classes, modules, or files
Structuring code for readability and maintainability
Deciding on function size and single responsibility
Removing unused code, commented-out blocks, or dead imports
Extracting reusable logic to avoid duplication
Applying consistent formatting and indentation
Refactoring code for clarity and simplicity
Principles:
Clear, descriptive names that reveal intent
DRY (Don't Repeat Yourself) principle
Single Responsibility Principle
Self-documenting code through structure
Consistent formatting across the codebase
Applies to: All code files (.py,.js, .ts,.jsx, .tsx,.vue, .rb,.go, .java,.rs, .cpp,.c, .swift,.kt)