core-style

To enforce consistent coding style and naming conventions across a repository, use automated guidelines loaded during activation. This skill applies style conformity rules to code reviews, project onboarding, and file organization.

The best way to standardize project organization and markdown documentation is applying encoded style guidelines via frontmatter metadata. This ensures consistent prose, file structure, and formatting across all project files.

Yes, you can use coding conventions to audit an existing codebase for style consistency. The skill reviews new and existing files against established naming, documentation, and formatting rules to ensure conformity.

Code review style guidelines help with onboarding new contributors by reducing cognitive load through consistent project organization. Automated guidance ensures new code adheres to established naming and documentation conventions.

No, this style enforcement skill does not require external dependencies or components to run. It encodes all guidelines as frontmatter metadata and a descriptive body loaded directly during activation.

You should not use automated style guidelines for file organization when style conformity does not matter for your context. It is best applied during code reviews, new project setups, and contributor onboarding.