Code Practice

Use this skill for cross-language engineering defaults in guidance, review, and implementation.

When to use

Trigger for work like:

• clean code or maintainability guidance
• refactoring for readability, ownership, or cohesion
• general code style or coding conventions
• naming, function shape, duplication, or complexity reduction
• API shape, module boundaries, and responsibility splits
• state, mutation, concurrency, error handling, or testability concerns
• code review focused on reusable engineering defaults rather than language or framework rules
• application vs library tradeoffs without language-specific rules

Do not use this skill when the main question is about component collaboration shape, Kotlin idioms, Spring architecture, Cucumber / BDD structure, or any framework-managed pattern.

Core promise