code-standards

Validate directory structure and file naming conventions across projects.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/zhizhunbao/ai-dev-config --skill code-standards-zhizhunbao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-standards
Source: https://github.com/zhizhunbao/ai-dev-config/tree/main/core/skills/dev-code_standards
Command: npx skills add https://github.com/zhizhunbao/ai-dev-config --skill code-standards-zhizhunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining consistent and high-quality code structure and naming conventions across projects, preventing technical debt and improving maintainability.

Core Features & Use Cases

  • Directory Structure Validation: Ensures projects adhere to established patterns (e.g., Python's src/, tests/, docs/).
  • File Naming Convention Enforcement: Checks for adherence to snake_case, kebab-case, PascalCase, etc., based on project type.
  • Code Organization Review: Identifies potential issues like large files, unclear module responsibilities, and tight coupling.
  • Use Case: When starting a new Python project, use this Skill to automatically set up a clean, standard directory structure and verify that all new files and modules follow the defined naming conventions.

Quick Start

Use the code-standards skill to validate the directory structure and file naming conventions for the current project.

Frequently Asked Questions about code-standards

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

FAQPage Schema
How do I validate directory structure and file naming conventions in my project?

File naming convention enforcement checks project files for adherence to snake_case, kebab-case, or PascalCase based on project type. This prevents technical debt by ensuring consistent code organization across various programming languages.

How do I review code organization for tight coupling and unclear module responsibilities?

To set up a Python project with a clean directory structure, apply validation scripts to automatically configure standard src/, tests/, and docs/ directories. This ensures all new files and modules follow defined naming conventions from the start.

Does this code standards validation work across various programming languages and project types?

Yes, code standards validation works across various programming languages and project types by requiring adherence to predefined project-specific rules. It adapts to different structural patterns and naming conventions based on your tech stack.

What are the limitations of enforcing code organization and module cohesion automatically?

Enforcing code organization and module cohesion automatically requires strict adherence to predefined project-specific rules. Limitations include potential conflicts with custom architectural patterns and the need for manual intervention when resolving complex dependency management issues.