code-quality

Evaluates frontend code quality across readability, predictability, cohesion, and coupling.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/dusvlf111/claude-setting-v0.1-fsd-next-etc --skill code-quality-dusvlf111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/dusvlf111/claude-setting-v0.1-fsd-next-etc/tree/main/.claude/skills/code-quality
Command: npx skills add https://github.com/dusvlf111/claude-setting-v0.1-fsd-next-etc --skill code-quality-dusvlf111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code quality risk and inconsistency across teams cause maintenance and review friction. This Skill codifies four quality axes—readability, predictability, cohesion, and coupling—to guide implementation, review, and refactoring decisions.

Core Features & Use Cases

  • Four quality axes with actionable criteria for frontend code (readability for easy scanning, predictability for stable behavior, cohesion for tightly related logic, and coupling to minimize cross-cut dependencies).
  • Practical strategies for organizing code and reducing drift, including guidelines for file structure, naming, and modularization; references to in-depth policies for deeper learning.
  • Use Case: teams adopt the Skill when assessing a new module or library, then apply concrete rules to improve maintainability and reduce bugs.

Quick Start

Review the codebase against readability, predictability, cohesion, and coupling, then apply the recommended strategies to improve maintainability.

Frequently Asked Questions about code-quality

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

FAQPage Schema
What are the core metrics for evaluating frontend code quality?

To improve code quality, review your codebase against readability, predictability, cohesion, and coupling metrics, then apply the recommended strategies for file structure, naming, and modularization to improve maintainability.

How do I reduce coupling and improve cohesion in a component-driven design?

Reducing coupling and improving cohesion in component-driven designs involves codifying concrete rules for organization, naming, and reviewing practices that minimize cross-cutting dependencies and group tightly related logic together.

Does this code quality guidance apply to scaling new modules and libraries?

Yes, this guidance applies to scaling frontend codebases and component-driven designs. Teams adopt these quality axes and concrete rules when assessing a new module or library to reduce maintenance friction and bugs.

What is the best way to enforce consistent code review practices across a team?

The best way to enforce consistent code review practices is to codify concrete rules for organization and naming based on four quality axes, providing actionable criteria and references to in-depth policies for deeper learning.