Does it enforce specific formatting libraries?

Yes, it mandates the use of the internal @/lib/format library for all numbers, dates, and durations instead of native JavaScript formatting methods like toLocaleString().

How does this skill handle legacy code?

Unlike traditional systems that use deprecation notices, this skill encourages the immediate removal of obsolete code and shims to prevent technical debt accumulation and keep the codebase lean.

What is the 'No Backwards Compatibility' rule?

It means the skill will suggest renaming or deleting code to reflect its current state rather than adding shims or wrappers to support old function signatures.

Can this skill help with code reviews?

Absolutely. It is designed to scan for missing brackets in control flow and identify redundant utilities that should be merged into existing patterns before new code is committed.

Code Style Enforcement

Name: Code Style Enforcement
Author: legacy3

bylegacy3

•

Developer Tools

Enforces strict code formatting, DRY principles, and aggressive legacy code removal to maintain a high-quality, lean codebase.

About

The Code Style skill provides specialized guidance for maintaining a consistent and modern codebase by mandating strict structural rules. It enforces the use of brackets in all control flow statements, promotes the DRY (Don't Repeat Yourself) principle by requiring searches for existing utilities, and implements a 'no legacy' policy that prefers breaking changes over maintaining technical debt. Additionally, it standardizes data presentation by requiring the use of a centralized formatting library rather than native JavaScript methods, ensuring that every part of the application remains clean, readable, and easy to refactor.

Key Features

Mandatory bracket enforcement for all control flow statements
1 GitHub stars
Aggressive legacy code removal and no-backward-compatibility refactoring
Standardized data formatting using the project's internal utility suite
Proactive DRY checks across hooks, utils, and state helpers
Automated cleanup of unused imports, dead code, and console logs

Use Cases

Cleaning up technical debt by identifying and removing deprecated patterns
Enforcing consistent formatting and utility usage during code reviews
Standardizing a codebase during large-scale refactoring or migrations

About

Key Features

Mandatory bracket enforcement for all control flow statements
1 GitHub stars
Aggressive legacy code removal and no-backward-compatibility refactoring
Standardized data formatting using the project's internal utility suite
Proactive DRY checks across hooks, utils, and state helpers
Automated cleanup of unused imports, dead code, and console logs

Use Cases

Cleaning up technical debt by identifying and removing deprecated patterns
Enforcing consistent formatting and utility usage during code reviews
Standardizing a codebase during large-scale refactoring or migrations