“refactoring”

Plan refactors with Ontoly impact and dependency evidence.

Refactor code to improve structure and readability.

Aplicar refactoring cuando el encargo requiera código y contratos actuales.

Use when restructuring existing code without changing behavior.

Safe refactoring workflow for Go: behavior-preserving steps, compiler-checked renames, extracting packages, breaking circular dependencies, and strangler…

Guide for code refactoring, use this skill to guide you when user asked to refactor a components or functions and when an implementation of a plan requiring a…

Refactor high-complexity React components in Dify frontend.

Multi-target refactoring orchestrator.

Code refactoring patterns and techniques for improving code quality without changing behavior.

Plan behavior-preserving refactoring with explicit scope, depth and risk choices.

Audit code quality and architectural health or plan refactoring using Fowler code smells and techniques; write prioritized findings to docs/_refacs/.

Changing existing code structure without intending to change observable behavior.

Hierarchical catalog of code smells and Fowler-style refactoring techniques (source — refactoring.guru).

Perform one behavior-preserving refactoring step on a given target.

Use when 设计新界面、界面看起来难看/杂乱、布局与间距不协调、层级不清、配色刺眼或发灰、文字排版别扭、阴影层次不对、图片处理不当、需要设计评审或打磨收尾。覆盖层级、留白、字号阶梯、HSL 调色板、层次感、图片、空状态等 9 个主题的可执行规则。触发词：UI 设计、界面优化、设计系统、design…

Apply named refactoring transformations to improve code structure without changing behavior.

End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests.

Invoke IMMEDIATELY via python script when user requests refactoring analysis, technical debt review, or code quality improvement.

Use when a user explicitly requests Sepia refactor for minimal in-place prose revision.

Behavior-preserving code refactoring.

Audit and fix visual hierarchy, spacing, color, and depth in web UIs.

Refactor code at method, file, or project scope.

Use when a named refactor, rename, move or internal API reshape must keep behavior unchanged, or a shim or compatibility re-export tempts.

Refactor cleanly instead of layering sediment.